Linux microVM sandboxes for AI agents: run commands, files, processes, pause and wake.
The SDKs, CLI, MCP server and agent integrations for Runtime: sandboxes for AI agents. Each sandbox is a Firecracker microVM with its own Linux kernel, started from one call.
npm install withruntime # TypeScript SDK, the `runtime` CLI and the MCP server
pip install withruntime # Python SDK, sync and async
import { Sandbox } from "withruntime";
await using sbx = await Sandbox.create();
const result = await sbx.exec("python3 -c 'print(6 * 7)'");
console.log(result.exitCode, result.stdout);
from withruntime import Sandbox
with Sandbox.create() as sbx:
result = sbx.exec("python3 -c 'print(6 * 7)'")
print(result.exit_code, result.stdout)
The client reads RUNTIME_API_KEY, or the connection npx withruntime login
saved on this machine. A new account starts on a free trial with no card. The
quickstart takes it from there.
| Path | What it is |
|---|---|
packages/cloud-sdk | The TypeScript SDK, the runtime CLI and the MCP server: withruntime on npm |
sdks/python | The Python SDK: withruntime on PyPI |
sdks/python/integrations/langchain-withruntime | LangChain and Deep Agents sandbox backend |
sdks/go, sdks/java, sdks/ruby | The Go, Java and Ruby SDKs |
integrations/pydantic-ai, integrations/google-adk | Pydantic AI and Google ADK integrations |
integrations/claude-code, codex, cursor, gemini-cli, vscode, windsurf | Skills, rules and MCP settings for coding agents |
packages/cloud-guide/docs | The guides served at withruntime.com/docs, which the SDK tests check samples against |
bun test in packages/cloud-sdk and python3 -m unittest discover -s tests
in sdks/python run here as they are. The suites that start Runtime's API
server in-process, including all of the Go, Java and Ruby tests, run in
Runtime's main repository before each release.
Each release copies the SDKs here from Runtime's main repository, so each commit here is one copy, named after the versions in its source; a copy made before those versions reach npm and PyPI says so. Issues are welcome. A pull request is reviewed here and carried into the next release with its author credited.
Apache-2.0. See LICENSE.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y withruntimeMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"com-withruntime-runtime": {
"command": "npx",
"args": [
"-y",
"withruntime"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceRuntime Cloud works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.