chore(docs): update links and minor improvements to AI Bridge #20714
Conversation
| "title": "MCP Tools Injection", | ||
| "description": "How to configure MCP servers for tools injection through AI Bridge", | ||
| "path": "./ai-coder/ai-bridge/mcp.md", | ||
| "state": ["early access"] |
There was a problem hiding this comment.
Marking the MCP Tools injection section explicitly as Early Access. We would like to keep this feature opt-in and EA even after AI Bridge itself graduates to Beta or GA.
| Template admins can pre-configure workspaces to route all AI tool requests through AI Bridge, providing a seamless and secure experience for users. This can be done for both Coder Tasks and other AI tools running in the workspace. | ||
| Template admins can pre-configure workspaces to route all AI tool requests through AI Bridge, providing a seamless and secure experience for users. This can be done with either [Coder Tasks](../tasks.md) or AI agents running in the workspace. | ||
|
|
||
| ### Using Coder Tasks |
There was a problem hiding this comment.
I still think mentioning Coder Tasks here is distracting and unnecessary.
We're still talking about the basic setup here. Tasks is an optional integration, therefore it should have lower hierarchical priority.
There was a problem hiding this comment.
I will try to come up with a different version. Or we can drop Taks. Thoughts @david-fraley?
There was a problem hiding this comment.
We should absolutely keep the Tasks section, but not make it sound like Tasks are required for Bridge to work.
2479f38 to
a106652
Compare
dannykopping
left a comment
There was a problem hiding this comment.
Thanks for reorganising the doc 👍
One suggestion but LGTM
Co-authored-by: Danny Kopping <danny@coder.com>
Addresses some feedback from #20640