agent-definition-snapshot-at-session-startlisted

# An agent definition is snapshotted at session start ## Problem The natural loop for repairing a subagent is: read its definition, fix the frontmatter, dispatch the agent, confirm the fix. **That loop cannot work.** The Agent tool resolves `.claude/agents/*.md` once, at session start. Every edit after that point is inert for the rest of the session. So the confirming dispatch runs against the pre-repair snapshot, and **a correct repair reports as a failure.** Worse, the failure report names the *tool*, not the staleness — which sends the next hour hunting a capability that is not missing. ## Context / Trigger Conditions Any one of these: - A subagent returns **`Error: No such tool available: X. X is disabled for this session, in subagents as well as here.`** while the main session has successfully used `X` in the same session. The second half of that sentence is the generic absent-tool string and is **not a statement about your configuration**. - A subagent reports a tool as unavailable that **is listed in its own `tools:` frontmatter**. - A newly created agent file returns **`Agent type '<name>' not found`** with the file plainly on disk. - You edited anything under `.claude/agents/` earlier in this session. - You are about to write "the harness does not support X in subagents", "no edit to any file in this repository can change that", or "this needs a settings change" — about a subagent capability. ## Solution ### 1. Check the commit time against the sess