Skip to content

legume-mcp 0.4; a name a running job holds is skipped; version 0.10.2 - #41

Merged
YPARK merged 1 commit into
mainfrom
legume-mcp-0.4
Oct 20, 2026
Merged

YPARK merged 1 commit into
mainfrom
legume-mcp-0.4

Conversation

@YPARK

@YPARK YPARK commented Oct 20, 2026

Copy link
Copy Markdown
Contributor

What

  • legume-mcp goes from "0.3" to "0.4", for both the dependency and the dev-dependency. With 0.10.1, a tool already on legume-mcp 0.4 carried two copies of it.
  • When data-beans picks an output name itself (in today's results folder), it now skips any name a running job is writing, however the path is spelled. It does this through Call::ensure_free, on top of the claims data-beans already keeps. A name the agent gives is still refused while a job writes it, both by run_making/spawn_job and by the claim.
  • Version 0.10.2: a patch. Only the MCP server changes; there is no CLI or library change.

Checks

  • cargo fmt --check and cargo clippy --all-targets --features sim are clean.
  • cargo test --features sim passes, with legume-mcp 0.4.0 and legume-tui 0.3.14.
  • tests/detach_session.rs failed 0 of 10 runs, and 0 of 15 on legume-tui 0.3.13. Earlier, one test (a_kill_before_the_explorer_lets_its_output_file_finish) failed once while another crate was building at the same time. It waits a fixed 1 s, so heavy load can trip it.
  • Review: checked against MCP write tools in the background; legume-mcp 0.3; version 0.10.1 #40's review findings and the design settled there. This diff only adds the ensure_free check where a name is picked.

An output data-beans names itself (in today's results folder) skips
any name a running job writes, however spelled, through legume-mcp's
Call::ensure_free, as well as the ones data-beans' own claims hold. A
name the agent gives is still refused while a job writes it.
@YPARK
YPARK merged commit 0940cf9 into main Oct 20, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant