Hey! This is a known issue with the MCP allowlist. The team is aware and already tracking it. A few users have reported the same behavior where clicking “Allowlist” doesn’t save the permission.
A couple things that would help narrow it down:
Which MCP server does this happen with?
In Settings > Agents > Auto-Run Mode, which option is currently selected?
For now, you can try a workaround. Go to Settings > Agents > Auto-Run Mode and switch to Auto-Run in Sandbox. This fully bypasses the allowlist prompt for MCP tools and runs them in an isolated environment.
Also, some users noticed the allowlist syntax can change between sessions, like project-0-servername:tool vs servername:tool, which can make previously saved entries stop working. If you’re seeing that pattern, try manually adding a wildcard pattern like *servername:* to your allowlist.
Let me know if switching the auto-run mode helps, or if you need more help.