Dormice skill
A skill that teaches a coding agent to use Dormice sandboxes: acquire by key, run commands, move files and set lifecycle.
- 1,879 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The agent runs arbitrary commands and writes files in a sandbox, and the API token grants control of the whole sandbox fleet.
- Server installation goes through `curl | bash` as root.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/dormiceDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent runs arbitrary commands and writes files in a sandbox, and the API token grants control of the whole sandbox fleet.
- Server installation goes through `curl | bash` as root.
This is third-party code. Review the repository files before installing.
What it does
Dormice is a self-hosted sandbox platform for AI agents with an E2B-compatible API. A sandbox is not deleted after work: an idle one gradually moves through the states `active`, `frozen`, `stopped` and `archived`, and any new call brings it back. The `dormice` skill in a single file, `skills/dormice/SKILL.md`, explains to an agent how to work with this. The whole model fits in the `acquireSandbox(name)` call. It is idempotent: the same name always leads to the same sandbox, whether it was created, frozen, stopped or archived. The skill then shows three ways to drive it: the official E2B SDKs, the native HTTP API with a TypeScript client and the `dor` CLI. The agent runs commands, moves files both ways and tunes the lifecycle policy. The skill applies when an agent must connect to a Dormice server, run untrusted or generated code in isolation, get a persistent workspace or migrate an application off E2B.
Who it is for. Agent developers who run or plan to deploy their own Dormice server and need a long-lived isolated workspace for agent code.
Good fit when
- Model-generated code runs in an isolated sandbox rather than on the developer's machine.
- An agent's working directory stays in place after freezing, stopping and host reboot.
- An E2B application is moved to your own server by changing two URLs and the key prefix.
- Files go into a sandbox and the result comes out through the `dor` CLI or an SDK.
- Idle sandboxes should freeze and wake in a fraction of a second.
Not a fit when
- The platform is not deployed: the skill covers working with an existing Dormice server, not installing it.
- Production operation is needed: the author calls the project early development, not ready for production.
- Template builds with `e2b template build` are required: that is not implemented.
Example request
Connect to my Dormice server, create a sandbox my-agent, run `python3 -c "print(6 * 7)"` in it and show the exit code.Limitations
The author calls the project early development: nothing in it is ready for production yet. Installation on a bare Ubuntu or Debian x86_64 server is done as root with one `curl | bash` command. The native `@dormice/sdk` client was not yet published to npm at the time of the README. Templates are created as a Docker image and registered with `dor template add`, and the E2B template build is not implemented. Access is protected by one API token and both ports listen only on `127.0.0.1`, so another machine needs an SSH tunnel or a reverse proxy.
How to disable. Delete the `dormice` skill directory from the agent's skills folder and start a new session. The Dormice server itself stays and is removed separately.
FAQ
How do I install the skill?
Run `npx skills add BitMiracle-AI/Dormice`. The skill is a single file, `skills/dormice/SKILL.md`.
What does acquireSandbox do?
It idempotently returns a sandbox by name: creates it, wakes a frozen one, starts a stopped one or restores an archived one. Other operations answer 404 for an unknown name.
How do I migrate an application off E2B?
The `e2b` package works with Dormice unmodified: set the server's `apiUrl` and `sandboxUrl` and a key with the `e2b_` prefix. No code changes are needed.
What is kept after a sandbox stops?
The disk, not the container, is the sandbox's body: files survive freezing, stopping, daemon restart and host reboot. Only `destroySandbox` loses data.
How do I install the server itself?
As root on a clean Ubuntu or Debian x86_64 host: `curl -fsSL https://raw.githubusercontent.com/BitMiracle-AI/Dormice/main/deploy/install.sh | bash`. `dor doctor` runs at the end of the install.
Discussion
No questions or reviews yet.
Related
SkillsA self-hosted agent code sandbox on Kubernetes: REST API, MCP server, E2B compatibility and skills for managing it.
Isolated Linux microVMs for agent code: the official Vercel skill on the SDK, network rules and snapshots.
Agent Skill Manager
agent-skill-manager
A universal skill manager for coding agents: finds and installs skills, scanning them for shell calls, network access and credential leaks first
An SSH skill for Codex and Claude Code: remote commands, file transfer and tunnels with one JSON result and replay protection.
A CLI and skill for the Inspire compute platform: an agent creates notebooks, training jobs and services without web clicks.
A Nix and Home Manager module: skill sources are pinned in a flake and chosen SKILL.md folders are laid out into agent directories
README in short
The project runs on a machine you already pay for and charges nothing for every second a sandbox exists. An idle 1 GiB sandbox holds about 5 MiB of resident memory after freezing and wakes in roughly 50 ms.