OpenHands / OpenHands/software-agent-sdk
Release Docker conversation runtimes without deleting audit history
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 539
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 137
Description
Desired Behavior
The Docker runtime API supports inspection and reprovisioning but cannot explicitly release a finished runtime without deleting its conversation history. A scheduled factory therefore accumulates containers or loses its audit trail.
Acceptance Criteria
- An authenticated runtime stop endpoint releases a conversation container while retaining its trajectory and workspace.
- Stopping is idempotent and runtime inspection reports unavailable after stop.
- Explicit reprovisioning can restore the same conversation.
- Active execution is interrupted before release, and failed stop is surfaced.
- Behavior tests and a live Docker check demonstrate preservation and release.
Readiness
ready-for-dev. Depends on PR #4998 for the runtime lifecycle API.
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 by reading PR #4998 and the runtime lifecycle API it adds, then locate the authenticated Docker runtime entry point and existing behavior tests. Add coverage for idempotent stop, interrupted execution, preserved trajectory and workspace, inspection after release, and reprovisioning; finish by running the behavior tests and live Docker check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100