ClaudeHalt is the moment a Claude session goes idle — the ✷ 12s line
in the terminal. Every time that happens, a hook looks at what the session just finished and
decides what should happen next: carry on, resolve it automatically, or interrupt Julian.
One row here = one of those decisions, for one session. The Session column is the session it fired in, so yes — these are per-session. Click the Session heading to pick a session and see only its decisions.
live is the only ACTED lane,
every shadow_* lane is a would-lane. Nothing else on the row can change it.live, or one of shadow_cascade, shadow_v6,
shadow_continue_commit, shadow_class_check,
shadow_bare_signoff, shadow_ch_doneidle,
shadow_recommended. Shadow rows vastly outnumber live ones because
ClaudeHalt is still being trialled before it is switched on fleet-wide.CONTINUE_TODO more work left · NOTHING genuinely done ·
RESOLVE_VIA_DECIDE a question it can answer itself ·
SURFACE_QUESTION / SURFACE_FORK needs Julian.escalated, blocked_decide, suppressed_done_idle,
accepted_greyed_…. Where the row also recorded an intent that the
outcome overrode, it is shown after it as (wanted: inject).
On a would row it is always written would continue /
would escalate / would inject — never the bare verb.
A bare imperative in this column means the row acted; that is the whole rule.Source: table claudehalt_events in Master_Claude.db (also browsable
raw in All Tables below — this section is that same table, joined to
claude_user_messages so the escalation text is readable).
Background, including the full ACTED / would (no action) label scheme: C:/Users/julia/Nextcloud/Brain/System/ClaudeHalt/_wiki.md — section “DISPLAY VOCABULARY”.
claudehalt_events, pre-joined for readability.