Milestone 5: agent server migration fan-out
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 349
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 324
Description
Work (In parallel):
- Hermes follow-up and broader resource-access validation.
- OpenCode
- OpenClaw
- Pi
- Codex, including normalized AgentObservationBundle.
- Remaining CLI harnesses
Definition of done:
- Every standard Responses API harness passes seed, activation, close, cookie isolation, cancellation, observation, token-capture, and borrowed-sandbox tests.
- Each migrated harness still passes compatibility /run tests.
- No migrated harness contains benchmark-specific setup or cleanup.
- Every nonstandard harness has a named specialized processor requirement.
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 locating the standard Responses API harnesses and their seed, activation, close, cookie-isolation, cancellation, observation, token-capture, and borrowed-sandbox tests. Review the listed harness groups and compatibility /run tests; done means all required tests pass, benchmark-specific setup and cleanup are absent, and each nonstandard harness has a named specialized processor requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100