OpenHands / OpenHands/software-agent-sdk
Discuss the future of the TypeScript local agent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 539
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 137
Description
Context
The TypeScript client contains an in-process LocalConversation implementation, a stub LocalWorkspace, local security/confirmation helpers, and a browser demo. The remote Agent Server client is the primary production path.
The local loop supports custom tool executors, but it is not full SDK parity: LocalWorkspace cannot execute filesystem or shell operations, confirmation handling is incomplete, and persistence/security/stuck-detection integration is limited.
Decision needed
Decide whether to:
- retain and explicitly support the local agent, including end-to-end coverage and a documented scope;
- move it to a separate experimental package/example; or
- remove it in a future major release with migration guidance.
No removal is proposed by this issue. This tracks the product/API decision before any future breaking cleanup.
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 inspecting the TypeScript client's LocalConversation, LocalWorkspace, local security and confirmation helpers, and browser demo, then compare them with the remote Agent Server client. Done means recording a decision to retain, separate, or remove the local agent, with its supported scope or migration guidance documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100