Skip to content

0.1.7: salvage a crashed server's work, and show what a worker is running

Choose a tag to compare

@tomw1808 tomw1808 released this 22 Oct 13:01
· 9 commits to main since this release
aaedb89

Acts on the field report in #5, from a night of unattended work on Windows 11.

Update: /plugin marketplace update flash-agents, update the plugin, then restart Claude Code (or /mcp reconnect plugin:flash-agents:flash). A clone only needs git pull.

Fixed

  • A crashed server's work is salvaged again. The restart sweep looked for a dead server's copies one folder level too high (<pid>/slots instead of <pid>/<instance>/slots). It found nothing and deleted the uncommitted work. It now checks both layouts, and the tests build the folder layout a real server creates. A dead server's folder whose salvage fails is kept and retried, at most every 10 minutes and three times in all, instead of deleted.
  • No connect timeout after a crash. The server answers initialize first and sweeps afterwards. A dead server's directory is renamed to trash-* and deleted in the background. clean deletes synchronously and includes trash in its report; trim leaves trash alone.

New

  • flash_status shows what a worker is running: each open command and how long it has run (current). It warns when the same command fails three or more times in a call (warnings).
  • Automatic retry of early, empty failures: under 180 s and 12 model calls, nothing delegated or only empty reports, nothing changed in the copy. Such a call is retried once, after 10 s, and its result says so.
  • Plain values in slotEnv: "OPENSSL_DIR": "value:C:\\openssl". PATH, PATHEXT, NODE_OPTIONS, NODE_PATH and LD_*/DYLD_* are refused for every kind.
  • Short patch ids: flash_apply, flash_patch and basePatch accept a unique prefix of at least 8 hex digits.
  • Patches record their task: a stored patch records its task (the brief's first line, job and session ids) and the worker's final report. A salvaged patch reads its task from the copy.
  • A foreground writing call that has to wait for a busy copy says so. A taskFile job is labelled with the brief's first line. Workers get three more lines of guidance.

Verification

560 unit tests and 116/116 live checks pass. We also ran the crash case live: a server killed with SIGKILL mid-task, then a new server on the same project. The new server answered in 77 ms and salvaged the worker's change as a patch named after its brief.