# boxes.dev > Give every coding agent its own cloud computer. Bring your Codex or Claude subscription, start agents from Slack and Linear, and manage them from your desktop, phone, or terminal. ## Pages - [boxes.dev: Cloud computers for Claude Code and Codex](https://boxes.dev/): Give every coding agent its own cloud computer. Bring your Codex or Claude subscription, start agents from Slack and Linear, and manage them from your desktop, phone, or terminal. - [boxes.dev for teams](https://boxes.dev/teams): Give your engineering team a shared cloud development environment for coding agents, with every devbox starting from one maintained Template box. - [About boxes.dev](https://boxes.dev/about): boxes.dev is built by Nick Bushak and Drew Regitsky, who met at MIT and built Gem together. - [Security at boxes.dev](https://boxes.dev/security): How boxes.dev approaches security, what we recommend for development credentials, and how to report a vulnerability. - [Install the Slack integration | boxes.dev](https://boxes.dev/slack-integration-install): Connect your team's Slack workspace to boxes.dev, link your Slack user, and start coding agents from Slack with an automation. - [Set up Tailscale for boxes.dev](https://boxes.dev/tailscale-admin-setup): A guide for Tailscale administrators preparing a company tailnet so boxes.dev project machines can join it. - [Support | boxes.dev](https://boxes.dev/support): Email boxes.dev with support questions, account requests, or anything else you need help with. - [Privacy Policy | boxes.dev](https://boxes.dev/privacy): How boxes.dev collects, uses, and protects your personal information. - [Terms of Service | boxes.dev](https://boxes.dev/terms): The terms that govern your use of boxes.dev. ## Guides - [Guides to running coding agents in the cloud](https://boxes.dev/guides): How to run Claude Code and Codex in the cloud, keep agents working after you close your laptop, run agents in parallel, and check in from your phone. - [How to run Claude Code in the cloud: your options compared](https://boxes.dev/guides/run-claude-code-in-the-cloud): Run Claude Code in the cloud with Anthropic's cloud sessions, a VM you manage, a managed platform, or Boxes.dev: where each runs and what it costs. - [How to run Codex in the cloud: your options compared](https://boxes.dev/guides/run-codex-in-the-cloud): Run Codex in the cloud with OpenAI's cloud environments, a VM you manage, a managed platform, or Boxes.dev: where each runs and what it costs. - [Best cloud coding agents in 2026](https://boxes.dev/guides/best-cloud-coding-agents): Compare cloud coding agents from Anthropic, OpenAI, Cursor, Devin, Boxes.dev, and more: where each agent runs, how it's set up, and what it costs. - [Run coding agents in parallel: worktrees or cloud machines](https://boxes.dev/guides/run-coding-agents-in-parallel): Run Claude Code and Codex in parallel with Git worktrees or a cloud machine per task: what worktrees separate, what they share, and how to avoid clashes. - [Keep coding agents running after you close your laptop](https://boxes.dev/guides/keep-coding-agents-running-after-you-close-your-laptop): Why Claude Code and Codex stop when your laptop sleeps, how to keep a Mac awake, and how to keep agents working on a VM, in the cloud, or on boxes.dev. - [Run Claude Code and Codex from your phone](https://boxes.dev/guides/run-claude-code-and-codex-from-your-phone): Use Claude Code and Codex from your phone: the Claude and ChatGPT apps, Remote Control, SSH with tmux, and Boxes.dev's iOS and Android apps compared. - [Cloud development environments for AI coding agents](https://boxes.dev/guides/cloud-development-environments-for-ai-coding-agents): What AI coding agents need from a cloud development environment, how Codespaces, Coder, Ona, CloudCLI, and Boxes.dev compare, and how to choose. ## Comparisons - [Boxes.dev and alternatives: coding agent tools compared](https://boxes.dev/compare): Compare boxes.dev with alternatives for running Claude Code, Codex, and other coding agents, from desktop apps to cloud platforms. - [Boxes.dev vs Claude Code: running Claude Code in the cloud](https://boxes.dev/compare/claude-code): Claude Code's cloud sessions run in fresh VMs and count toward Claude plan limits. Boxes.dev runs Claude Code and Codex on copies of your dev environment. - [Boxes.dev vs Codex: an OpenAI Codex Cloud alternative](https://boxes.dev/compare/codex): Codex Cloud runs tasks in VMs from environments Codex sets up, kept up to 7 days. Boxes.dev runs Codex and Claude Code on copies of your full environment. - [Boxes.dev vs Conductor: a cloud Conductor alternative](https://boxes.dev/compare/conductor): Conductor runs parallel agents in worktrees on your Mac, with paid cloud workspaces. Boxes.dev gives each task a cloud copy of your full dev environment. - [Boxes.dev vs Cursor: a Cursor alternative for cloud agents](https://boxes.dev/compare/cursor): Cursor is an AI code editor whose own agent also runs in cloud VMs. Boxes.dev runs Claude Code and Codex on full cloud copies of your dev environment. - [Boxes.dev vs Devin: a Devin AI alternative](https://boxes.dev/compare/devin): Devin is an autonomous agent that works in cloud VMs from one organization snapshot. Boxes.dev runs Claude Code and Codex on copies of your environment. - [Boxes.dev vs Amp: an Amp Orbs alternative](https://boxes.dev/compare/amp): Amp runs its own agent on a cloud orb for each thread. Boxes.dev runs Claude Code and Codex on full, isolated copies of your dev environment. - [Boxes.dev vs T3 Code: a T3 Code alternative in the cloud](https://boxes.dev/compare/t3-code): T3 Code is a free, open-source app for coding agents on computers you run. Boxes.dev runs Claude Code and Codex on cloud copies of your dev environment. - [Boxes.dev vs Superset: a Superset alternative in the cloud](https://boxes.dev/compare/superset): Superset runs many CLI agents in Git worktrees on computers you run. Boxes.dev runs Claude Code and Codex on cloud copies of your dev environment. - [Boxes.dev vs Orca: an Orca agent IDE alternative](https://boxes.dev/compare/orca): Orca is a free, open-source agent IDE for CLI agents in worktrees on computers you run. Boxes.dev runs Claude Code and Codex on managed cloud machines. - [Boxes.dev vs GitHub Copilot: a cloud agent alternative](https://boxes.dev/compare/github-copilot): Copilot's cloud agent works on GitHub in a fresh environment per task, for up to 59 minutes. Boxes.dev runs Claude Code and Codex on copies of your setup. - [Boxes.dev vs Factory AI: a Factory Droid alternative](https://boxes.dev/compare/factory): Factory's Droids work on long-lived Droid Computers, with worktrees for parallel tasks. Boxes.dev gives each task a full copy of your dev environment. - [Boxes.dev vs Replicas: a Replicas.dev alternative](https://boxes.dev/compare/replicas): Replicas runs eight coding agents in cloud VMs built from hook scripts. Boxes.dev runs Claude Code and Codex on full copies of your dev environment. - [Boxes.dev vs Niteshift: a Niteshift alternative](https://boxes.dev/compare/niteshift): Niteshift builds task environments from repo config and tests changes in a browser. Boxes.dev runs each task on a full copy of your dev environment. - [Boxes.dev vs Tembo: a Tembo alternative](https://boxes.dev/compare/tembo): Tembo runs seven coding agents on cloud VMs that end with each session. Boxes.dev runs Claude Code and Codex on lasting copies of your dev environment. - [Boxes.dev vs Vorflux: a Vorflux alternative](https://boxes.dev/compare/vorflux): Vorflux takes tickets to tested pull requests with its own agent, paid from credits. Boxes.dev runs Claude Code and Codex on copies of your dev setup. - [Boxes.dev vs AQ: an aq.dev alternative for coding agents](https://boxes.dev/compare/aq): AQ runs agent CLIs in Git worktrees on a shared team machine that teammates watch live. Boxes.dev gives each task a full copy of your dev environment. - [Boxes.dev vs Ellipsis: an Ellipsis alternative](https://boxes.dev/compare/ellipsis): Ellipsis runs Claude Code and Codex agents defined in YAML in sandboxes of up to an hour. Boxes.dev gives each task a lasting copy of your dev setup. - [Boxes.dev vs CloudCLI: a CloudCLI alternative](https://boxes.dev/compare/cloudcli): CloudCLI runs five coding agents in cloud containers you set up. Boxes.dev runs Claude Code and Codex on copies of your running dev environment. - [Boxes.dev vs Continuum: a Continuum alternative](https://boxes.dev/compare/continuum): Continuum is a free app for coding agents on computers you run. Boxes.dev runs Claude Code and Codex on cloud copies of your dev environment. ## Help center - [Help center | boxes.dev](https://boxes.dev/help): Guides for setting up projects on boxes.dev, working with Codex and Claude Code on cloud devboxes, reviewing changes, and managing your team. - [How boxes.dev works | boxes.dev](https://boxes.dev/help/how-boxes-works): Learn where your agents run and how your development environment gets to the cloud. - [Choose how to set up your project | boxes.dev](https://boxes.dev/help/choose-project-setup): Choose a setup path for your code and development environment. - [Set up from a local folder | boxes.dev](https://boxes.dev/help/local-folder-setup): Review your laptop's files and configuration, then prepare your app in the cloud. - [Create a project from GitHub | boxes.dev](https://boxes.dev/help/github-project-setup): Clone your repositories, configure Git access, and get your app running. - [Start from a Team Template | boxes.dev](https://boxes.dev/help/start-from-team-template): Create your own project from an environment prepared by your team. - [Your first task | boxes.dev](https://boxes.dev/help/first-task): Ask an agent for a small change, test it, and save your work. - [Tour the desktop app | boxes.dev](https://boxes.dev/help/desktop-tour): Find your conversations, inspect changes, and test your app with the desktop tools. - [Connect Codex and Claude | boxes.dev](https://boxes.dev/help/connect-agents): Connect an agent account or API key, change accounts, and repair sign-in problems. - [Start and continue a thread | boxes.dev](https://boxes.dev/help/start-and-continue-threads): Start a task, send follow-ups while an agent works, and recover interrupted messages. - [Give useful instructions | boxes.dev](https://boxes.dev/help/give-useful-instructions): Describe a task, set its boundaries, and save instructions for future work. - [Models, reasoning, and usage | boxes.dev](https://boxes.dev/help/models-reasoning-usage): Choose agent settings and understand context capacity, usage limits, and recorded activity. - [Agent settings | boxes.dev](https://boxes.dev/help/agent-settings): Keep Claude and Codex settings the same on every box in a project. - [Keep Codex working toward a goal | boxes.dev](https://boxes.dev/help/goals-and-longer-tasks): Set an objective Codex can pursue across responses, control progress, and review the result. - [Branch a conversation | boxes.dev](https://boxes.dev/help/branch-conversation): Continue from an earlier response in a new chat, with shared files or a separate devbox. - [Agent permissions | boxes.dev](https://boxes.dev/help/agent-permissions): Allow boxes.dev actions and choose when agents need approval for edits and commands. - [Organize and share threads | boxes.dev](https://boxes.dev/help/organize-and-share-threads): Find your work, share conversations with teammates, and restore archived chats. - [Notifications | boxes.dev](https://boxes.dev/help/notifications): Choose when agent replies notify you and keep track of unread conversations. - [Use the agent’s terminal view | boxes.dev](https://boxes.dev/help/agent-terminal-view): Open Codex or Claude's interactive terminal inside the desktop app and return to the graphical view. - [Preview your app | boxes.dev](https://boxes.dev/help/preview-your-app): Test an app running on a devbox in your laptop's browser. - [Review a page with your agent | boxes.dev](https://boxes.dev/help/browser-review): Point to page elements and send feedback from the browser you share with your agent. - [Browse, edit, and transfer files | boxes.dev](https://boxes.dev/help/files-and-transfers): Read and edit devbox files, or copy files between a devbox and your laptop. - [Review code and leave comments | boxes.dev](https://boxes.dev/help/code-review-comments): Send your agent feedback on file content or code changes. - [Commit, push, and open a pull request | boxes.dev](https://boxes.dev/help/commit-push-pull-request): Save reviewed changes in Git, share them with your team, and handle pull request follow-ups. - [Review branch history and add repositories | boxes.dev](https://boxes.dev/help/branches-history-repositories): Inspect commits and add repositories to a devbox or your project's starting environment. - [Create and manage devboxes | boxes.dev](https://boxes.dev/help/manage-devboxes): Start work on a separate cloud machine and save your changes before deleting it. - [Sleep, wake, and recover a devbox | boxes.dev](https://boxes.dev/help/sleep-wake-recover): Understand automatic sleep, return to paused work, and recover a machine that is stuck. - [Use the terminal | boxes.dev](https://boxes.dev/help/use-terminal): Run commands on your cloud machine and manage terminal tabs and sessions. - [Update your Template box and snapshots | boxes.dev](https://boxes.dev/help/template-box-snapshots): Change and save the environment that new devboxes will start from. - [Startup, teardown, and maintenance | boxes.dev](https://boxes.dev/help/lifecycle-and-maintenance): Prepare and clean up individual devboxes, and keep your saved environment current. - [Environment files and secrets | boxes.dev](https://boxes.dev/help/environment-files): Manage environment variables centrally and deliver them to your project's machines. - [Shared project storage | boxes.dev](https://boxes.dev/help/shared-project-storage): Share selected files across a project's machines. - [Share a running app | boxes.dev](https://boxes.dev/help/share-running-app): Create a public HTTPS link when someone else needs to try an app running on your devbox. - [Project URLs | boxes.dev](https://boxes.dev/help/project-urls): Keep one callback, webhook, or API address while choosing which devboxes receive requests. - [Create an automation | boxes.dev](https://boxes.dev/help/create-automation): Save instructions for a repeatable agent task, then test and activate it. - [Schedules and run history | boxes.dev](https://boxes.dev/help/automation-schedules-history): Schedule tasks, inspect runs, send results to Slack, and choose when to clean up devboxes. - [Trigger an automation through the API | boxes.dev](https://boxes.dev/help/automation-api): Start an agent task from a script or service and check whether its thread is ready. - [Work from Slack | boxes.dev](https://boxes.dev/help/slack): Connect Slack, send an agent a request, and continue in the same Slack thread. - [Work from Linear | boxes.dev](https://boxes.dev/help/linear): Delegate issues to an agent and review its progress and results in Linear. - [Connect GitHub | boxes.dev](https://boxes.dev/help/connect-github): Set up repository access and the GitHub CLI, and choose the identity on your commits. - [Add MCP servers | boxes.dev](https://boxes.dev/help/mcp-servers): Connect service tools to Codex and Claude, choose their scope, and manage sign-ins. - [Connect an outside assistant | boxes.dev](https://boxes.dev/help/remote-assistants): Let an assistant find, read and control your boxes.dev threads in projects you choose. - [Install agent plugins | boxes.dev](https://boxes.dev/help/agent-plugins): Find and install plugins, update them, and choose how they reach your devboxes. - [Connect AWS | boxes.dev](https://boxes.dev/help/aws): Connect your company sign-in and choose the AWS accounts and permissions your project will use. - [Connect Tailscale | boxes.dev](https://boxes.dev/help/tailscale): Let your cloud machines reach private company services through Tailscale. - [Team access and roles | boxes.dev](https://boxes.dev/help/team-access-and-roles): Understand member and admin access, shared environments, and team network settings. - [Create and publish a Team Template | boxes.dev](https://boxes.dev/help/create-team-template): Prepare, test, and save a shared environment for teammates' new projects. - [Maintain a Team Template | boxes.dev](https://boxes.dev/help/maintain-team-template): Update the shared environment, automate maintenance, and manage team scripts. - [Required member files and values | boxes.dev](https://boxes.dev/help/member-files-and-values): Define personal configuration requirements and supply the files or values your project needs. - [Use boxes.dev on your phone | boxes.dev](https://boxes.dev/help/use-mobile): Start tasks, reply to agents, inspect files, and manage devboxes away from your computer. - [Install and use the CLI | boxes.dev](https://boxes.dev/help/use-cli): Install dvb on your computer to continue agent conversations and open cloud terminals. - [Set up a project with your local agent | boxes.dev](https://boxes.dev/help/local-agent-setup): Ask Codex or Claude Code on your laptop to prepare and upload your development environment. - [Agent command reference | boxes.dev](https://boxes.dev/help/agent-command-reference): Automate devbox and thread tasks with commands for your computer and managed machines. - [Plans, seats, and box-hours | boxes.dev](https://boxes.dev/help/plans-and-box-hours): Compare plan allowances, machine usage rates, and limits on projects and awake devboxes. - [Manage billing and usage | boxes.dev](https://boxes.dev/help/billing-and-usage): Review machine usage, assign paid seats, and manage payment and prepaid credits. - [Your data and credentials | boxes.dev](https://boxes.dev/help/data-and-credentials): Understand what you upload, what code on your machines can access, and what deletion removes. - [Troubleshooting | boxes.dev](https://boxes.dev/help/troubleshooting): Find recovery steps for setup, agents, machines, GitHub, and integration failures. - [Contact support | boxes.dev](https://boxes.dev/help/contact-support): Report a problem or send feedback to the boxes.dev team. - [Glossary | boxes.dev](https://boxes.dev/help/glossary): Look up the terms used in boxes.dev.