Repository navigation
Proposal: kosa8 Cloud as a community sandbox provider #8339
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). The PR template asks for a discussion before a non-trivial feature, so I'd like to check scope before opening a PR.Why. DeerFlow already has community sandbox providers (AIO, OpenSandbox, the provisioner/Kubernetes mode, and several open provider PRs). Teams that already run their agents' code on kosa8 Cloud would like DeerFlow threads to run there too, without a Docker host of their own.
What it would add. A community provider,
deerflow.community.kosa8:Kosa8SandboxProvider, selected withsandbox.useinconfig.yaml:httpxthe harness already depends on, so no new dependency.(user_id, thread_id), a warm pool per Gateway process, reclaim only by the same scope after a liveness probe, and outputs copied back to the thread's outputs directory under the same limits and rules.ttl_sdeletes it.kosa8_api_key,kosa8_base_url), so a key left inconfig.yamlfor another provider is never sent to kosa8.backend/docs/CONFIGURATION.mdanddocs/guide/sandbox.md, and aconfig.example.yamlblock.The implementation is on a branch: https://github.com/drvt69talati/deer-flow/tree/feat/kosa8-sandbox-provider (it needs a rebase on
mainbefore a PR).kosa8 Cloud is a paid service (plans from $29/month; no free tier). SOC 2 is in progress, not complete.
Questions: is a new community sandbox provider in scope for DeerFlow right now? And would you prefer it in-tree under
deerflow/community/, or as a separate package loaded throughsandbox.use?Drafted with Claude Code for the kosa8 team.
All reactions