44 Guides Step-by-step Updated May 2026

Guides

Step-by-step playbooks for everything you'd want to do with Sandbox Platform — SSH into your sandbox, give Claude Code its own machine, run 50 browsers in parallel, deploy AI employees that work overnight. Each guide is self-contained, copy-paste ready, and ships with the actual cost numbers.

Product

The feature pages — what the product does, shown with real screenshots and video from the live app. Two layers: the computer, and what you put on it. See the product overview →

Getting Started

Start here if you're new. The mental model and your first 10 minutes.

Setting Up Your Claw
The two credentials a personal AI assistant needs — a Telegram bot token from BotFather and a model API key from Anthropic or OpenAI. Both are yours; here is exactly how to get each and where to paste it.
AI Coding Agents Need Computers: The 2026 Landscape
Claude Code, Codex, Devin, Cursor, and dozens of open-source agents are writing code autonomously. But most run on your laptop. Here's why that's a problem.
Your First AI Employee: From Laptop to Cloud in 10 Minutes
Give the agent its own machine and watch what changes. 10 minutes from "I should try this" to "my agent is running on a cloud computer, working while I make coffee."
What Changes When Your Agent Has a Dedicated Machine
Overnight runs. Parallel execution. Disposable environments. Persistent workspaces. The mental model shift from "AI tool I use" to "AI employee I manage."
Put an AI Coding Agent on a Cron
Hand a coding agent a job and a schedule, and it shows up, does the work on your own box, and leaves you a reviewable result. Managed task workers, from create to review.
The Employee Who Never Logs Off
Always-on AI agents on your own server: a name, a channel, memory that persists, credentials that never leave your box. How a persistent employee differs from a stateless bot.
Give Your AI Agents a Shared Brain
Coordination on your own box: a shared filesystem, an event log, mailboxes and leases, so a team of agents works together without a peer-to-peer mess.
Build a Team of AI Agents That Actually Coordinate
One agent is a worker; a team is a company. How a shared filesystem, a real-time comms line, and safe locks let a manager and workers build together, and how the claws team builder composes the roster.
Building Blocks, Not Bespoke Scripts
How anything gets set up on your box: declarative building-block steps that install their own dependencies, on any machine, without assuming what is already there.
Claude Code Today, Codex Tomorrow
Why your AI worker should not be locked to one brain: harness-as-config, model-key sovereignty, and the roadmap for swapping the agent behind the job.
Framework Integrations

Wire sandboxes into the agent framework you already use.

Browser Automation

Headless Chrome over CDP, fan-out at 50 browsers, vision-model agents.

AI Employee Use Cases

End-to-end agents that do real work. Cost numbers included.

Managing AI Employees

Hire, onboard, supervise, and review your AI workforce. The operational layer most teams skip.

Industry Deployments

Vertical-specific AI employees with CLAUDE.md templates, compliance notes, and real ROI tables.

Architecture & Operations

How to run agents at scale — events, persistence, parallelism, multi-tenancy, budgets, security.

Running 100 AI Agents in Parallel
Map, Pool, and Pipeline patterns for parallel agent fleets. Full Python with Anthropic SDK, asyncio orchestration, cost math (per-sandbox-second billing), and an end-to-end 200-file PR review example.
Warm Pools: Sub-Second Agent Start
Cold start = 30-45s. Warm pool start = 200-800ms. Snapshot architecture, static/predictive/on-demand pre-warming strategies, break-even cost model, production Dockerfile spec.
Multi-Tenant AI Agent SaaS
Process isolation, filesystem isolation, egress allowlists, per-tenant CLAUDE.md injection, cost attribution, SOC 2 controls table. How Cursor, GitHub Copilot Workspace, and Linear do it.
Persistent Workspaces: AI Agent State
An AI employee that remembers. Persistent filesystem, checkpoint/resume, workspace versioning, tmux sessions that survive reboots. The difference between a tool and a coworker.
Custom Docker Images for AI Agents
Three reference Dockerfiles (coding agent, browser agent, vertical agent), GitHub Actions CI/CD, multi-stage builds, CVE scanning with Trivy, warm-pool pairing. Stop fighting cold-start dependency installs.
Event-Driven Agent Architecture: Deep Dive
The full technical reference: SQS fan-out, SNS topics, webhook ingress, dead-letter queues, exactly-once semantics, and the choreography vs orchestration tradeoff for agent fleets.
AI Agent File I/O: Datasets and Results
Mount S3 buckets, stream large datasets, write structured results back. Efficient I/O patterns for agents that process millions of rows, thousands of files, or multi-GB outputs.
Event-Driven Agents: Work That Starts Itself
AI employees react to emails, calendar reminders, Slack messages, and deadlines — just like human employees. Webhooks, cron, SQS, calendar-aware scheduling.
The Always-On Agent
An always-on agent has an office — files from last week, notes from yesterday, context that makes it better each day. Persistent sandboxes, checkpoint/resume, tmux sessions. Cost: $0.96/day.
Cost Control: Your AI Workforce Budget
50 AI employees running 4 hours/day: $1,320/month total. Per-department budgets, auto-stop, spending caps, and the monthly report template. The guide you forward to your CFO.
Task Design for AI Agents
The #1 reason AI agents fail isn't the model — it's the task description. "Make this better" fails. "Sort column C, add a SUM, export as PDF" succeeds in 30 seconds.
Security for AI Agents in Production
Network isolation, egress control, short-lived credentials, audit logging. What happens when an agent goes rogue? The guide your security team needs.
Strategy

The bigger picture — economics, market landscape, what comes next.

Stop reading. Start building.

Every guide here is something you can copy-paste-run today. Get an account, generate a key, ssh in.

Open Dashboard