Files

1.7 KiB

Triage an issue

Triage lets your own coding agent investigate a Hanzo Dev problem. The agent reads the logs and state of the machine, checks the Hanzo Dev source for that version, finds known issues, and can help you write a good GitHub issue. It asks before it applies a fix or posts anything.

In the app

Open the command palette and choose Triage an issue. A new thread with no project opens, with the triage playbook linked in the message. Choose any provider, describe what went wrong after the link, and send. Hanzo Dev gets the source for the server's version while you write.

Triage runs on the machine of the thread or draft that you have open. With nothing open, it uses your primary machine if that supports triage, or else the first connected machine that does. The new thread shows the machine name, and on mobile the palette row shows it before you start. If you change the machine before you send, triage moves to that machine. The agent runs inside that Hanzo Code server, so it gives you any restart steps and does not do them itself.

In a terminal

If the app does not start, or triage does not work in the app, run:

npx hanzo triage

It starts Claude Code, Codex, or Antigravity in your terminal with the same instructions. If more than one is installed, it asks which to use. You can also choose explicitly:

npx hanzo triage --agent antigravity
npx hanzo triage --agent codex

Antigravity needs Google's standalone agy CLI on your PATH and its own sign-in. The ACP runtime installed through Hanzo Dev does not include this terminal CLI. Install it using Google's CLI setup guide. Pass --model <model-id> to choose a model, or leave it out to use the CLI's default.