{"version":"2.1.323","anchor":"bridge-project-reply-mount-holds-back-thread-only-tool-pre-a","canonical_anchor":"bridge-project-reply-mount-holds-back-thread-only-tool-pre-a","heading":"Thread-only tool pre-approvals are held back when the tools are not a thread's","tier":"internal","area":"Bridge","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/bridge-project-reply-mount-holds-back-thread-only-tool-pre-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Thread-only tool pre-approvals are held back when the tools are not a thread's\n\nWhen replying for a project through the bridge, Claude Code no longer pre-approves thread-only tools unless the listed tools belong to a thread\n\n**What**\n\nClaude Code can pre-approve certain tools so they run without asking you for permission. Some of these pre-approvals are meant only for a conversation thread. The part of Claude Code that handles project replies over the bridge connection used to pre-approve every tool on its auto-allow list. It now watches the list of MCP tools (tools supplied by outside programs). When those tools do not belong to a thread, it holds back the thread-only pre-approvals and logs a note saying so.\n\nThe approval rules are also applied as soon as this reply handler starts, rather than later.\n\n**Why**\n\nFewer tools get automatic permission in this path, so some may now ask before they run.\n\n- Area: Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}