[Bug]: Creating MCP proxies without proper authorization tokens logs the user out of the workspace
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
AI Workspace
Please select the aspect the issue is related to
Aspect/UI (Frontend layouts, components, styling)
Description
When setting up an MCP proxy for a secured server, omitting the required credentials triggers an unexpected workspace logout. The system terminates the active session rather than preventing the action and displaying a UI error.
Steps to Reproduce
- Login to AI workspace and navigate to create MCP proxies
- Enter GitHub's official MCP server URL: "https://api.githubcopilot.com/mcp/"
- Click Fetch Info
- User is logged out
Severity Level of the Issue
Severity/Critical (Core functionality is broken but there is a workaround. Need urgent attention)
Environment Details (with versions)
No response
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 from the AI Workspace MCP proxy creation flow and the Fetch Info action, reproducing the issue with GitHub's official MCP server URL and no credentials. Trace how the failed authorization response affects the active session; done means the workspace remains logged in and the UI shows an error instead of logging the user out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100