fix(loop)!: drop --all for Claude Code parity; persist no longer rolls back peer updates (0.7.4) - #23
Merged
Merged
Conversation
…s back peer updates (0.7.4) Claude Code's /loop has no cross-session flag — its jobs are strictly per-session — so this removes --all entirely instead of fixing its cross-process semantics (TEST_REPORT F-02/F-06/F-11/F-13, I-07/08/09): - scheduler/tools: list/cancel/pause/resume/stop/stop-all only ever see the current session; another session's tasks report "No task <id> in this session"; the `all` tool argument is gone; help/README updated. - store: cancelAll removed (no callers left). - store persist merge fix: an untouched (non-dirty) in-memory task no longer overwrites a newer disk version — only ids this instance actually modified win the merge, so two processes can no longer roll back each other's updates (TEST_REPORT problem 4). - README: dropped stale upgrade/history narratives; documents current behavior only. Verified with two real opencode serve processes sharing one project: cross-session tasks are invisible and unmanageable, bare stop stays session-local, and a peer's persist no longer reverts a pause. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the issues from the v0.7.3 field test report (
TEST_REPORT.md, 66 cases):--allentirely (report problems 1–3): Claude Code's/loophas no cross-session equivalent — its jobs are strictly per-session — so instead of fixing--all's broken cross-process semantics, all subcommands and both LLM tools are now purely session-scoped. Another session's tasks are invisible tolistand report "No task<id>in this session" for cancel/pause/resume. The cross-session refusal-message and[s:xxxx]tag doc mismatches disappear with the feature.persist()— only ids this instance actually modified win the merge. Two OpenCode processes sharing onetasks.jsoncan no longer roll back each other's updates (e.g. a peer'sset_fixed/pausebeing reverted).Test plan
npm test— 176/176 (all--allcases re-pinned to session-only semantics; new store merge-direction test)opencode serveprocesses on one project:listdoes not show A's task; B'scancel <A task>refused without--allhint; A's task intactpausedstate not rolled back/loop stopcancels only the current session;/loop helpcontains no--all🤖 Generated with Claude Code