/boot — session boot ritual
The SessionStart hook (plugin/hooks/session_start.py) already ran this
automatically when this Claude Code session started, UNLESS it reported a
diagnostic on stderr (e.g. ambiguous account — more than one account is
registered and none was specified, or zero accounts registered yet). This
skill is the manual/fallback path; hooks are already armed either way — it
does not "arm" anything.
-
Check whether a session is already open and read its bundle:
trialerror session status -
If nothing is open (or the hook reported an account-resolution failure), boot explicitly:
trialerror session boot --account <account-id>First-ever boot on a brand-new program (zero accounts registered yet):
trialerror session boot --create-account "<your label>"trialerror session bootis idempotent by default: if a session is already open it returns that session's CURRENT bundle rather than refusing. -
Read the returned bundle in full before doing anything else:
pin_status/foreign_since_last— law rulings appended since your last session; read them before spawning anything (mid-flight staleness is visible-not-refused, but boot-time staleness should not be ignored).dangling_launches— PROVISIONAL/RUNNING launches orphaned by a session that never closed cleanly. Investigate before spawning more; if that prior session crashed, mark ittrialerror session abandon --session-id <id>once you understand why.inbox_items— the user's unread messages (already marked read by boot; do not re-fetch, but do NOT skip reading them here).budget— pool headroom per model class.active_jobs— detached workers (OCR/embed/index/...) still running from a prior session; they legitimately outlive it.latest_handoff_markdown— the previous session's handoff, if any.
-
Do not re-run
trialerror session bootagain this session unless you closed or abandoned the current one — with--freshit refuses outright while a session is already open (without--fresh, the default, it is a no-op that just re-reads the bundle).