Repository navigation
[Feature] Add kosa8 Cloud as a workspace (sandbox) backend #4105
drvt69talati
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm on the kosa8 team (kosa8.com: microVM sandboxes for AI agents, hosted API at
api.kosa8.com). We'd like to add kosa8 Cloud as a workspace backend, next to the E2B, Daytona, OpenSandbox and K8s backends, and would like to check with the core team first, as CONTRIBUTING.md asks.Problem. AgentScope users who run agent code on kosa8 Cloud have no
WorkspaceBasefor it today, soexec_shell,read_fileandwrite_filehave to be wrapped by hand.Proposal. Same shape as
_e2b:src/agentscope/workspace/_kosa8/:Kosa8Backend(BackendBase)(getcwd,exec_shellwith timeout and exit code,read_file/write_filethrough kosa8's file API) andKosa8Workspace(SandboxedWorkspaceBase)withsandbox_id, create on start, reattach by id, delete on close.app/workspace_manager/_kosa8_workspace_manager.py, followingE2BWorkspaceManager, including the prewarm hooks.api_key(orKOSA8_API_KEY),templateorimage,size,ttl,env, and egress (internet on or off, or allow and deny lists, enforced on the host).kosa8Python SDK as an optional extra, imported lazily; unit tests with the client mocked, plus a live test that only runs withKOSA8_API_KEYset.Each kosa8 sandbox is its own microVM with its own kernel. kosa8 also has checkpoints and fork of a running sandbox, which could later help with prewarming, but that is not part of this proposal.
kosa8 Cloud is a paid service (plans from $29/month; no free tier). SOC 2 is in progress, not complete.
If this fits the roadmap, I'm happy to open the implementation as small, separate PRs (backend + workspace first, then the manager). If you'd rather keep vendor backends out of tree, a pointer to the preferred extension point would help too.
Drafted with Claude Code for the kosa8 team.
All reactions