Repository navigation
deep-loop v1.26.0
Added
- Read-only
run status [--json] [--cwd DIR] [--run-id ID] [--project-root R] [--now T]. It reusesrun resolve's selection and prints one closed-shapestatus_version: 1envelope: status, pause reason, budget, comprehension debt, pending human reviews, breaker, workstream counts and the next action. Exit 0 or 1 always carries the envelope; exit 2 is a usage error with empty stdout. It takes no lease, writes no state and evaluates no goal proof. - Claude Code status band (
hooks/status-band/, Claude Code 2.1.287 and later). One line above the prompt for the selectedrunningorpausedrun, or a notice when several active runs make the choice ambiguous.Status,AckandHidebuttons only fill an empty prompt; nothing is submitted. One merged toast on breaker, debt-gate, budget-stop and completion transitions. It runs onlyrun status --jsonand is active only while a terminal or desktop surface is attached.
Changed
- The static assertion grader recognizes Claude Code Mods host calls (
$.process.run,$.process.spawn,$.http.fetch), including aliases, optional chaining, wrapper members and helpers, so the band is covered byno-external-action-routes. /deep-loop-statusstates correctly thatbudget checkreturns{ok, reason, tier_after}; the figures come fromstate getorrun status --json.
Compatibility
.claude-plugin/plugin.jsonnow points athooks/hooks.claude.json, which repeatshooks/hooks.json's command hooks verbatim and adds the module. Grok 1.0.46 reads only the manifest hooks file, so the repetition keeps its hooks unchanged. Claude Code runs identical command hooks once (measured on 2.1.291, including a real/compact, and on 2.1.200). Codex reads onlyhooks/hooks.json, which is byte-identical.- Claude Code without Mods support, Codex and Grok show no band and behave as before. No schema or migration change.
- Test and CI results demonstrate the covered contracts, not statistical real-agent efficacy. The real Claude desktop-app composer was not exercised.
Implementation and validation history: #76