# Boxes.dev

Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. The same evidence rules apply to Podium and its competitors, but they do not remove this conflict of interest.

Page: https://adecomparison.com/ade/boxes-dev/
Website: https://boxes.dev/
Research: covered

Method: https://adecomparison.com/method/

Rank by must-haves met, then preferences, then name. Read each finding's checked date. Findings stay published after their scheduled recheck. Checks over six months old may be outdated.

## boxes-dev:ACC-01

Finding: Boxes.dev distributes macOS/Linux desktop workbenches, iOS/Android apps and its own CLI for cloud threads. The homepage also lists web access; help documents browser project setup, Billing and Team Template administration, including creating a later GitHub project on a phone before continuing in the native app. Browser agent-chat parity is not established.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev browser and phone web client; Boxes.dev iOS and Android apps; Workstation dvb CLI and switchboard; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Minimum Linux/Android versions, browser support matrix and editor-extension distribution are not established in the client guides or public CLI package; desktop/mobile build source is unavailable.

Source: https://boxes.dev/
Locator: Manage your agents; Pricing; For Teams
Finding: The service runs native Claude Code and Codex on cloud computers with desktop, mobile, browser and CLI access. Teams pricing advertises SSO/SAML/OIDC, SCIM, audit logs and custom infrastructure; implementation, contract scope and enablement are not established by the marketing list.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/desktop-tour
Locator: Opening platform paragraph; Find your way around; tools and keyboard shortcuts
Finding: The desktop workbench is distributed for macOS and Linux. The main Mac build requires Apple Silicon and macOS 12 or later, with macOS 13 needed for the bundled PostgreSQL copy tools. Threads, folders, devbox groups, terminals, files, Git/Review and browser tools form its main workspace.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/use-mobile
Locator: Install and open a project; Start or continue a task; Review files and use a terminal
Finding: The iOS and Android apps open existing cloud projects. They can start and continue threads, answer questions and approvals, stop work, inspect files and diffs, batch code comments and use a terminal. The /m link is an app-install route, not proof of a mobile browser workbench. Initial environment preparation and some administration remain computer tasks.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/use-cli
Locator: Install and sign in; switchboard; native interfaces; Agent permissions
Finding: The product-owned dvb CLI is installable on macOS and Linux x64/arm64. It opens native agent interfaces, lists and reads threads, starts work, runs shell commands, manages machines, MCPs and permissions. Workstation sign-in is separate; managed machines use dvb-onbox instead. Claude input control transfers require confirmation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/choose-project-setup
Locator: Choose your starting point; Before you begin; Where setup starts
Finding: Users sign in and connect an agent, then use local-agent setup, the desktop local-folder wizard, a Team Template, or GitHub setup for subsequent projects. GitHub login is optional for local setup. Machine size is chosen at creation, applies across the project and is not resizable in place; each size includes 100 GB disk.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/notifications
Locator: Attention markers; desktop defaults; quiet hours; mobile push
Finding: Completion, failures and input requests can notify on desktop/mobile, link to the thread and maintain unread markers across devices. Quiet hours and pause suppress alerts but preserve pending questions. Desktop defaults notify when unfocused; sound defaults on. Muting completion does not mute input requests.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/team-access-and-roles
Locator: Members/Admins; remove member; shared environments; static egress
Finding: Admin and Member roles have distinct template, membership, integration and billing privileges. Each member owns projects/devboxes and personal credentials. Shared workbench access is read-only. Removal offers transfer/keep/delete workflows, stops running work and pauses automations. Static egress requires enablement and is limited to configured public TCP destinations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

Source: https://apps.apple.com/us/app/boxes-dev/id6758927946
Locator: Compatibility; Version History; account prerequisite
Finding: The public iOS/iPadOS listing requires version 16.4 or later, distributes version 1.0.1135 and requires an existing Boxes.dev account. Its seller is ND Innovations LLC. Store download price alone does not establish free compute access.
Retrieved: 2026-11-21

Source: https://play.google.com/store/apps/details?id=dev.boxes
Locator: About this app; Updated on
Finding: The public Android listing is dated updated 2026-11-19 and offers thread history, follow-ups and notifications. Its description still calls account access early access/waitlist, unlike the current self-serve website/help. Successful signup and region-specific eligibility were not tested.
Retrieved: 2026-11-21

Source: https://registry.npmjs.org/@boxes-dev/cli/1.0.1135
Locator: package.json os/cpu/license/bin; tarball standalone-manifest.json and scripts/postinstall.mjs
Finding: The exact npm release is UNLICENSED, exports dvb/dvbd and distributes darwin/linux x64/arm64 archives with SHA-256 checks. The inspected shell wrapper executes the installed standalone runtime. Tarball SHA-256 d41fe950a7504c2019a999276e535a8d36b84b0aa8fbe735e0f4fa7ab61df844. No upstream Git commit is published.
Retrieved: 2026-11-21

## boxes-dev:ACC-02

Finding: Native Codex and Claude Code are the documented harnesses. Codex can use OpenAI or saved OpenRouter, Vercel or compatible custom Responses providers. Provider/model choice does not establish additional coding harnesses.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev iOS and Android apps; Workstation dvb CLI and switchboard; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The public connection guides establish Codex/Claude, not a general harness adapter API. The closed server and non-CLI clients prevent an exhaustive implementation audit.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/use-cli
Locator: Install and sign in; switchboard; native interfaces; Agent permissions
Finding: The product-owned dvb CLI is installable on macOS and Linux x64/arm64. It opens native agent interfaces, lists and reads threads, starts work, runs shell commands, manages machines, MCPs and permissions. Workstation sign-in is separate; managed machines use dvb-onbox instead. Claude input control transfers require confirmation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/models-reasoning-usage
Locator: Model and effort pickers; provider restrictions; Inspect recorded activity
Finding: Model, reasoning and speed are configurable per thread within supported choices. Claude Ultracode workflows are harness functionality. Saved conversation activity includes tokens, calls and context charts, not reconciled dollar spend. Other activity is one combined series, missing history is identified and provider quotas are separate from machine box-hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

## boxes-dev:ACC-03

Finding: Users bring their native ChatGPT/Claude subscription login or provider API account. Boxes.dev bills compute separately and does not sell agent tokens. Multiple saved accounts and optional API fallback have explicit restart and billing consequences.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev iOS and Android apps; Workstation dvb CLI and switchboard; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Exact eligible provider subscription tiers and arbitrary local-model behavior are not enumerated. Model endpoint compatibility remains provider-dependent; hosted authentication internals are closed.

Source: https://boxes.dev/
Locator: Manage your agents; Pricing; For Teams
Finding: The service runs native Claude Code and Codex on cloud computers with desktop, mobile, browser and CLI access. Teams pricing advertises SSO/SAML/OIDC, SCIM, audit logs and custom infrastructure; implementation, contract scope and enablement are not established by the marketing list.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/models-reasoning-usage
Locator: Model and effort pickers; provider restrictions; Inspect recorded activity
Finding: Model, reasoning and speed are configurable per thread within supported choices. Claude Ultracode workflows are harness functionality. Saved conversation activity includes tokens, calls and context charts, not reconciled dollar spend. Other activity is one combined series, missing history is identified and provider quotas are separate from machine box-hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/choose-project-setup
Locator: Choose your starting point; Before you begin; Where setup starts
Finding: Users sign in and connect an agent, then use local-agent setup, the desktop local-folder wizard, a Team Template, or GitHub setup for subsequent projects. GitHub login is optional for local setup. Machine size is chosen at creation, applies across the project and is not resizable in place; each size includes 100 GB disk.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:ACC-04

Finding: Onboarding prepares a managed cloud environment through a local agent, desktop upload wizard or Team Template. Subsequent GitHub setup is also documented. Uploads need review and machine usage is separate from agent authentication.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev browser and phone web client; Workstation dvb CLI and switchboard; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The setup guides and published setup prompts do not explicitly settle all no-Git/no-remote cases or provide a public BYO VPS product installer. Hosted provisioning source is unavailable.

Source: https://boxes.dev/help/choose-project-setup
Locator: Choose your starting point; Before you begin; Where setup starts
Finding: Users sign in and connect an agent, then use local-agent setup, the desktop local-folder wizard, a Team Template, or GitHub setup for subsequent projects. GitHub login is optional for local setup. Machine size is chosen at creation, applies across the project and is not resizable in place; each size includes 100 GB disk.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/local-folder-setup
Locator: Review the setup scans; Check the final bundle; Fine-tune what gets copied
Finding: Read-only local scans prepare an upload bundle. The user selects repositories, local edits, untracked files, config, databases and optional history before upload. SSH, GitHub credentials and signing choices are explicit. Remote agents prepare the template; snapshots initialize later work.
Retrieved: 2026-11-21

## boxes-dev:ACC-05

Finding: Boxes.dev has a scripting CLI, secret-authenticated automation run/status API and OAuth remote MCP service. Their operations differ: the launch API does not return final agent results and MCP cannot answer approval dialogs.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Workstation dvb CLI and switchboard; Boxes.dev automations, Slack, Linear and remote MCP; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The documented automation API is narrower than the marketing API example. A standalone SDK and stable API compatibility guarantee are not established; the managed backend is closed.

Source: https://boxes.dev/help/use-cli
Locator: Install and sign in; switchboard; native interfaces; Agent permissions
Finding: The product-owned dvb CLI is installable on macOS and Linux x64/arm64. It opens native agent interfaces, lists and reads threads, starts work, runs shell commands, manages machines, MCPs and permissions. Workstation sign-in is separate; managed machines use dvb-onbox instead. Claude input control transfers require confirmation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-command-reference
Locator: Resource commands; thread start, read, send, interrupt, wait, artifacts and permissions
Finding: Scripting commands expose project, machine and thread inventory, creation, reading, follow-up, interruption and observation with explicit IDs and JSON. On-box tools have their own permissioned operations for agent delegation, messages, artifacts and settings. These IDs describe threads and devboxes, not a documented native issue database.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/remote-assistants
Locator: Connect your assistant; Find or start a task; Stop current work
Finding: The remote MCP endpoint is https://api.boxes.dev/mcp. OAuth grants selected projects and read, task-control, event or settings scopes. It can inspect, start and follow up on the owner's threads and interrupt current work. Teammates' shared threads and approval dialogs are excluded; stops preserve queued work and event subscriptions need renewal within 24 hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-api
Locator: Idempotency; configurable input; existing targets; accepted run; status endpoint
Finding: An activated automation exposes secret-authenticated POST run/wake operations and GET launch status. Configurable requests select prompt, model and targets; identical idempotency keys replay the original run while changed input conflicts. Existing-devbox threads share files, not conversation. Status reports launch/delivery, not final output; use the thread for results.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

Source: https://boxes.dev/changelog
Locator: November 19, 2026, Version 1.0.1135; November 17, Version 1.0.1134
Finding: Release 1.0.1135 is dated 2026-11-19 and adds HTML review, first-thread archiving and optional devbox/tab sidebar layout; PR follow-ups ignore late edits of bot status comments. The prior release adds Codex GPT-6.2-Sol/Astra and web Team Template setup. These are release dates, not retrieval dates.
Retrieved: 2026-11-21

Source: https://registry.npmjs.org/@boxes-dev/dvb-runtime/-/dvb-runtime-1.0.1135.tgz
Locator: package/package.json; dist/bin/dvb.mjs lines 300360-302304; dist/product-docs/references/agent-tools.md and onbox-agent-tools.md
Finding: The readable released bundle implements thread start/control/read/observation command routing and ships agent-tool documentation. It is UNLICENSED and includes React/Ink CLI dependencies. Pin is npm version 1.0.1135, tarball SHA-256 213b030dae6a0fb83fd7861ab63ecc467f40a9ad16e7f2dd2613438af936fa18; no public upstream Git commit is exposed, so this distribution inspection is recorded as documented evidence rather than commit-pinned source-inspected. It cannot establish closed server enforcement or desktop/mobile implementation.
Retrieved: 2026-11-21

## boxes-dev:ACC-06

Finding: The product manages external MCP servers and supported agent plugins, while repository instructions and some account plugins remain harness-owned. Destination and authorization determine whether a tool reaches future or existing devboxes.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Managed MCP/plugins and harness instructions are documented, but arbitrary extension compatibility and enforcement depend on closed services and the underlying agents.

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/local-folder-setup
Locator: Review the setup scans; Check the final bundle; Fine-tune what gets copied
Finding: Read-only local scans prepare an upload bundle. The user selects repositories, local edits, untracked files, config, databases and optional history before upload. SSH, GitHub credentials and signing choices are explicit. Remote agents prepare the template; snapshots initialize later work.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/mcp-servers
Locator: Add and authorize a server; project and agent scope
Finding: Boxes.dev manages MCP connections for Codex and Claude, including separate OAuth sign-ins and project scope. An MCP client connection adds external tools to agents and is separate from the remote MCP service that exposes Boxes.dev to outside assistants.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-plugins
Locator: Destinations; managed plugins; Update or remove
Finding: Plugins install skills and tools for Codex or Claude. Supported verified public GitHub plugins can be managed at a pinned commit across a project. Local/private/per-machine plugins stay template-local. ChatGPT account plugins and inherited harness sign-ins have different scopes.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/give-useful-instructions
Locator: Ask for checks; Save instructions for future work
Finding: Repository AGENTS.md and CLAUDE.md retain versioned guidance. Project Agent guidance is applied to newly prepared devboxes, with Team Template guidance first in managed projects; changing it does not update existing sessions. Verification and delivery boundaries are prompt instructions, not proof of enforced gates.
Retrieved: 2026-11-21

## boxes-dev:ACC-07

Finding: The versioned public product docs identify an Electron desktop main-process log. Full desktop and mobile build sources were not found; native mobile marketing and Expo push transport do not establish the mobile UI framework.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-05-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev iOS and Android apps
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The published runtime documentation identifies the desktop Electron log; full desktop/mobile application build source is unavailable. Native mobile marketing does not establish a UI framework.

Source: https://boxes.dev/privacy
Locator: Sections 2, 4, 5, 7, 9 and 10
Finding: The policy discloses account/device/session data, masked replay, Convex, Cloudflare, Expo, OpenAI title generation, Amplitude and Sentry. Replay retention is generally up to 30 days; other retention/backups lack fixed durations. International processing may occur in the US/other provider locations. Third-party agent terms are separate. No training promise is general to all customer content; narrower Google/Slack commitments must stay scoped.
Retrieved: 2026-11-21

Source: https://registry.npmjs.org/@boxes-dev/dvb-runtime/-/dvb-runtime-1.0.1135.tgz
Locator: package/dist/product-docs/references/security-and-data.md, Desktop app logs, line 344
Finding: The versioned product documentation identifies the desktop main-process log as ~/.devbox/logs/desktop-electron-main.log. This supports an Electron desktop implementation, without access to its full build source or proof of mobile framework. Same package SHA-256 213b030dae6a0fb83fd7861ab63ecc467f40a9ad16e7f2dd2613438af936fa18; upstream Git commit unavailable.
Retrieved: 2026-11-21

## boxes-dev:PLAN-01

Finding: Prompts, Slack and Linear can start work. Linear issues keep their external identifiers and return progress/results through Agent Sessions; this is an integration, not evidence of a native Boxes.dev issue tracker.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev automations, Slack, Linear and remote MCP; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Linear remains authoritative for external issues. Public help and CLI distributions do not establish a separate Boxes.dev issue entity, issue-field sync contract or tracker edit parity; the backend is closed.

Source: https://boxes.dev/help/agent-command-reference
Locator: Resource commands; thread start, read, send, interrupt, wait, artifacts and permissions
Finding: Scripting commands expose project, machine and thread inventory, creation, reading, follow-up, interruption and observation with explicit IDs and JSON. On-box tools have their own permissioned operations for agent delegation, messages, artifacts and settings. These IDs describe threads and devboxes, not a documented native issue database.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/slack
Locator: Team connection; linked account; start and continue requests
Finding: A team admin connects Slack and each member links an account/automation. Mentions and thread replies route work to the linked owner's cloud environment and return updates. Slack context and attachments reach the agent; this integration does not establish native issue management or unrestricted shared prompting.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/linear
Locator: Start and follow a task; Send a follow-up; Attach work products
Finding: Linear Agent Sessions provide issue context and stable external issue identifiers. Progress and final answers return to Linear and result URLs can be attached. Repeated session events reuse a thread. Only the linked Linear account can follow up or stop; other people's replies are refused. Linear remains the issue tracker.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/start-and-continue-threads
Locator: Queue versus Steer; Stop; drafts; attachments; import
Finding: Codex and Claude support queued follow-ups and steering with different interruption semantics. Stopping a response can leave queued work able to run. Drafts and failed-start recovery retain requests; attachments include files, folders and model-dependent images. Reusing a devbox shares its files, while changing Codex provider needs a new thread.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

## boxes-dev:PLAN-02

Finding: Saved thread goals retain an objective across agent responses. Codex can edit or pause a goal while keeping the thread. A goal and prompt instructions do not establish a structured acceptance-criteria or versioned project plan system.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Goals and conversation history are documented. A structured acceptance-criteria object, dedicated plan editor and full attributable plan revisions are not established by the goal guide or closed service.

Source: https://boxes.dev/help/goals-and-longer-tasks
Locator: Set a useful goal; Follow progress; Review before finishing; Claude goals
Finding: A saved goal keeps an agent working across responses. Codex goals can be edited, paused or resumed in the same thread and expose blocked and budget-limited states. Claude goals have different controls and a 4,000-character condition limit. Goal achieved still requires human review; it is not an independent acceptance gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/start-and-continue-threads
Locator: Queue versus Steer; Stop; drafts; attachments; import
Finding: Codex and Claude support queued follow-ups and steering with different interruption semantics. Stopping a response can leave queued work able to run. Drafts and failed-start recovery retain requests; attachments include files, folders and model-dependent images. Reusing a devbox shares its files, while changing Codex provider needs a new thread.
Retrieved: 2026-11-21

## boxes-dev:PLAN-04

Finding: Repository instructions, saved project guidance and shared /project files provide reusable context. The open-beta share redirects Claude project memory across devboxes; Codex can use files there without moving its state or transcripts.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Shared files and Claude memory are documented; source provenance, stale-memory detection and managed cross-harness memory correction are not established by the guides or closed backend.

Source: https://boxes.dev/help/agent-plugins
Locator: Destinations; managed plugins; Update or remove
Finding: Plugins install skills and tools for Codex or Claude. Supported verified public GitHub plugins can be managed at a pinned commit across a project. Local/private/per-machine plugins stay template-local. ChatGPT account plugins and inherited harness sign-ins have different scopes.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/give-useful-instructions
Locator: Ask for checks; Save instructions for future work
Finding: Repository AGENTS.md and CLAUDE.md retain versioned guidance. Project Agent guidance is applied to newly prepared devboxes, with Team Template guidance first in managed projects; changing it does not update existing sessions. Verification and delivery boundaries are prompt instructions, not proof of enforced gates.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/shared-project-storage
Locator: Share Claude project memory; Understand persistence; consistency cautions
Finding: The open-beta /project share outlives devboxes but is deleted with the project. Claude automatic project memory uses /project/.claude/memory unless its settings override that. Codex can use ordinary shared files but its state/transcripts are not moved. Writes can conflict, and the share does not provide strict consistency or multi-writer file locks.
Retrieved: 2026-11-21

## boxes-dev:PLAN-05

Finding: Agents can inspect machine files and use configured external tools, while people can search workspace files and attach images/files. No architectural consistency or spec-conflict enforcement is established.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Files search, attachments and MCP provide inputs. Public help and shipped CLI code do not establish a proprietary repository index, architecture conflict detection or review-time requirement enforcement; server implementation is unavailable.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/models-reasoning-usage
Locator: Model and effort pickers; provider restrictions; Inspect recorded activity
Finding: Model, reasoning and speed are configurable per thread within supported choices. Claude Ultracode workflows are harness functionality. Saved conversation activity includes tokens, calls and context charts, not reconciled dollar spend. Other activity is one combined series, missing history is identified and provider quotas are separate from machine box-hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/mcp-servers
Locator: Add and authorize a server; project and agent scope
Finding: Boxes.dev manages MCP connections for Codex and Claude, including separate OAuth sign-ins and project scope. An MCP client connection adds external tools to agents and is separate from the remote MCP service that exposes Boxes.dev to outside assistants.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-plugins
Locator: Destinations; managed plugins; Update or remove
Finding: Plugins install skills and tools for Codex or Claude. Supported verified public GitHub plugins can be managed at a pinned commit across a project. Local/private/per-machine plugins stay template-local. ChatGPT account plugins and inherited harness sign-ins have different scopes.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/start-and-continue-threads
Locator: Queue versus Steer; Stop; drafts; attachments; import
Finding: Codex and Claude support queued follow-ups and steering with different interruption semantics. Stopping a response can leave queued work able to run. Drafts and failed-start recovery retain requests; attachments include files, folders and model-dependent images. Reusing a devbox shares its files, while changing Codex provider needs a new thread.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/files-and-transfers
Locator: Workspace search; previews; uploads/downloads; conflict handling
Finding: Files searches filenames/text and edits current machine files with save/conflict indicators. It previews Markdown, images, videos, PDFs and HTML via Browser. Desktop transfers allow files up to 5 GiB; phone downloads allow 100 MB. Folder download requires an archive. Machine-local files are lost when the devbox is destroyed.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

## boxes-dev:COORD-01

Finding: Codex/Claude threads can run concurrently on separate devboxes or share a machine. Plans limit awake devboxes per user rather than proving a fixed session count or measured throughput.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Concurrency is documented, not measured. No hands-on runs were performed, and exact simultaneous throughput is not inferred from UI tabs or package code.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-api
Locator: Idempotency; configurable input; existing targets; accepted run; status endpoint
Finding: An activated automation exposes secret-authenticated POST run/wake operations and GET launch status. Configurable requests select prompt, model and targets; identical idempotency keys replay the original run while changed input conflicts. Existing-devbox threads share files, not conversation. Status reports launch/delivery, not final output; use the thread for results.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/notifications
Locator: Attention markers; desktop defaults; quiet hours; mobile push
Finding: Completion, failures and input requests can notify on desktop/mobile, link to the thread and maintain unread markers across devices. Quiet hours and pause suppress alerts but preserve pending questions. Desktop defaults notify when unfocused; sound defaults on. Muting completion does not mute input requests.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

## boxes-dev:COORD-02

Finding: Dispatch routes integration events to the linked human account and configured agent. API idempotency and Linear Agent Session reuse prevent duplicate launches within those paths, without establishing a general task-claim system.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev automations, Slack, Linear and remote MCP; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Linear owner routing and idempotency are bounded to those launch paths. A general shared task-claim queue or exclusive ownership mechanism is not established by public docs; the service is closed.

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/create-automation
Locator: Create, pause, activate, Run now and agent editing
Finding: Automations store prompt, agent and model settings and can be manual, scheduled, API, Slack or Linear driven. New automations begin paused and can be tested with Run now. Agents need approved temporary automation-editing permission to create or change them.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-api
Locator: Idempotency; configurable input; existing targets; accepted run; status endpoint
Finding: An activated automation exposes secret-authenticated POST run/wake operations and GET launch status. Configurable requests select prompt, model and targets; identical idempotency keys replay the original run while changed input conflicts. Existing-devbox threads share files, not conversation. Status reports launch/delivery, not final output; use the thread for results.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/linear
Locator: Start and follow a task; Send a follow-up; Attach work products
Finding: Linear Agent Sessions provide issue context and stable external issue identifiers. Progress and final answers return to Linear and result URLs can be attached. Repeated session events reuse a thread. Only the linked Linear account can follow up or stop; other people's replies are refused. Linear remains the issue tracker.
Retrieved: 2026-11-21

## boxes-dev:COORD-03

Finding: Boxes.dev supplies permissioned tools for agents to create workers, inspect threads, send messages and continue work. Agent-created devboxes are grouped under their creator. A universally available dedicated Coordinator role and automatic result acceptance remain unestablished.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Product tools permit permissioned worker creation, reading and messaging. A separate Coordinator entry is mentioned only when available; public docs do not establish universal access, automated acceptance or a complete retained role graph.

Source: https://boxes.dev/help/agent-command-reference
Locator: Resource commands; thread start, read, send, interrupt, wait, artifacts and permissions
Finding: Scripting commands expose project, machine and thread inventory, creation, reading, follow-up, interruption and observation with explicit IDs and JSON. On-box tools have their own permissioned operations for agent delegation, messages, artifacts and settings. These IDs describe threads and devboxes, not a documented native issue database.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-permissions
Locator: Create and read threads; Message other agents; temporary grants; Claude modes
Finding: Users can let agents create devboxes, read threads, message agents and pause/resume their own workers with scoped permissions. Both ends need messaging permission. Settings/template grants last three hours; certain integration actions require separate exact approval. Claude defaults to Full-access unless a custom policy applies, with Auto, Manual and Plan modes subject to model and machine support.
Retrieved: 2026-11-21

Source: https://registry.npmjs.org/@boxes-dev/dvb-runtime/-/dvb-runtime-1.0.1135.tgz
Locator: package/package.json; dist/bin/dvb.mjs lines 300360-302304; dist/product-docs/references/agent-tools.md and onbox-agent-tools.md
Finding: The readable released bundle implements thread start/control/read/observation command routing and ships agent-tool documentation. It is UNLICENSED and includes React/Ink CLI dependencies. Pin is npm version 1.0.1135, tarball SHA-256 213b030dae6a0fb83fd7861ab63ecc467f40a9ad16e7f2dd2613438af936fa18; no public upstream Git commit is exposed, so this distribution inspection is recorded as documented evidence rather than commit-pinned source-inspected. It cannot establish closed server enforcement or desktop/mobile implementation.
Retrieved: 2026-11-21

## boxes-dev:COORD-04

Finding: Vendor-owned automations run on recurrence, API or integration events without a prompt for each run. Capacity, overlap and delivery statuses have explicit limits and are distinct from agent completion.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev automations, Slack, Linear and remote MCP; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Capacity retries and skipped overlaps are documented; broader failure/retry guarantees and exact scheduler infrastructure are not exposed by the closed service.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/goals-and-longer-tasks
Locator: Set a useful goal; Follow progress; Review before finishing; Claude goals
Finding: A saved goal keeps an agent working across responses. Codex goals can be edited, paused or resumed in the same thread and expose blocked and budget-limited states. Claude goals have different controls and a 4,000-character condition limit. Goal achieved still requires human review; it is not an independent acceptance gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/create-automation
Locator: Create, pause, activate, Run now and agent editing
Finding: Automations store prompt, agent and model settings and can be manual, scheduled, API, Slack or Linear driven. New automations begin paused and can be tested with Run now. Agents need approved temporary automation-editing permission to create or change them.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-api
Locator: Idempotency; configurable input; existing targets; accepted run; status endpoint
Finding: An activated automation exposes secret-authenticated POST run/wake operations and GET launch status. Configurable requests select prompt, model and targets; identical idempotency keys replay the original run while changed input conflicts. Existing-devbox threads share files, not conversation. Status reports launch/delivery, not final output; use the thread for results.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/slack
Locator: Team connection; linked account; start and continue requests
Finding: A team admin connects Slack and each member links an account/automation. Mentions and thread replies route work to the linked owner's cloud environment and return updates. Slack context and attachments reach the agent; this integration does not establish native issue management or unrestricted shared prompting.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/linear
Locator: Start and follow a task; Send a follow-up; Attach work products
Finding: Linear Agent Sessions provide issue context and stable external issue identifiers. Progress and final answers return to Linear and result URLs can be attached. Repeated session events reuse a thread. Only the linked Linear account can follow up or stop; other people's replies are refused. Linear remains the issue tracker.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

## boxes-dev:COORD-05

Finding: Users can steer, queue, stop and continue agents, answer requests and receive alerts across devices. Stopping a response preserves queued follow-ups, which may start next; sleeping pauses the whole machine.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Stop/steer/queue and alerts are documented, but harness-specific waits and queued messages can outlive a stop. No guaranteed end-to-end cancellation of all future work is established.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/use-cli
Locator: Install and sign in; switchboard; native interfaces; Agent permissions
Finding: The product-owned dvb CLI is installable on macOS and Linux x64/arm64. It opens native agent interfaces, lists and reads threads, starts work, runs shell commands, manages machines, MCPs and permissions. Workstation sign-in is separate; managed machines use dvb-onbox instead. Claude input control transfers require confirmation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/remote-assistants
Locator: Connect your assistant; Find or start a task; Stop current work
Finding: The remote MCP endpoint is https://api.boxes.dev/mcp. OAuth grants selected projects and read, task-control, event or settings scopes. It can inspect, start and follow up on the owner's threads and interrupt current work. Teammates' shared threads and approval dialogs are excluded; stops preserve queued work and event subscriptions need renewal within 24 hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/goals-and-longer-tasks
Locator: Set a useful goal; Follow progress; Review before finishing; Claude goals
Finding: A saved goal keeps an agent working across responses. Codex goals can be edited, paused or resumed in the same thread and expose blocked and budget-limited states. Claude goals have different controls and a 4,000-character condition limit. Goal achieved still requires human review; it is not an independent acceptance gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/start-and-continue-threads
Locator: Queue versus Steer; Stop; drafts; attachments; import
Finding: Codex and Claude support queued follow-ups and steering with different interruption semantics. Stopping a response can leave queued work able to run. Drafts and failed-start recovery retain requests; attachments include files, folders and model-dependent images. Reusing a devbox shares its files, while changing Codex provider needs a new thread.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/notifications
Locator: Attention markers; desktop defaults; quiet hours; mobile push
Finding: Completion, failures and input requests can notify on desktop/mobile, link to the thread and maintain unread markers across devices. Quiet hours and pause suppress alerts but preserve pending questions. Desktop defaults notify when unfocused; sound defaults on. Muting completion does not mute input requests.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/sleep-wake-recover
Locator: Automatic sleep; timed checks; Reset; Reboot; recovery notice
Finding: Default inactivity sleep is about five minutes, configurable to 15/30/60. Active agents and bounded background protection can keep a box awake. Sleep saves memory/files but pauses work. Reset kills processes and retains files; reboot loses in-memory state. Recovery notices identify restored memory/files and snapshot time. There is no documented guaranteed lossless failover.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:COORD-06

Finding: The workbench groups threads by devbox, folders and creator, with work/unread/input indicators and searchable history. This is a fleet view of sessions, not established evidence of native epic dependencies or a measured multi-epic fixture.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Folders and grouped worker devboxes aid navigation, but public docs do not establish a multi-epic dependency/status model. No test fixture or live navigation measurement was run; app source is closed.

Source: https://boxes.dev/help/desktop-tour
Locator: Opening platform paragraph; Find your way around; tools and keyboard shortcuts
Finding: The desktop workbench is distributed for macOS and Linux. The main Mac build requires Apple Silicon and macOS 12 or later, with macOS 13 needed for the bundled PostgreSQL copy tools. Threads, folders, devbox groups, terminals, files, Git/Review and browser tools form its main workspace.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/notifications
Locator: Attention markers; desktop defaults; quiet hours; mobile push
Finding: Completion, failures and input requests can notify on desktop/mobile, link to the thread and maintain unread markers across devices. Quiet hours and pause suppress alerts but preserve pending questions. Desktop defaults notify when unfocused; sound defaults on. Muting completion does not mute input requests.
Retrieved: 2026-11-21

## boxes-dev:COORD-07

Finding: A simple prompt starts ordinary work, while goals, automation settings and per-thread agent controls support longer workflows. Agents may create workers through explicit grants; a complete epic/Coordinator workflow is not established.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Ordinary prompts and per-thread settings are documented. A formal epic workflow, universal coordinator access and complete retained role/results visualization are not established by public docs or available CLI code.

Source: https://boxes.dev/help/desktop-tour
Locator: Opening platform paragraph; Find your way around; tools and keyboard shortcuts
Finding: The desktop workbench is distributed for macOS and Linux. The main Mac build requires Apple Silicon and macOS 12 or later, with macOS 13 needed for the bundled PostgreSQL copy tools. Threads, folders, devbox groups, terminals, files, Git/Review and browser tools form its main workspace.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/models-reasoning-usage
Locator: Model and effort pickers; provider restrictions; Inspect recorded activity
Finding: Model, reasoning and speed are configurable per thread within supported choices. Claude Ultracode workflows are harness functionality. Saved conversation activity includes tokens, calls and context charts, not reconciled dollar spend. Other activity is one combined series, missing history is identified and provider quotas are separate from machine box-hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/goals-and-longer-tasks
Locator: Set a useful goal; Follow progress; Review before finishing; Claude goals
Finding: A saved goal keeps an agent working across responses. Codex goals can be edited, paused or resumed in the same thread and expose blocked and budget-limited states. Claude goals have different controls and a 4,000-character condition limit. Goal achieved still requires human review; it is not an independent acceptance gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-permissions
Locator: Create and read threads; Message other agents; temporary grants; Claude modes
Finding: Users can let agents create devboxes, read threads, message agents and pause/resume their own workers with scoped permissions. Both ends need messaging permission. Settings/template grants last three hours; certain integration actions require separate exact approval. Claude defaults to Full-access unless a custom policy applies, with Auto, Manual and Plan modes subject to model and machine support.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/start-and-continue-threads
Locator: Queue versus Steer; Stop; drafts; attachments; import
Finding: Codex and Claude support queued follow-ups and steering with different interruption semantics. Stopping a response can leave queued work able to run. Drafts and failed-start recovery retain requests; attachments include files, folders and model-dependent images. Reusing a devbox shares its files, while changing Codex provider needs a new thread.
Retrieved: 2026-11-21

## boxes-dev:RUN-01

Finding: Ordinary Boxes.dev coding work runs on vendor-managed Linux devboxes and continues after client disconnect. Local agents may prepare the initial upload, but those setup scans do not establish general local execution. Customer-hosted deployment remains a sales discussion.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Managed Linux devboxes and on-box agent tools; Boxes.dev desktop workbench for macOS and Linux; Boxes.dev browser and phone web client; Boxes.dev iOS and Android apps; Workstation dvb CLI and switchboard
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Current ordinary execution is managed cloud. Custom customer-infrastructure hosting is sales discussion only; specific regions, storage lifetime and a released self-hosted control plane are not established by public docs or closed hosting code.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/choose-project-setup
Locator: Choose your starting point; Before you begin; Where setup starts
Finding: Users sign in and connect an agent, then use local-agent setup, the desktop local-folder wizard, a Team Template, or GitHub setup for subsequent projects. GitHub login is optional for local setup. Machine size is chosen at creation, applies across the project and is not resizable in place; each size includes 100 GB disk.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/sleep-wake-recover
Locator: Automatic sleep; timed checks; Reset; Reboot; recovery notice
Finding: Default inactivity sleep is about five minutes, configurable to 15/30/60. Active agents and bounded background protection can keep a box awake. Sleep saves memory/files but pauses work. Reset kills processes and retains files; reboot loses in-memory state. Recovery notices identify restored memory/files and snapshot time. There is no documented guaranteed lossless failover.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/teams
Locator: Infrastructure options; Plans sized around your workflow
Finding: Custom pricing, hour pools and dedicated resources are available through discussion. The team brief says the vendor is open to hosting on customer infrastructure; it does not establish a downloadable self-hosted control plane.
Retrieved: 2026-11-21

## boxes-dev:RUN-02

Finding: A separate devbox isolates its own files, processes, local databases and ports. Several threads on the same devbox share those resources; shared project storage and external services intentionally cross machine boundaries. No hostile-code boundary or VM implementation is inferred.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Separate devbox files/processes are documented. VM/container implementation and hostile-code containment are not established by the accessible code; shared storage/services and delivered secrets remain reachable intentionally.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/shared-project-storage
Locator: Share Claude project memory; Understand persistence; consistency cautions
Finding: The open-beta /project share outlives devboxes but is deleted with the project. Claude automatic project memory uses /project/.claude/memory unless its settings override that. Codex can use ordinary shared files but its state/transcripts are not moved. Writes can conflict, and the share does not provide strict consistency or multi-writer file locks.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

## boxes-dev:RUN-03

Finding: Client reconnect and sleep preserve conversation/machine state, while Reset kills processes and Reboot loses memory. Snapshot recovery can restore older state and shows a notice. These mechanisms do not guarantee lossless task recovery after infrastructure failure.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Managed Linux devboxes and on-box agent tools; Boxes.dev desktop workbench for macOS and Linux; Workstation dvb CLI and switchboard
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The recovery guide gives reset/reboot and snapshot behavior but no guaranteed crash/restart replay, duplicate-free recovery or complete multi-day restoration after machine replacement. Closed worker/server code is unavailable.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/use-cli
Locator: Install and sign in; switchboard; native interfaces; Agent permissions
Finding: The product-owned dvb CLI is installable on macOS and Linux x64/arm64. It opens native agent interfaces, lists and reads threads, starts work, runs shell commands, manages machines, MCPs and permissions. Workstation sign-in is separate; managed machines use dvb-onbox instead. Claude input control transfers require confirmation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/sleep-wake-recover
Locator: Automatic sleep; timed checks; Reset; Reboot; recovery notice
Finding: Default inactivity sleep is about five minutes, configurable to 15/30/60. Active agents and bounded background protection can keep a box awake. Sleep saves memory/files but pauses work. Reset kills processes and retains files; reboot loses in-memory state. Recovery notices identify restored memory/files and snapshot time. There is no documented guaranteed lossless failover.
Retrieved: 2026-11-21

## boxes-dev:RUN-04

Finding: Prepared template snapshots copy dependencies and services to fresh devboxes, with lifecycle scripts and managed environment values. Per-box ports avoid local collisions; external shared systems still require deliberate setup.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Managed Linux devboxes and on-box agent tools; Boxes.dev desktop workbench for macOS and Linux
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Snapshots and lifecycle scripts prepare environments; arbitrary dependency repair, cache correctness and automatic reconciliation of shared external services are not established by public docs or the closed runtime.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/choose-project-setup
Locator: Choose your starting point; Before you begin; Where setup starts
Finding: Users sign in and connect an agent, then use local-agent setup, the desktop local-folder wizard, a Team Template, or GitHub setup for subsequent projects. GitHub login is optional for local setup. Machine size is chosen at creation, applies across the project and is not resizable in place; each size includes 100 GB disk.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-settings
Locator: Project JSON/TOML; synchronization; validation; team inheritance
Finding: Claude JSON and Codex TOML settings synchronize to project machines. Running boxes update within a minute; sleeping boxes on wake. Some settings require a new session. Repository settings take precedence. Concurrent saves require loading the latest values; plugins and MCPs have separate management pages.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/shared-project-storage
Locator: Share Claude project memory; Understand persistence; consistency cautions
Finding: The open-beta /project share outlives devboxes but is deleted with the project. Claude automatic project memory uses /project/.claude/memory unless its settings override that. Codex can use ordinary shared files but its state/transcripts are not moved. Writes can conflict, and the share does not provide strict consistency or multi-writer file locks.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/sleep-wake-recover
Locator: Automatic sleep; timed checks; Reset; Reboot; recovery notice
Finding: Default inactivity sleep is about five minutes, configurable to 15/30/60. Active agents and bounded background protection can keep a box awake. Sleep saves memory/files but pauses work. Reset kills processes and retains files; reboot loses in-memory state. Recovery notices identify restored memory/files and snapshot time. There is no documented guaranteed lossless failover.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/lifecycle-and-maintenance
Locator: Startup; teardown; template maintenance and GitHub watches
Finding: Project startup, teardown and template-maintenance scripts prepare and maintain environments. Template snapshots and managed Team Template versions feed future devboxes. Lifecycle commands are environment automation rather than enforced product-spec or test acceptance.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/environment-files
Locator: Environment files; member overrides; propagation
Finding: Boxes.dev supplies configured environment files and variables to project machines with team/member scopes. Delivered values are readable by software and agents with machine access; changing or removing a managed value does not revoke credentials or erase unrelated copies.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

## boxes-dev:RUN-05

Finding: Limits include per-user awake capacity, billing/credit blocks, provider quotas and goal budgets. Background protection and command timeouts differ by harness; they are not a universal task budget.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Managed Linux devboxes and on-box agent tools; Boxes.dev automations, Slack, Linear and remote MCP
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Documented budgets and sleep/background limits are scoped, not a universal task deadline. General turn limits and provider retry policy across all agents are not established; hosted execution code is closed.

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/models-reasoning-usage
Locator: Model and effort pickers; provider restrictions; Inspect recorded activity
Finding: Model, reasoning and speed are configurable per thread within supported choices. Claude Ultracode workflows are harness functionality. Saved conversation activity includes tokens, calls and context charts, not reconciled dollar spend. Other activity is one combined series, missing history is identified and provider quotas are separate from machine box-hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/goals-and-longer-tasks
Locator: Set a useful goal; Follow progress; Review before finishing; Claude goals
Finding: A saved goal keeps an agent working across responses. Codex goals can be edited, paused or resumed in the same thread and expose blocked and budget-limited states. Claude goals have different controls and a 4,000-character condition limit. Goal achieved still requires human review; it is not an independent acceptance gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/sleep-wake-recover
Locator: Automatic sleep; timed checks; Reset; Reboot; recovery notice
Finding: Default inactivity sleep is about five minutes, configurable to 15/30/60. Active agents and bounded background protection can keep a box awake. Sleep saves memory/files but pauses work. Reset kills processes and retains files; reboot loses in-memory state. Recovery notices identify restored memory/files and snapshot time. There is no documented guaranteed lossless failover.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:RUN-06

Finding: Thread activity, machine resource meters, usage charts and automation launch reasons expose operational state. Launch Ready and an idle agent do not prove a task delivered its result.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The product exposes run launch reasons and thread/usage activity. Cross-layer task/board consistency, traces, responsiveness and success-rate measurements are not established by public docs; no measurements were performed.

Source: https://boxes.dev/help/models-reasoning-usage
Locator: Model and effort pickers; provider restrictions; Inspect recorded activity
Finding: Model, reasoning and speed are configurable per thread within supported choices. Claude Ultracode workflows are harness functionality. Saved conversation activity includes tokens, calls and context charts, not reconciled dollar spend. Other activity is one combined series, missing history is identified and provider quotas are separate from machine box-hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/remote-assistants
Locator: Connect your assistant; Find or start a task; Stop current work
Finding: The remote MCP endpoint is https://api.boxes.dev/mcp. OAuth grants selected projects and read, task-control, event or settings scopes. It can inspect, start and follow up on the owner's threads and interrupt current work. Teammates' shared threads and approval dialogs are excluded; stops preserve queued work and event subscriptions need renewal within 24 hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/notifications
Locator: Attention markers; desktop defaults; quiet hours; mobile push
Finding: Completion, failures and input requests can notify on desktop/mobile, link to the thread and maintain unread markers across devices. Quiet hours and pause suppress alerts but preserve pending questions. Desktop defaults notify when unfocused; sound defaults on. Muting completion does not mute input requests.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/sleep-wake-recover
Locator: Automatic sleep; timed checks; Reset; Reboot; recovery notice
Finding: Default inactivity sleep is about five minutes, configurable to 15/30/60. Active agents and bounded background protection can keep a box awake. Sleep saves memory/files but pauses work. Reset kills processes and retains files; reboot loses in-memory state. Recovery notices identify restored memory/files and snapshot time. There is no documented guaranteed lossless failover.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:RUN-07

Finding: Boxes.dev separates per-thread token/provider quota charts from hourly machine box-hour history. Those measurements are not a reconciled per-task dollar bill and do not establish child/epic cost aggregation.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Token/quota and compute charts are documented separately. Per-task/child/epic dollar reconciliation, cross-harness aggregation, usage export and universal budget alerts are not established by the help or closed billing service.

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/models-reasoning-usage
Locator: Model and effort pickers; provider restrictions; Inspect recorded activity
Finding: Model, reasoning and speed are configurable per thread within supported choices. Claude Ultracode workflows are harness functionality. Saved conversation activity includes tokens, calls and context charts, not reconciled dollar spend. Other activity is one combined series, missing history is identified and provider quotas are separate from machine box-hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:RUN-08

Finding: Per-user awake-devbox caps and fixed machine resources constrain compute. Scheduled capacity retries and idle-machine sleep are configurable, with skipped overlaps. No shared verification deduplication or fairness guarantee is established.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Managed Linux devboxes and on-box agent tools; Boxes.dev automations, Slack, Linear and remote MCP
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Per-user machine capacity and bounded scheduled retries are documented. Fleet fairness, per-host dispatch optimization and deduplicated verification are not established by public docs or closed scheduler code.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/start-and-continue-threads
Locator: Queue versus Steer; Stop; drafts; attachments; import
Finding: Codex and Claude support queued follow-ups and steering with different interruption semantics. Stopping a response can leave queued work able to run. Drafts and failed-start recovery retain requests; attachments include files, folders and model-dependent images. Reusing a devbox shares its files, while changing Codex provider needs a new thread.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/sleep-wake-recover
Locator: Automatic sleep; timed checks; Reset; Reboot; recovery notice
Finding: Default inactivity sleep is about five minutes, configurable to 15/30/60. Active agents and bounded background protection can keep a box awake. Sleep saves memory/files but pauses work. Reset kills processes and retains files; reboot loses in-memory state. Recovery notices identify restored memory/files and snapshot time. There is no documented guaranteed lossless failover.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:TEAM-01

Finding: Shared workbench links are read-only, but an owner can authorize linked teammates to send instructions to the same agent through Slack. This route uses the owner's credentials and compute allowance, identifies each sender and applies owner-selected Steer/Queue behavior. Both users need active membership in the same team and linked Slack accounts.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev browser and phone web client; Boxes.dev iOS and Android apps; Boxes.dev automations, Slack, Linear and remote MCP; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Shared-view links remain read-only, while owner-authorized teammates can prompt the same agent through Slack. Formal concurrent-input conflict guarantees, live presence, native issue discussion and exact plan-specific two-person trial entitlements are not established by the public guides; the application/server source is closed.
Slack teammate access defaults to No one and must be granted by the owner. In private channels the owner must remain a member; read-only sharing links themselves do not grant agent control.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/team-access-and-roles
Locator: Members/Admins; remove member; shared environments; static egress
Finding: Admin and Member roles have distinct template, membership, integration and billing privileges. Each member owns projects/devboxes and personal credentials. Shared workbench access is read-only. Removal offers transfer/keep/delete workflows, stops running work and pauses automations. Static egress requires enablement and is limited to configured public TCP destinations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/transfer-thread-to-teammate
Locator: Before transfer; How your work moves; failure handling
Finding: An idle Codex/Claude thread can transfer to a teammate with a matching template or repository. History and packaged Git changes move to a new devbox using recipient credentials. Existing environment files are excluded; missing extra data depends on agent packaging. The source is archived after success; live processes are not transferred.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/slack
Locator: Follow up in the same Slack thread; Let teammates start work in your project; private-channel and owner authorization rules
Finding: Owners can authorize selected or any linked teammates to start work and send follow-ups in linked Slack threads, including tasks the owner started. Both people must be active on the same Boxes.dev team with linked Slack accounts. No one is the default and teammates cannot grant themselves access. Follow-ups target the same agent and identify their sender; active work receives Steer unless the owner chooses Queue. Work uses the owner's environment, credentials and usage. Private-channel restrictions also apply after launch.
Retrieved: 2026-11-21

## boxes-dev:TEAM-02

Finding: Documented Admin and Member roles separate template, membership, integration and billing rights. Personal credentials remain per member. Enterprise SSO/SCIM are advertised separately from these documented controls.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Documented Admin/Member controls; SSO/SCIM only advertised for custom Teams arrangements
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev browser and phone web client; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Admin/Member rights are documented. SSO/SCIM and enterprise controls are advertised but no detailed plan-specific enforcement/enablement contract or public implementation was available.

Source: https://boxes.dev/
Locator: Manage your agents; Pricing; For Teams
Finding: The service runs native Claude Code and Codex on cloud computers with desktop, mobile, browser and CLI access. Teams pricing advertises SSO/SAML/OIDC, SCIM, audit logs and custom infrastructure; implementation, contract scope and enablement are not established by the marketing list.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/team-access-and-roles
Locator: Members/Admins; remove member; shared environments; static egress
Finding: Admin and Member roles have distinct template, membership, integration and billing privileges. Each member owns projects/devboxes and personal credentials. Shared workbench access is read-only. Removal offers transfer/keep/delete workflows, stops running work and pauses automations. Static egress requires enablement and is limited to configured public TCP destinations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

## boxes-dev:TEAM-03

Finding: Product permissions gate worker, messaging and settings operations, while harness modes govern commands/edits. Temporary grants and public preview revocation have documented lifetimes; neither is a general deployment approval system.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Product operation grants and Claude modes are documented separately. Exact network/secret/merge policy enforcement across every harness is not established by closed server/worker code.

Source: https://boxes.dev/help/agent-permissions
Locator: Create and read threads; Message other agents; temporary grants; Claude modes
Finding: Users can let agents create devboxes, read threads, message agents and pause/resume their own workers with scoped permissions. Both ends need messaging permission. Settings/template grants last three hours; certain integration actions require separate exact approval. Claude defaults to Full-access unless a custom policy applies, with Auto, Manual and Plan modes subject to model and machine support.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/share-running-app
Locator: Public links; stopping sharing
Finding: A devbox port can be exposed by a public preview link. Anyone with the URL can use it until sharing stops. Revocation blocks new requests and closes public WebSockets within 30 seconds but cannot erase downloaded responses or close unrelated access paths.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

## boxes-dev:TEAM-04

Finding: Conversation history, attributed teammate-agent messages and automation launch settings retain useful context. Copy transcript exports Markdown. The public sources do not establish an immutable audit log with retention and integrity guarantees.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Saved transcripts and launch settings are documented. No complete immutable attributed audit stream, retention guarantee or full action export is established; enterprise audit logs are marketing-only.

Source: https://boxes.dev/
Locator: Manage your agents; Pricing; For Teams
Finding: The service runs native Claude Code and Codex on cloud computers with desktop, mobile, browser and CLI access. Teams pricing advertises SSO/SAML/OIDC, SCIM, audit logs and custom infrastructure; implementation, contract scope and enablement are not established by the marketing list.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/remote-assistants
Locator: Connect your assistant; Find or start a task; Stop current work
Finding: The remote MCP endpoint is https://api.boxes.dev/mcp. OAuth grants selected projects and read, task-control, event or settings scopes. It can inspect, start and follow up on the owner's threads and interrupt current work. Teammates' shared threads and approval dialogs are excluded; stops preserve queued work and event subscriptions need renewal within 24 hours.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-permissions
Locator: Create and read threads; Message other agents; temporary grants; Claude modes
Finding: Users can let agents create devboxes, read threads, message agents and pause/resume their own workers with scoped permissions. Both ends need messaging permission. Settings/template grants last three hours; certain integration actions require separate exact approval. Claude defaults to Full-access unless a custom policy applies, with Auto, Manual and Plan modes subject to model and machine support.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

## boxes-dev:TEAM-05

Finding: Git/Review and Files guide review through changed files, line/range comments and a single feedback batch. Mobile review and keyboard shortcuts are documented; exact-revision approval and measured review quality are not.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

File/diff comment navigation is documented. Review effort, missed-evidence rate and a required independent reviewer role are not established by docs and were not measured.

Source: https://boxes.dev/help/desktop-tour
Locator: Opening platform paragraph; Find your way around; tools and keyboard shortcuts
Finding: The desktop workbench is distributed for macOS and Linux. The main Mac build requires Apple Silicon and macOS 12 or later, with macOS 13 needed for the bundled PostgreSQL copy tools. Threads, folders, devbox groups, terminals, files, Git/Review and browser tools form its main workspace.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/use-mobile
Locator: Install and open a project; Start or continue a task; Review files and use a terminal
Finding: The iOS and Android apps open existing cloud projects. They can start and continue threads, answer questions and approvals, stop work, inspect files and diffs, batch code comments and use a terminal. The /m link is an app-install route, not proof of a mobile browser workbench. Initial environment preparation and some administration remain computer tasks.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/code-review-comments
Locator: Comment on file/diff; Review and send the batch; Check the revision
Finding: Line and range comments from Files or Git/Review collect into one Code review attachment for the agent, including phone comments. These are not GitHub PR comments. File/range/PR references preserve context, but line contents can change; reviewers must check the revision. This is feedback, not a durable exact-revision approval gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

## boxes-dev:TEAM-06

Finding: An idle owned thread can be transferred to a teammate with compatible project code. History and packaged changes arrive on a new devbox using the recipient's credentials. This preserves conversation context but is not live runtime takeover.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Idle thread transfer packages files into a recipient environment. Ongoing process takeover, full secret/runtime equivalence and lossless cross-harness transfer are not established by this workflow or closed implementation.

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/team-access-and-roles
Locator: Members/Admins; remove member; shared environments; static egress
Finding: Admin and Member roles have distinct template, membership, integration and billing privileges. Each member owns projects/devboxes and personal credentials. Shared workbench access is read-only. Removal offers transfer/keep/delete workflows, stops running work and pauses automations. Static egress requires enablement and is limited to configured public TCP destinations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/transfer-thread-to-teammate
Locator: Before transfer; How your work moves; failure handling
Finding: An idle Codex/Claude thread can transfer to a teammate with a matching template or repository. History and packaged Git changes move to a new devbox using recipient credentials. Existing environment files are excluded; missing extra data depends on agent packaging. The source is archived after success; live processes are not transferred.
Retrieved: 2026-11-21

## boxes-dev:SHIP-01

Finding: Threads can retain diffs, attached files, screenshots and published media, while Files and previews expose machine outputs. Download or push work before destroying the devbox; archived conversation alone does not retain its filesystem.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Files, attachments and published media have different retention. A revision-bound cross-task artifact gallery and complete child-review result retention are not established by public docs or closed storage services.

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/automation-schedules-history
Locator: Capacity and overlap behavior; run states; cleanup; Slack output
Finding: Vendor schedules support recurrence and timezone, optional idle-machine sleep and bounded capacity retries. Overlapping manual/scheduled launches can skip. API, Slack and Linear events are independent. Run ready means launch success, not task completion. History retains launch settings and archived conversations; cleanup deletes machine files and has explicit safeguards.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/files-and-transfers
Locator: Workspace search; previews; uploads/downloads; conflict handling
Finding: Files searches filenames/text and edits current machine files with save/conflict indicators. It previews Markdown, images, videos, PDFs and HTML via Browser. Desktop transfers allow files up to 5 GiB; phone downloads allow 100 MB. Folder download requires an archive. Machine-local files are lost when the devbox is destroyed.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/share-running-app
Locator: Public links; stopping sharing
Finding: A devbox port can be exposed by a public preview link. Anyone with the URL can use it until sharing stops. Revocation blocks new requests and closes public WebSockets within 30 seconds but cannot erase downloaded responses or close unrelated access paths.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

## boxes-dev:SHIP-02

Finding: The guides ask users to request tests and review results. Git UI blocks commits with unresolved conflicts and pull-and-push requires a successful pull; these controls do not establish mandatory test, spec or independent-review gates.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Prompts request checks and Git controls enforce some repository state. Required tests/lint/types/CI/independent review or persistent-spec gates are not established as product-wide policy; closed server enforcement is unavailable.

Source: https://boxes.dev/help/give-useful-instructions
Locator: Ask for checks; Save instructions for future work
Finding: Repository AGENTS.md and CLAUDE.md retain versioned guidance. Project Agent guidance is applied to newly prepared devboxes, with Team Template guidance first in managed projects; changing it does not update existing sessions. Verification and delivery boundaries are prompt instructions, not proof of enforced gates.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/goals-and-longer-tasks
Locator: Set a useful goal; Follow progress; Review before finishing; Claude goals
Finding: A saved goal keeps an agent working across responses. Codex goals can be edited, paused or resumed in the same thread and expose blocked and budget-limited states. Claude goals have different controls and a 4,000-character condition limit. Goal achieved still requires human review; it is not an independent acceptance gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/agent-permissions
Locator: Create and read threads; Message other agents; temporary grants; Claude modes
Finding: Users can let agents create devboxes, read threads, message agents and pause/resume their own workers with scoped permissions. Both ends need messaging permission. Settings/template grants last three hours; certain integration actions require separate exact approval. Claude defaults to Full-access unless a custom policy applies, with Auto, Manual and Plan modes subject to model and machine support.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

## boxes-dev:SHIP-03

Finding: Git/Review integrates staging, commits, branches, pushes and GitHub pull requests. Optional follow-ups handle failed checks, review feedback and conflicts, with explicit pause and owner-routing rules.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Integrated GitHub workflow is documented. Git worktree management is not established as a Boxes.dev workspace feature; devbox copies are separate machines, and harness shell commands are not product state.

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/branches-history-repositories
Locator: Branch history; repository selector; branch operations
Finding: The workbench lists repository history, branch and commit ranges and repositories within a project. Branch operations are separate from devbox filesystem isolation. Git history is the revision record; the product does not establish arbitrary native issue dependencies.
Retrieved: 2026-11-21

## boxes-dev:SHIP-04

Finding: The workbench can merge a GitHub pull request with the connected user's permissions and supported GitHub merge rules. PR creation, merging and production deployment remain separate; no general product release/deploy authority is established.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

GitHub merge UI and user credentials are documented. A product-owned release/deploy authority model and approval bound to the exact candidate revision are not established by help or closed backend.

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

## boxes-dev:SHIP-05

Finding: Optional commit trailers connect changes to their originating thread, and PR follow-ups retain the responsible conversation and merged notice. The UI can revert selected edits. Build/deploy receipts and stale approval invalidation remain unknown.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Thread/PR/commit links and revert are documented. Build/deployment receipts and automatic invalidation of product approvals after edits are not established by help or closed storage code.

Source: https://boxes.dev/help/code-review-comments
Locator: Comment on file/diff; Review and send the batch; Check the revision
Finding: Line and range comments from Files or Git/Review collect into one Code review attachment for the agent, including phone comments. These are not GitHub PR comments. File/range/PR references preserve context, but line contents can change; reviewers must check the revision. This is feedback, not a durable exact-revision approval gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

## boxes-dev:SHIP-06

Finding: Folders and thread/devbox groups help organize completed work, while file/diff feedback can be batched per thread. There is no established dependency-aware merge queue or exact-revision approval workflow in the checked public sources.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-03-21
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Folders, diffs and feedback batches are documented. Risk filters, exact-revision approvals and dependency-aware merge/release queues are not established by the public review guides; server/app code is unavailable.

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/files-and-transfers
Locator: Workspace search; previews; uploads/downloads; conflict handling
Finding: Files searches filenames/text and edits current machine files with save/conflict indicators. It previews Markdown, images, videos, PDFs and HTML via Browser. Desktop transfers allow files up to 5 GiB; phone downloads allow 100 MB. Folder download requires an archive. Machine-local files are lost when the devbox is destroyed.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/code-review-comments
Locator: Comment on file/diff; Review and send the batch; Check the revision
Finding: Line and range comments from Files or Git/Review collect into one Code review attachment for the agent, including phone comments. These are not GitHub PR comments. File/range/PR references preserve context, but line contents can change; reviewers must check the revision. This is feedback, not a durable exact-revision approval gate.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/commit-push-pull-request
Locator: Review/commit; PR creation; merge; automated follow-ups; attribution
Finding: Git/Review stages hunks, commits, reverts edits, creates/pushes branches and GitHub PRs and displays checks/conflicts. Pull-and-push supports rebase/merge. Optional PR follow-ups respond to checks, human/bot feedback and conflicts with documented batching and pause rules. Merged-PR notices indicate landing; optional commit trailers link threads.
Retrieved: 2026-11-21

## boxes-dev:OWN-01

Finding: Boxes.dev is a vendor cloud service under custom service terms. Public CLI packages are readable but marked UNLICENSED; no public full application/server repository or upstream Git commit was established. Visibility of a distribution does not make the product open source.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-05-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev iOS and Android apps; Workstation dvb CLI and switchboard; Managed Linux devboxes and on-box agent tools; Boxes.dev automations, Slack, Linear and remote MCP
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The npm distributions are public readable UNLICENSED artifacts, not an open-source app repository. No upstream Git commit or full desktop/mobile/server source/license grant is published in the checked official links and repository searches.

Source: https://boxes.dev/terms
Locator: Cloud Service; Subscription Period; Non-Renewal Notice; data deletion and backups
Finding: Boxes, Inc. offers a cloud-service agreement with a one-month subscription period, tier/usage fees and incorporated Common Paper terms. The posted order form says 30 days' non-renewal notice, while the billing guide describes cancellation at the period end. Separate signed cover pages can replace these terms. This is not an open-source license grant.
Retrieved: 2026-11-21

Source: https://registry.npmjs.org/@boxes-dev/cli/1.0.1135
Locator: package.json os/cpu/license/bin; tarball standalone-manifest.json and scripts/postinstall.mjs
Finding: The exact npm release is UNLICENSED, exports dvb/dvbd and distributes darwin/linux x64/arm64 archives with SHA-256 checks. The inspected shell wrapper executes the installed standalone runtime. Tarball SHA-256 d41fe950a7504c2019a999276e535a8d36b84b0aa8fbe735e0f4fa7ab61df844. No upstream Git commit is published.
Retrieved: 2026-11-21

Source: https://registry.npmjs.org/@boxes-dev/dvb-runtime/-/dvb-runtime-1.0.1135.tgz
Locator: package/package.json; dist/bin/dvb.mjs lines 300360-302304; dist/product-docs/references/agent-tools.md and onbox-agent-tools.md
Finding: The readable released bundle implements thread start/control/read/observation command routing and ships agent-tool documentation. It is UNLICENSED and includes React/Ink CLI dependencies. Pin is npm version 1.0.1135, tarball SHA-256 213b030dae6a0fb83fd7861ab63ecc467f40a9ad16e7f2dd2613438af936fa18; no public upstream Git commit is exposed, so this distribution inspection is recorded as documented evidence rather than commit-pinned source-inspected. It cannot establish closed server enforcement or desktop/mobile implementation.
Retrieved: 2026-11-21

Source: https://registry.npmjs.org/@boxes-dev/dvb-runtime/-/dvb-runtime-1.0.1135.tgz
Locator: package/dist/product-docs/references/security-and-data.md, Desktop app logs, line 344
Finding: The versioned product documentation identifies the desktop main-process log as ~/.devbox/logs/desktop-electron-main.log. This supports an Electron desktop implementation, without access to its full build source or proof of mobile framework. Same package SHA-256 213b030dae6a0fb83fd7861ab63ecc467f40a9ad16e7f2dd2613438af936fa18; upstream Git commit unavailable.
Retrieved: 2026-11-21

## boxes-dev:OWN-02

Finding: Code/files can be downloaded or pushed, user/final-agent transcript messages copied as Markdown and native local threads imported. A vendor-independent full ADE or complete portable account export is not established.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-05-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

File download, Markdown transcript copy and native-history import are documented. Full vendor-independent control-plane hosting, complete account export and cancellation portability are not established by current docs or closed backend.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/choose-project-setup
Locator: Choose your starting point; Before you begin; Where setup starts
Finding: Users sign in and connect an agent, then use local-agent setup, the desktop local-folder wizard, a Team Template, or GitHub setup for subsequent projects. GitHub login is optional for local setup. Machine size is chosen at creation, applies across the project and is not resizable in place; each size includes 100 GB disk.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/local-folder-setup
Locator: Review the setup scans; Check the final bundle; Fine-tune what gets copied
Finding: Read-only local scans prepare an upload bundle. The user selects repositories, local edits, untracked files, config, databases and optional history before upload. SSH, GitHub credentials and signing choices are explicit. Remote agents prepare the template; snapshots initialize later work.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/start-and-continue-threads
Locator: Queue versus Steer; Stop; drafts; attachments; import
Finding: Codex and Claude support queued follow-ups and steering with different interruption semantics. Stopping a response can leave queued work able to run. Drafts and failed-start recovery retain requests; attachments include files, folders and model-dependent images. Reusing a devbox shares its files, while changing Codex provider needs a new thread.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/files-and-transfers
Locator: Workspace search; previews; uploads/downloads; conflict handling
Finding: Files searches filenames/text and edits current machine files with save/conflict indicators. It previews Markdown, images, videos, PDFs and HTML via Browser. Desktop transfers allow files up to 5 GiB; phone downloads allow 100 MB. Folder download requires an archive. Machine-local files are lost when the devbox is destroyed.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

Source: https://boxes.dev/terms
Locator: Cloud Service; Subscription Period; Non-Renewal Notice; data deletion and backups
Finding: Boxes, Inc. offers a cloud-service agreement with a one-month subscription period, tier/usage fees and incorporated Common Paper terms. The posted order form says 30 days' non-renewal notice, while the billing guide describes cancellation at the period end. Separate signed cover pages can replace these terms. This is not an open-source license grant.
Retrieved: 2026-11-21

Source: https://boxes.dev/teams
Locator: Infrastructure options; Plans sized around your workflow
Finding: Custom pricing, hour pools and dedicated resources are available through discussion. The team brief says the vendor is open to hosting on customer infrastructure; it does not establish a downloadable self-hosted control plane.
Retrieved: 2026-11-21

## boxes-dev:OWN-03

Finding: Code, prompts, credentials and history reach managed machines and selected provider services. Analytics, crash logs and masked replay are disclosed. Some retention/deletion behavior is explicit; general training exclusions, fixed backup expiry and telemetry opt-out remain unknown.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev browser and phone web client; Boxes.dev iOS and Android apps; Workstation dvb CLI and switchboard; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The data guide and privacy policy give partial retention and narrower Google/Slack training statements. A general customer-content training exclusion, fixed backup expiry, selectable residency and documented telemetry opt-out/default/consent controls remain unestablished; app/backend source is closed.

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/data-and-credentials
Locator: Copied files; credentials; machine sharing; stored history; deletion
Finding: Code and secrets selected for upload reside on cloud machines and are usable by their tools/agents. Selected SSH/signing private keys may be copied explicitly. Tokens/member files have scoped encrypted storage but authorized services and machine software can decrypt/read them. Saved history is also stored by Boxes.dev. Analytics, Sentry logs and masked replay are disclosed. Machine deletion archives threads; account deletion has billing and backup exceptions.
Retrieved: 2026-11-21

Source: https://boxes.dev/privacy
Locator: Sections 2, 4, 5, 7, 9 and 10
Finding: The policy discloses account/device/session data, masked replay, Convex, Cloudflare, Expo, OpenAI title generation, Amplitude and Sentry. Replay retention is generally up to 30 days; other retention/backups lack fixed durations. International processing may occur in the US/other provider locations. Third-party agent terms are separate. No training promise is general to all customer content; narrower Google/Slack commitments must stay scoped.
Retrieved: 2026-11-21

## boxes-dev:OWN-04

Finding: Managed compute costs USD 19/99/249 per paid seat/month on Starter/Pro/Max, including 50/300/750 box-hours. Trial is 20 hours. Paid overage is USD 0.40 per standard box-hour before discounts; agent subscriptions/API costs remain separate.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Trial, Starter, Pro and Max public monthly billing; custom Teams arrangements separate
Surface: Boxes.dev browser and phone web client; Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Public prices and compute units are established. Tax treatment, all enterprise minima and separately billed mobile/build resource rates are not fully specified by the public plan table; provider/model invoices remain separate.

Source: https://boxes.dev/
Locator: Manage your agents; Pricing; For Teams
Finding: The service runs native Claude Code and Codex on cloud computers with desktop, mobile, browser and CLI access. Teams pricing advertises SSO/SAML/OIDC, SCIM, audit logs and custom infrastructure; implementation, contract scope and enablement are not established by the marketing list.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:OWN-05

Finding: Illustrative monthly Starter workload: each developer completes 10 tasks on a standard devbox for 4 awake hours each, with at most 2 awake work boxes and 10 total awake template hours, for 50 box-hours/person. One person pays USD 19, two collaborating people USD 38 and five USD 95 before provider charges/taxes. This is an input scenario, not measured task cost.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Illustrative Starter monthly scenario, not a measured benchmark or provider-cost quote
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The scenarios below calculate only documented Boxes.dev seat and box-hour charges. Actual provider subscription/API costs, tokens per task, mobile/build charges and taxes cannot be inferred; no average task price is invented.

Source: https://boxes.dev/help/how-boxes-works
Locator: Start a thread, get a machine; Continue from any device; Return later
Finding: Threads run on managed Linux devboxes, by default copied from a prepared template. Each devbox has its own files, services and ports; several threads may share one devbox. External databases can remain shared. Sleep preserves files and memory but pauses execution. Destroying a devbox deletes its files and archives its conversations.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

## boxes-dev:OWN-06

Finding: Current public docs and store distributions offer account-based access and a finite self-serve trial. Official release 1.0.1135 is dated 2026-11-19. Android still describes early-access/waitlist accounts; signup eligibility was not tested.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Boxes.dev browser and phone web client; Boxes.dev iOS and Android apps; Workstation dvb CLI and switchboard; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Public clients and a self-serve trial exist, but the Android description still says early access/waitlist. Signup success, region-specific access, formal GA status, status history and general response SLA are not established.

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/files-and-transfers
Locator: Workspace search; previews; uploads/downloads; conflict handling
Finding: Files searches filenames/text and edits current machine files with save/conflict indicators. It previews Markdown, images, videos, PDFs and HTML via Browser. Desktop transfers allow files up to 5 GiB; phone downloads allow 100 MB. Folder download requires an archive. Machine-local files are lost when the devbox is destroyed.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/contact-support
Locator: Feedback channels; CLI reports; diagnostics
Finding: Support is available through hi@boxes.dev, the public support page and in-app feedback. dvb report-bug includes description, CLI version/platform and account information, not repository files or environment variables automatically. Security reports go to security@boxes.dev. No general support response SLA is given.
Retrieved: 2026-11-21

Source: https://boxes.dev/changelog
Locator: November 19, 2026, Version 1.0.1135; November 17, Version 1.0.1134
Finding: Release 1.0.1135 is dated 2026-11-19 and adds HTML review, first-thread archiving and optional devbox/tab sidebar layout; PR follow-ups ignore late edits of bot status comments. The prior release adds Codex GPT-6.2-Sol/Astra and web Team Template setup. These are release dates, not retrieval dates.
Retrieved: 2026-11-21

Source: https://boxes.dev/security
Locator: Credential guidance; Vulnerability Disclosure Policy; What to expect
Finding: Security guidance and vulnerability reporting are public; the vendor commits to acknowledging vulnerability reports within three business days. This is not a support SLA, SOC 2 report or ISO certificate.
Retrieved: 2026-11-21

Source: https://apps.apple.com/us/app/boxes-dev/id6758927946
Locator: Compatibility; Version History; account prerequisite
Finding: The public iOS/iPadOS listing requires version 16.4 or later, distributes version 1.0.1135 and requires an existing Boxes.dev account. Its seller is ND Innovations LLC. Store download price alone does not establish free compute access.
Retrieved: 2026-11-21

Source: https://play.google.com/store/apps/details?id=dev.boxes
Locator: About this app; Updated on
Finding: The public Android listing is dated updated 2026-11-19 and offers thread history, follow-ups and notifications. Its description still calls account access early access/waitlist, unlike the current self-serve website/help. Successful signup and region-specific eligibility were not tested.
Retrieved: 2026-11-21

## boxes-dev:OWN-08

Finding: Evaluation uses a finite 20-box-hour per-user trial, not an established ongoing free compute plan. It includes connected-agent access and limited cloud capacity; after trial expiry/exhaustion, a paid seat is required to start or wake machines.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

The 20-box-hour trial is finite; no recurring free compute allowance is established. Trial end date and card requirements can vary by team. Public pricing, not free store downloads, determines continued compute access.

Source: https://boxes.dev/help/use-mobile
Locator: Install and open a project; Start or continue a task; Review files and use a terminal
Finding: The iOS and Android apps open existing cloud projects. They can start and continue threads, answer questions and approvals, stop work, inspect files and diffs, batch code comments and use a terminal. The /m link is an app-install route, not proof of a mobile browser workbench. Initial environment preparation and some administration remain computer tasks.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/connect-agents
Locator: Connect an account; Add a model provider; account switching and limits
Finding: Codex supports ChatGPT login, OpenAI keys, OpenRouter, Vercel AI Gateway and compatible custom streaming Responses endpoints. Claude supports Claude login or API keys. Saved accounts can switch or rotate, with optional separately billed API fallback. Providers remain fixed within Codex threads; a new provider starts a new conversation.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/organize-and-share-threads
Locator: Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Finding: Threads can be named, pinned, archived, restored and searched across titles, prompts and final replies, including archives. Agent-created devboxes group under their creator. Sharing is read-only: teammates cannot prompt, approve, stop, open a terminal or control the machine. Copy transcript produces Markdown; media/history access has distinct persistence rules.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

Source: https://play.google.com/store/apps/details?id=dev.boxes
Locator: About this app; Updated on
Finding: The public Android listing is dated updated 2026-11-19 and offers thread history, follow-ups and notifications. Its description still calls account access early access/waitlist, unlike the current self-serve website/help. Successful signup and region-specific eligibility were not tested.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/slack
Locator: Follow up in the same Slack thread; Let teammates start work in your project; private-channel and owner authorization rules
Finding: Owners can authorize selected or any linked teammates to start work and send follow-ups in linked Slack threads, including tasks the owner started. Both people must be active on the same Boxes.dev team with linked Slack accounts. No one is the default and teammates cannot grant themselves access. Follow-ups target the same agent and identify their sender; active work receives Steer unless the owner chooses Queue. Work uses the owner's environment, credentials and usage. Private-channel restrictions also apply after launch.
Retrieved: 2026-11-21

## boxes-dev:OWN-09

Finding: Self-serve pricing is partially specified: monthly seat rates, box-hour units, allowances and overages are public. Agent costs are separate, enterprise terms require a quote and cancellation wording differs between help and the posted order form.

Verification: agent-cross-checked
Checked: 2026-11-21
Scheduled recheck: 2027-01-20
Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated
Surface: Boxes.dev desktop workbench for macOS and Linux; Managed Linux devboxes and on-box agent tools
Version: Desktop/CLI release 1.0.1135 (2026-11-19); live service/help checked 2026-11-21; mobile stores scoped separately

Self-serve units/prices are public, while taxes and enterprise terms remain unspecified. Website cancellation language and the posted order form differ; exact contractual notice obligations need confirmation for the customer's agreement.

Source: https://boxes.dev/
Locator: Manage your agents; Pricing; For Teams
Finding: The service runs native Claude Code and Codex on cloud computers with desktop, mobile, browser and CLI access. Teams pricing advertises SSO/SAML/OIDC, SCIM, audit logs and custom infrastructure; implementation, contract scope and enablement are not established by the marketing list.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/plans-and-box-hours
Locator: Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Finding: Trial grants 20 box-hours per user. Starter is USD 19/seat/month with 50 hours, Pro USD 99 with 300, Max USD 249 with 750. Per-user awake-devbox caps are 3/5/12/25 plus the template; projects 2/5/10/20. Standard compute is 4 vCPU/8 GiB. Paid overage uses shared prepaid credits at USD 0.40/box-hour before volume discounts. Template awake time counts; sleeping time does not.
Retrieved: 2026-11-21

Source: https://boxes.dev/help/billing-and-usage
Locator: Hourly history; seat and cancellation rules; credit limits; mobile devices
Finding: Usage history shows the owner's compute by hour/day and per-box contribution, updating on completed hourly windows. Paid seats have individual included hours; overage credits pool by team. Credits require a paid plan and purchases start at USD 20 with a USD 1,000/team/month cap. Optional auto-reload has a separate cap. Cloud mobile devices/builders use separate credit charges. Cancellation takes effect at period end.
Retrieved: 2026-11-21

Source: https://boxes.dev/terms
Locator: Cloud Service; Subscription Period; Non-Renewal Notice; data deletion and backups
Finding: Boxes, Inc. offers a cloud-service agreement with a one-month subscription period, tier/usage fees and incorporated Common Paper terms. The posted order form says 30 days' non-renewal notice, while the billing guide describes cancellation at the period end. Separate signed cover pages can replace these terms. This is not an open-source license grant.
Retrieved: 2026-11-21

Source: https://boxes.dev/teams
Locator: Infrastructure options; Plans sized around your workflow
Finding: Custom pricing, hour pools and dedicated resources are available through discussion. The team brief says the vendor is open to hosting on customer infrastructure; it does not establish a downloadable self-hosted control plane.
Retrieved: 2026-11-21