inf halo to kick off a one-off analysis, schedule recurring ones, watch a run reach completion, and read the resulting report.
How HALO is organized
- A run is one analysis of one agent over one time window. Each completed run produces exactly one report.
- A conversation is the thread a run lives in. The first assistant message is the original report; any follow-up questions you ask add more runs and more assistant messages to the same conversation.
- A schedule fires recurring runs for one agent on a cadence (hourly, daily, weekly, or monthly).
Quickstart: run an analysis and read the report
inf halo run create prints both the run-id and the conversation-id. The report prints in full from inf halo conversation get — no --json required. Add --json only when you want the raw structured payload for scripting.
inf halo agent
List the agents HALO sees in your project’s recent traces. You need an agent’s UUID to start a run or create a schedule.
inf halo agent ls
Options
inf halo run
Create and inspect HALO runs.
inf halo run create
Start a manual analysis for one agent over a time window.
--agent-uuid to pick from recent agents. In non-interactive or --json mode, --agent-uuid is required.
Options
inf halo run poll
Poll a run until it reaches a terminal state (completed, failed, cancelled, timed_out, or no_traces). Exits 0 only on completed.
Options
inf halo run get
Fetch a run’s status and its referenced trace dataset. This returns run metadata, not the report text — read the conversation for the report.
inf halo run events
List the structured event timeline for a run (started, heartbeat, agent steps, completed, failed).
Options
inf halo run cancel
Request cancellation of an in-flight run.
Options
inf halo conversation
Inspect HALO conversations and read their reports.
Alias: inf halo conv
inf halo conversation list
List conversations in the active project, newest first.
inf halo conversation ls
Options
inf halo conversation get
Print a conversation with its messages, runs, and trace datasets. The assistant messages are the report markdown — the first assistant message is the original report; later ones answer follow-up questions in the same thread. Message content prints in full.
--json to get the raw payload (every message, run, and trace dataset) for scripting.
inf halo schedule
Manage recurring HALO analyses. Each schedule targets one agent and fires runs on a cadence.
inf halo schedule list
inf halo schedule ls
inf halo schedule get
inf halo schedule runs
List recent runs fired by a schedule.
inf halo schedule create
inf halo schedule update
Update mutable fields on a schedule. Accepts the same flags as create (all optional), keyed by <schedule-id>.
inf halo schedule archive / unarchive
Archive a schedule so it stops firing, or restore it later.
archive prompts for confirmation. Pass -y / --yes to skip the prompt.
Common workflows
Related commands
inf traceandinf spaninspect the underlying traces HALO analyzes.- The MCP server exposes the same reports to AI coding assistants via
list_halo_conversationsandget_halo_conversation.