fix: use backend proxy for remote AgentKit to avoid CORS#584
Merged
Conversation
- Add /agentkit-proxy/* route in backend (similar to skillhub proxy) - Remove CORS-related headers (origin, referer, sec-fetch-*) before forwarding - Frontend routes remote AgentKit requests through proxy via X-AgentKit-Base/Key headers - Local agents continue to use same-origin requests (no impact) Fixes 403 Forbidden error when connecting to remote AgentKit APIs Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
yaozheng-fang
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/agentkit-proxy/*解决远程 AgentKit 跨域问题根因
浏览器直接请求远程 AgentKit 时，CORS 策略阻止跨域访问，返回 403 Forbidden。
修复
参考 Skill Hub 代理实现，添加后端代理转发远程请求，移除浏览器特有 headers。
测试