{"version":"2.1.248","anchor":"coordinator-sessions-are-told-skills-are-read-only-for-them","canonical_anchor":"coordinator-sessions-are-told-skills-are-read-only-for-them","heading":"Coordinator sessions are told skills are read-only for them","tier":"soon","area":"Coordinator Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/coordinator-sessions-are-told-skills-are-read-only-for-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Coordinator sessions are told skills are read-only for them\n\nCoordinator sessions are told skills only load for them, never execute.\n\n**What**\n\nNew instruction text tells a coordinator session that when it uses the Skill tool, the skill is only loaded and not run: no forking, no permission grants, no hooks and no preamble shell commands. Execution happens in worker sessions instead. The text is present in this build; where it is included in a prompt is decided at runtime.\n\n**Evidence**\n\n`no fork, no permission grants, no hooks, no preamble shell commands`\n\n- Area: Coordinator Mode\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}