Repository navigation
feat(workspace): add boxd as a sandboxed workspace backend #3979
MichielMAnalytics
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 work on boxd (https://boxd.sh?ref=agentscope). boxd runs full Ubuntu microVMs with a persistent disk. A machine can hibernate and wake with its disk and memory intact, and it does not expire on its own.
I'd like to add boxd as a workspace backend, built the same way as the E2B and Daytona backends:
BoxdWorkspaceonSandboxedWorkspaceBase,BoxdBackendonBackendBase, andBoxdWorkspaceManagernext to the E2B manager.workspace_id: the workspace id goes into a machine label, andinitialize()looks the machine up by that label.close()hibernates the machine, the way E2B pauses its sandbox. The nextinitialize()wakes it with skills,.mcpand sessions still on disk.boxdSDK goes in a new optional extraworkspace-boxd, imported lazily.BOXD_API_KEYis set, a README line, and a companion page in agentscope-ai/docs.A boxd machine has no lease to renew (the topic of #3208). An idle machine hibernates on its own and wakes on the next call.
Would you take this as a PR? If yes, I'm happy to follow a roadmap issue and any design notes you have.
All reactions