Can I think of it as ACP(agent-client-protocol)-over-HTTP? I know ACP is an editor-oriented local protocol, but I think it's similar to the design idea of this project.
I’ll take a stab after just reading documentation. I’ve been waiting for a good open source “wrapper” for Claude Code that allows me to run it somewhere and expose it as an API to be driven by a thin client elsewhere, and this appears to be that.
Furthermore, it exposes both the main session manager API, allowing it to spawn new sessions, as well as the API to chat with any given session directly. (Many wrappers allow you to wrap a single Claude code session in an API, driven by tmux under the covers, but don’t expose the meta-API to manage the sessions themselves)
I would use it to write a mobile or web client for my “agents” running remotely, either on sprites.dev, or on my MacBook over tailscale. (I currently use a mobile terminal for this, and have a list of Claude Code wrappers to try, but this “feels” like a cleaner abstraction primitive to build around.)
The above might be wishful thinking on my part, but hopefully the OP will correct me.
Congratulations on open sourcing this. Is there a small video explaining how it feels?
Thank you!
Posted this morning an overview of the project: https://x.com/NathanFlurry/status/2018366627021291699
Can I think of it as ACP(agent-client-protocol)-over-HTTP? I know ACP is an editor-oriented local protocol, but I think it's similar to the design idea of this project.
That's correct.
As you said – in terms of project goals, the biggest difference is:
- ACP seems to be focused on providing a universal API for the subset of features required for editors
- Sandbox Agent SDK is focused on automating agents, so aims to provide a much more comprehensive API coverage for niche agent-specific features
We maintain a feature coverage matrix (https://sandboxagent.dev/docs/session-transcript-schema#cove...) – it's early, much more coming soon.
For the newly initiated - can you help explain some common use cases? I’m not sure I fully grok practical usage of this
I’ll take a stab after just reading documentation. I’ve been waiting for a good open source “wrapper” for Claude Code that allows me to run it somewhere and expose it as an API to be driven by a thin client elsewhere, and this appears to be that.
Furthermore, it exposes both the main session manager API, allowing it to spawn new sessions, as well as the API to chat with any given session directly. (Many wrappers allow you to wrap a single Claude code session in an API, driven by tmux under the covers, but don’t expose the meta-API to manage the sessions themselves)
I would use it to write a mobile or web client for my “agents” running remotely, either on sprites.dev, or on my MacBook over tailscale. (I currently use a mobile terminal for this, and have a list of Claude Code wrappers to try, but this “feels” like a cleaner abstraction primitive to build around.)
The above might be wishful thinking on my part, but hopefully the OP will correct me.
Hit the nail on the head.
(Sprites.dev in the works already.)