investigate

/zeropath:investigate

Thin entrypoint. The full request-poll-summarize flow lives in the zeropath-investigator subagent.

What you do

Spawn the subagent immediately. Don't probe config/creds/CLI - auto-bootstrap handles those.

Use the Agent tool with subagent_type: "zeropath-investigator". Brief it with:

• The user's full intent
• The bound repo from ~/.zeropath-agent-plugin/repo-binding.json (subagent uses it to scope batch filters by default - "investigate the criticals" means this repo, not the whole org)

Target shapes the subagent accepts:

• A single finding id (/zeropath:investigate issue_abc123)
• A batch filter ("all open CRITICAL on backend-api with no investigation yet")
• No target at all - subagent picks the highest-severity unreviewed finding in the bound repo and confirms before triggering

Important

Investigations are not free - they trigger real backend work. The subagent requires explicit confirmation before requesting; don't try to streamline that out.