Codex/bcs bot v1 contract - #7
Conversation
|
@codex review |
6a65260 to
534d8e8
Compare
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6a652603f8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| /openapi/v1/bots/{bot_id}: | ||
| $ref: ./openapi/bots.yaml#/BotPath |
There was a problem hiding this comment.
In the checked gateway configuration (src/gateway/configs/application.yaml), every /openapi/v1/bots/** request is routed to the Backend, which already implements GET /openapi/v1/bots/{bot_id} with its own incompatible Bot model in src/backend/src/agentclaw/community/adapters/http/openapi_v1/bots/router.py; meanwhile, the BCS V1 router merges no Bot routes. Consequently, clients of this new BCS contract will reach the Backend handler rather than the declared BCS operation (and the other new Bot operations will return 404/405). Use a BCS-owned namespace or coordinate the gateway and serving implementation before adding this path to the authoritative contract.
AGENTS.md reference: AGENTS.md:L56-L61
Useful? React with 👍 / 👎.
2 participants
Problem
Solution
Validation
Compatibility and risk (optional)
Spec (optional)
Related issues (optional)