[checkpoint] Resume cline_agent sessions
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 #3221 and #3024.
Runtime state
responses_api_agents/cline_agent/app.py delegates authoritative continuation state to the Cline process, session database/data directory, and project tree.
Provider adapter requirements
Implement the shared opaque-runtime contract with provider/version, native session or thread ID, safe-boundary sequence, isolated workspace/session bundle manifest and digest, model-call lineage, resource/MCP metadata, exact resume operation, and stale-process fencing. Advertise export/restore only after native resume is proven; otherwise declare restart-only explicitly.
Acceptance criteria
- Retain per-run session/DB directories through commit and resume the captured session rather than deleting or sharing them.
- Kill and replace the agent server after each provider-emitted completed turn, then resume without duplicated model/tool effects.
- Session databases and workspaces are isolated by rollout attempt.
- Old processes cannot emit responses or mutate state after replacement.
- Missing, corrupt, or incompatible bundles fail restore before activation.
- Duplicate resume is idempotent or rejected deterministically.
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/cline_agent/app.py, then read the parent issues #3221 and #3024 for the shared opaque-runtime contract. Trace how continuation state is delegated to the Cline process, session database/data directory, and project tree. Done means isolated bundles can be safely committed and resumed, replacement processes are fenced, and invalid or duplicate restores fail deterministically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ai-infra-agents, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100