Let finished loops answer, keep /goal armed, report done on pi and OpenCode (#346) - #351
Merged
Merged
Conversation
… to report done (#346) A live run of goal loops on all five backends with 0.1.70-beta2 found three gaps in the #350 fix: - `graphcode node send` to a loop that succeeded or failed was staged to its memory even while its session was up. A follow-up question now reaches a live session and changes nothing about how the loop resolved; edges and wakes still leave resolved loops alone. - A long goal moves to PROMPT.md, and `/goal` inside a file is prose, so Codex never armed its goal and recorded no verdict. The typed pointer now opens with the directive and the start of the condition, shrinking the head before it would drop the briefing (#345). - pi and OpenCode, whose verdict the daemon cannot read, finished their work and reported to their creator but never ran `graphcode node done`. Their goal prompt now ends with the exact command, child goal loops get it with their own id at birth, and the briefing says it plainly. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
scgopi
added a commit
that referenced
this pull request
Sep 13, 2026
PR #351 landed with one [LineLength] violation, so `make check` exited 2 on main. Formatter output only, no semantic change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016n4hSXVu6wLR4RCfnt6PPG
This was referenced Sep 13, 2026
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.
Follow-up to #350 (#346), from a live run of goal loops on all five backends with 0.1.70-beta2.
What the live run found
PROMPT.md, and/goalinside a file is prose — the goal was never armed, so Codex recorded no verdictgraphcode node doneA follow-up question sent to a finished loop with
graphcode node sendwas also staged to its memory instead of reaching its still-running session.What changes
/goalstays the command. When a prompt is too long to type and moves to a file, the typed line still opens with the backend's goal directive and the start of the condition, then points at the file.graphcode node doneonce the goal is met. Child goal loops get the exact command, with their own id, in their memory at birth, and the briefing says it plainly.