{"version":"2.1.268","anchor":"resuming-an-in-process-teammate-now-checks-folder-trust-befo","canonical_anchor":"resuming-an-in-process-teammate-now-checks-folder-trust-befo","heading":"Resuming an in-process teammate now checks folder trust before restoring its custom agent definition","tier":"notice","area":"Trust & Teams","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/resuming-an-in-process-teammate-now-checks-folder-trust-befo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Resuming an in-process teammate now checks folder trust before restoring its custom agent definition\n\nResuming a background teammate now requires folder trust before restoring its custom agent setup\n\n**What**\n\nWhen resuming an in-process teammate (a background agent running as part of a multi-agent team), Claude Code now checks whether the folder that its custom agent definition came from is trusted. If it isn't, the custom definition is no longer restored: the teammate falls back to only the team-essential tools and no custom instructions, and an error is logged (`agent_type_untrusted`) explaining that the user needs to run Claude Code in that folder and accept the trust dialog.\n\n**Why**\n\nThis prevents a custom agent definition from an untrusted folder from being silently restored with its full instructions and tools when a teammate is resumed.\n\n- Area: Trust & Teams\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}