Resuming a conversation picks up your current MCP servers, commands and tools instead of stale ones.
What's wrong with this entry?
When a conversation is resumed, the available tools, allowed agent types, slash commands and MCP configuration are now read fresh at that moment instead of being inherited from whatever the previous screen was holding. Changes you made to MCP servers or commands take effect on resume.
- API key re-verification now goes through the shared verification path with current credentials rather than a value passed down.
computeToolPoolFresh
Strings lifted out of the shipped bundle, so the claim above can be checked against them.