{"version":"2.1.251","anchor":"clearer-error-when-an-agent-id-came-from-another-claude-code","canonical_anchor":"clearer-error-when-an-agent-id-came-from-another-claude-code","heading":"Clearer error when an agent id came from another Claude Code process","tier":"notice","area":"Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/clearer-error-when-an-agent-id-came-from-another-claude-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Clearer error when an agent id came from another Claude Code process\n\nResuming an agent id from another process now explains where the id came from.\n\n**What**\n\nResuming an agent whose transcript is missing now explains that the id likely came from a different Claude Code process, such as a lead's subagent seen from a teammate pane, and tells you to reply through the naming session rather than pasting the raw id.\n\n**Details**\n\n- Only shown when the transcript is genuinely missing and the agent's name resolves to a known session; otherwise the previous generic failure is used.\n\n**Evidence**\n\n`it never ran in this session \u2014 reply through \"${ki}\" or the session that sent it instead of the raw id`\n\n- Area: Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}