[checkpoint] Continue scicode_agent after verified sub-steps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 349
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 318
Description
Parent
Child of #3220 and #3024. No additional resource child.
State owner
responses_api_agents/scicode_agent/app.py owns sub-step cursor, generated scripts/responses, verification feedback, model/resource cookies, usage, and revision.
Adapter requirements
Use the shared whitebox participant and versioned boundary records. Persist output items, usage, cookies, last model-call identity, resource revisions, remaining budgets, and typed agent-specific state. Commit only after all effects of an operation are durable. On attempt N+1, skip reseeding and do not repeat completed model, tool, verifier, or judge work.
Acceptance criteria
- Restore after each verified sub-step continues with the next problem part without rerunning prior scripts or verification.
- Prepare/commit/process replacement/restore/resume succeeds at every supported boundary.
- Saved model responses, usage, cookies, and pending actions are applied exactly once.
- Checkpoint refusal retries without advancing history or the operation cursor.
- Resource revision mismatch, stale attempt, duplicate restore, and corrupt state fail closed.
- Completed-unacknowledged results cannot also be published as resumable work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with responses_api_agents/scicode_agent/app.py and the parent issues #3220 and #3024. Trace the sub-step cursor, generated scripts and responses, verification feedback, cookies, usage, revisions, and checkpoint boundaries described in the issue. Done means every listed acceptance criterion holds, including exact-once resume behavior and fail-closed handling of invalid state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100