feat(framework): persist orchestration state + --resume (#211)#216
Merged
Conversation
Save the run's orchestration state (stack rationale, loop status, decisions ledger) so a restarted dashboard can resume it. The dashboard is a pure projection of the FrameworkEvent stream, so persisting is durably logging that stream: append to .framework/events.jsonl, keep a derived run.json snapshot, and write a human-readable DECISIONS.md. --resume replays the log into a fresh dashboard read-only; --no-persist opts out. We do not persist the agent's transcript (Claude Code owns it), only our orchestration events. Part of #209. Closes #211.
suleimansh
added
enhancement
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.
Persists our orchestration state so the dashboard survives a restart. Closes #211 (part of #209).
The dashboard is already a pure projection of the run's event stream, so persisting is just durably logging that stream. Each run:
.framework/events.jsonlin the workspace,run.jsonsnapshot (status, passes, intent, session), andDECISIONS.mdat the root.framework --resumereopens the last run's dashboard read-only by replaying the log into a fresh stream, no agent run.--no-persistopts out.Per the sync: no chat-history DB. Claude Code owns the transcript; we persist only our orchestration events.
New
RunStore(injectable fs, in-memory tested) +--resume/--no-persistflags. 82 tests pass; verified end-to-end with a--fakerun then--resume.