Kong / Kong/developer.konghq.com
AI Gateway: Document supported AI IDE clients and AI Proxy configuration requirements
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 28
- Forks
- 121
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 313
Description
Overview
With increasing numbers of users trying to proxy their AI IDE Clients via AI Gateway, we have to create documentation for AI IDE clients that can route through Kong AI Gateway, with specific configuration steps for each.
Scope
- Identify which IDEs support OpenAI-compatible URL configuration (for example, Cursor, VSCode, Copilot)
- Create how-to documents for the relevant AI IDE Clients
- Create a separate signpost landing page, similar to https://developer.konghq.com/ai-gateway/ai-clis/
Nice-to-haves (TBD)
- Document IDEs that bypass proxy through their own backend APIs
- Add authentication plugin configuration examples (OIDC, Key Auth) for IDE clients
- Note limitations where direct provider routing prevents proxy usage
Point of contact: TBD
Size
L to XL
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing AI Gateway AI CLIs landing page referenced in the issue and identify which listed AI IDE clients support OpenAI-compatible URL configuration. Done means how-to documentation for each relevant client, a separate signpost landing page, and coverage of the stated proxy limitations and configuration requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100