Skip to content

0.1.10: keep a failed merge from writing half a patch, carry nested repositories, and apply settings without a reconnect

Choose a tag to compare

@tomw1808 tomw1808 released this 28 Oct 05:14
· 6 commits to main since this release
d7ec236

Acts on three reports in #5: two days and nights on 0.1.9 (Linux and Windows 11), 25 to 27 October on Linux, and the Python monorepo on Windows.

Update: /plugin marketplace update flash-agents, update the plugin, then run node install.mjs in the plugin folder. A clone: git pull, then node install.mjs. From 0.1.10 on no reconnect is needed: an idle runtime started before the install replaces itself, and both settings files are re-read on every call. That matters in Claude Code's VS Code extension, which has no /mcp reconnect.

Fixed

  • A failed three-way apply no longer writes half a patch. Every merged file is read before the first one is written; if a write still fails part-way, the error names what was written. The reported git cat-file --filters … failed was any merged file over 1 MiB: Node's default output limit for a child process. Git output may now be up to 1 GiB.
  • A three-way apply keeps your line endings. With core.autocrlf=true and an LF checkout, every merged file came back CRLF. A merged file now matches your checkout as it is, and a worker's own line-ending change is kept.
  • A warm build cache survives a timed-out call. The slot that ran it is retired, and its .flash-cache (cargo target, cache: folders) used to be deleted with it, so the retry compiled from cold. It now moves to the replacement slot; setup steps run once more there. isolation.buildCacheEmpty: true says when a call starts with an empty cache.
  • A basePatch already in your tree is not applied again. The result warns, and the new patch then holds only the new work.
  • Edits inside a nested git repository are no longer lost. In a whole-root copy they are now carried in the patch, for a nested repository the top one neither tracks nor ignores, or one whose own folder it ignores. Repositories under an ignored folder such as vendor/ or node_modules/ are left as before. One that cannot be read is named in warnings, and its copy is kept.
  • Unknown arguments are refused with the nearest known name: unknown argument "file" for flash_patch; did you mean "files"?. Before, they were ignored, and a misspelt files returned the whole patch. provider, reasoningEffort, agentOptions, permissions and sandbox, which were ignored, are refused too.
  • The repeated-failure warning is fairer. grep, rg, git grep, diff and cmp exiting 1 ("no match", "differs") no longer count. When a later run of the same command succeeded, the warning says so and does not suggest cancelling.

New

  • Settings without a reconnect. .flash-agents.json and .flash-agents.local.json are re-read at the start of every writing call. A call already running keeps the settings it started with. An invalid file keeps its last good settings and is named in every result until it is fixed. A changed slotEnv restarts the tree's idle runtime, so the next call's commands see it.
  • The profile-version warning clears without a reconnect. An idle runtime started before node install.mjs is replaced at its next use; a busy one says it will be replaced once its calls end.
  • Queue visibility. A queued call shows its place in line (first come, first served) and which jobs hold the trees; flash_status has queue: { position, of, holders }.
  • Two worker instructions: list any change beside a stated rule ("only", "never", "one place") under its own heading, Rules crossed; and on Windows, commands run in PowerShell (7 when installed, else Windows PowerShell 5.1), not bash.
  • Docs: the Windows sandbox limits (owner-only folders as Python's tempfile makes them, and named pipes, which multiprocessing and pytest-xdist need), state_base on Linux for Unix socket path limits, uv folders and a per-slot cargo registry through slotEnv, and that a read-only call reads your live tree.

Verification

770 unit tests (716 in 0.1.9) pass. An independent review of the merged change found six more defects; all are fixed, each with a test that fails without the fix. The live suite was not run for this release, because the flash models it drives were out of credits.