Skip to content

v0.8.2 — Runs survive their sessions

Choose a tag to compare

@dharrisHub dharrisHub released this 18 Aug 20:40
· 3 commits to main since this release

Three fixes from the CLI's first real days, each found live and each pinned by a test that stages the exact failure.

Runs survive their sessions

  • Abnormal ends recover themselves. A run or resume session that dies with the run still marked running — a dropped stream, a crashed process — is re-driven in place instead of printing a resume line at an empty chair. Bounded by EXOLVRA_GENESIS_AUTO_RESUMES (default 2, 0 disables). Deliberate endings are never re-driven: a lead that settled blocked made a decision, a tripped budget guard enforced one, an interrupt was a person.
  • Recovery backs off before it retries. Attempt N waits N × EXOLVRA_GENESIS_AUTO_RESUME_DELAY_MS (default 15s) first — found live when a 529 "Overloaded" killed a run and both instant retries died inside the same overload window. The notice says how long, and Ctrl-C during the wait still wins.

Builds may build

  • run and resume default to --permission-mode bypassPermissions. An unattended build executes the verification commands it was given; under the old cautious default a headless loop could edit files but never run a command — and discovered it 25 minutes in. The flag is now the restriction (acceptEdits for cautious operators); plan keeps the cautious default because it executes nothing.

The test double learned to fail once and then succeed — the exact shape recovery exists for — and help environment documents both new variables. Suite: 1053 tests.