Skip to content

feat: save headless -p sessions so --continue can resume them - #42

Merged
ostepan8 merged 2 commits into
mainfrom
fix/headless-session-persist
Oct 5, 2026
Merged

ostepan8 merged 2 commits into
mainfrom
fix/headless-session-persist

Conversation

@ostepan8

@ostepan8 ostepan8 commented Oct 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

marathon -p (headless print mode) saved no session, so a later marathon --continue had nothing to resume. Multi-turn benchmarks that resume an agent between steps could not use Marathon. This change saves headless sessions the same way interactive ones are saved.

Test plan

  • cargo test: 568 pass (run 2026-10-04)
  • Prod two-turn check on api.subconscious.dev: turn 1 told it a word, --continue in turn 2 recalled it

Notes

🤖 Generated with Claude Code

ostepan8 and others added 2 commits October 3, 2026 22:22
A headless run kept its conversation in memory only, so a later
`marathon -p "next" --continue` failed with "no prior session found".
Benchmarks that send follow-up turns (chained Terminal-Bench tasks,
repair rounds, simulated users) could not use Marathon.

Headless runs now append each turn through the same SessionStore the
TUI uses: to the resumed file for --continue/--resume, otherwise to a
lazily created ~/.sc/sessions/<id>.jsonl, so a run with no turns leaves
no file.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@ostepan8
ostepan8 merged commit d708597 into main Oct 5, 2026
5 of 8 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