podium

Boxes.dev

46 of 51 criteria have a sourced finding; 46 were also cross-checked by a second agent. Every comparison that includes Boxes.dev links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-11-21
Agent cross-checked
46 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
9 atomic answers
  • Desktop os [supported] The desktop guide lists macOS and Linux. Its main Mac build is Apple Silicon on macOS 12+, with macOS 13+ for bundled database copying. The complete desktop platform list omits Windows. Sources: boxes-dev:desktop.
  • Mobile apps [partial] Public iOS/iPadOS and Android store distributions exist. iOS/iPadOS requires 16.4+. A Boxes.dev account and a prepared project are needed; the Android access wording is still qualified. Sources: boxes-dev:mobile, boxes-dev:ios, boxes-dev:android.
  • Browser [partial] The homepage lists web alongside desktop/mobile/CLI. The setup guide documents website project creation and account setup; Billing and Team Template administration are documented as browser workflows separately. Full browser start/steer/approve/review/resume parity is not established. Sources: boxes-dev:home, boxes-dev:setup, boxes-dev:billing, boxes-dev:roles.
  • Mobile browser [partial] The setup guide explicitly allows creating a later GitHub project on the Boxes.dev website in a phone browser, then continuing in the native mobile app. This establishes a limited phone website workflow, not a browser agent-chat/review equivalent. /m is an app-install route. Sources: boxes-dev:setup, boxes-dev:mobile.
  • Cli [supported] dvb is the product-owned workstation CLI for macOS/Linux x64/arm64, separate from Codex/Claude and the on-box helper. Sources: boxes-dev:cli, boxes-dev:npm-cli.
  • Editor extensions [unknown] Editor extensions is not established. 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.
  • Task actions [partial] Desktop, phone and CLI guides cover starting, following up, stopping and resuming threads; phone/desktop support approvals and file/diff review. This does not promise every action in each client. Sources: boxes-dev:mobile, boxes-dev:cli, boxes-dev:desktop.
  • Notifications [supported] Desktop notifications and native phone push report replies, failure and input needs, with quiet hours, mute and account/device controls. Sources: boxes-dev:notifications.
  • Cross device continuity [supported] The same cloud conversation is available across clients. Claude terminal control transfers need confirmation; switching devices does not relocate the agent. Sources: boxes-dev:how, boxes-dev:cli.

Sources: boxes-dev:desktop, boxes-dev:mobile, boxes-dev:cli, boxes-dev:ios, boxes-dev:android, boxes-dev:setup, boxes-dev:npm-cli, boxes-dev:notifications, boxes-dev:how, boxes-dev:home, boxes-dev:billing, boxes-dev:roles

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
5 atomic answers
  • Harnesses [supported] The documented managed agent choices are Codex and Claude Code. Other provider models running in Codex remain Codex. Sources: boxes-dev:agents, boxes-dev:models.
  • Model providers [supported] Codex supports OpenAI, OpenRouter, Vercel and compatible custom endpoints; Claude uses its connected account. Gateway model catalogs are selected and change over time. Sources: boxes-dev:agents, boxes-dev:models.
  • Custom adapters [partial] Custom streaming Responses-compatible model endpoints are supported inside Codex, not a documented generic coding-harness adapter. Tool-loop compatibility is not guaranteed by saving a connection. Sources: boxes-dev:agents.
  • Session integration [supported] The apps and CLI manage persistent native Codex/Claude conversations and can run them in parallel on devboxes. This is session control, not just a launcher. Sources: boxes-dev:how, boxes-dev:cli, boxes-dev:plans.
  • Mixed harness operation [supported] The apps and CLI manage persistent native Codex/Claude conversations and can run them in parallel on devboxes. This is session control, not just a launcher. Sources: boxes-dev:how, boxes-dev:cli, boxes-dev:plans.

Sources: boxes-dev:agents, boxes-dev:models, boxes-dev:how, boxes-dev:cli, boxes-dev:plans

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Exact eligible provider subscription tiers and arbitrary local-model behavior are not enumerated. Model endpoint compatibility remains provider-dependent; hosted authentication internals are closed.
7 atomic answers
  • Agent subscriptions [partial] Native ChatGPT and Claude sign-ins reuse the connected provider account; exact eligible provider subscription tiers are not enumerated in these docs. Sources: boxes-dev:agents.
  • Api accounts [supported] OpenAI/Claude keys and Codex gateway/custom connections are available. API charges go to the provider in addition to Boxes.dev machine usage. Sources: boxes-dev:agents.
  • Vendor credits [supported] Boxes.dev prepaid credits pay compute/device/build usage, not model tokens. The product states that it does not sell tokens. Sources: boxes-dev:home, boxes-dev:billing.
  • Local models [partial] A reachable compatible custom endpoint may be used by Codex; localhost means the devbox, not the laptop. Arbitrary local models/tool-loop behavior is not guaranteed. Sources: boxes-dev:agents.
  • Account switching [supported] Several saved subscriptions/keys can be selected or automatically rotated. API fallback is opt-in; account changes can restart work and stop Claude background processes while preserving history. Sources: boxes-dev:agents.
  • Vendor account requirement [supported] A Boxes.dev sign-in, usable billing/trial and a connected agent/provider are needed for managed work. This is not an account-free local ADE. Sources: boxes-dev:setup, boxes-dev:plans.
  • Provider restrictions [supported] Codex custom providers need streaming Responses and tool compatibility. Provider is fixed in a thread; switching providers starts a new conversation without its prior history. Sources: boxes-dev:agents, boxes-dev:models.

Sources: boxes-dev:agents, boxes-dev:home, boxes-dev:plans, boxes-dev:billing, boxes-dev:setup, boxes-dev:models

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
7 atomic answers
  • First task setup [supported] Sign in, connect an agent, choose project/setup and machine size, review local scans/upload or select a template, let a remote agent prepare dependencies, then snapshot and start a thread. Git access and optional secrets need separate decisions. Sources: boxes-dev:setup, boxes-dev:local.
  • No git [unknown] No git is not established. 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.
  • Local git without remote [partial] Local-folder setup copies repository contents, history and chosen local edits without requiring a GitHub connection. Exact treatment of every remote-free repository configuration is not stated. Sources: boxes-dev:setup, boxes-dev:local.
  • Hosted git [supported] Later projects can clone selected GitHub repositories with granted repository access; the first environment follows local/template setup. Sources: boxes-dev:setup.
  • Prerequisite guidance [supported] Sign in, connect an agent, choose project/setup and machine size, review local scans/upload or select a template, let a remote agent prepare dependencies, then snapshot and start a thread. Git access and optional secrets need separate decisions. Sources: boxes-dev:setup, boxes-dev:local.
  • Managed cloud setup [supported] Sign in, connect an agent, choose project/setup and machine size, review local scans/upload or select a template, let a remote agent prepare dependencies, then snapshot and start a thread. Git access and optional secrets need separate decisions. Sources: boxes-dev:setup, boxes-dev:local.
  • Byo vps onboarding [unknown] Byo vps onboarding is not established. 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.

Sources: boxes-dev:setup, boxes-dev:local

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
8 atomic answers
  • Cli [supported] dvb resource commands create/read/send/interrupt/observe threads and manage machines, settings and permissions. The exact release bundle routes these operations; managed boxes use dvb-onbox. Sources: boxes-dev:commands, boxes-dev:npm-runtime.
  • Api [supported] Activated automations accept run/wake requests and report launch/delivery status. Idempotency handles retries; follow-ups can target existing owned threads. Read final output in the conversation. Sources: boxes-dev:api.
  • Sdk [unknown] Sdk is not established. 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.
  • Mcp server [supported] OAuth remote MCP at api.boxes.dev/mcp exposes selected projects, read/task/event/settings permissions, thread search/start/follow-up/interrupt and status, with documented restrictions. Sources: boxes-dev:mcp-server.
  • Webhooks [partial] External services can invoke the automation API; Slack/Linear/GitHub supply integration events. A general outgoing webhook subscription contract is not established. Sources: boxes-dev:api, boxes-dev:schedules, boxes-dev:git.
  • Operations [supported] dvb resource commands create/read/send/interrupt/observe threads and manage machines, settings and permissions. The exact release bundle routes these operations; managed boxes use dvb-onbox. Sources: boxes-dev:commands, boxes-dev:npm-runtime.
  • Authentication [supported] Workstation sign-in, automation Bearer secrets and OAuth MCP grants are separate. Secrets can rotate; MCP grants select projects and privileges. Sources: boxes-dev:cli, boxes-dev:api, boxes-dev:mcp-server.
  • Stability [partial] Versioned CLI releases and rejected invalid API inputs are documented, but no public compatibility SLA is established. Sources: boxes-dev:api, boxes-dev:release, boxes-dev:npm-runtime.

Sources: boxes-dev:commands, boxes-dev:api, boxes-dev:mcp-server, boxes-dev:npm-runtime, boxes-dev:schedules, boxes-dev:git, boxes-dev:cli, boxes-dev:release

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Managed MCP/plugins and harness instructions are documented, but arbitrary extension compatibility and enforcement depend on closed services and the underlying agents.
7 atomic answers
  • Mcp client [supported] Project-managed MCP connections support Codex/Claude authorization and external tools. This is separate from Boxes.dev's own remote MCP server. Sources: boxes-dev:mcp-client.
  • Plugins [partial] Plugins add skills/tools. Verified public marketplace plugins can be managed across machines at their verified commit; private/local/per-machine plugins may stay template-only. Sources: boxes-dev:plugins.
  • Custom tools [partial] Plugins add skills/tools. Verified public marketplace plugins can be managed across machines at their verified commit; private/local/per-machine plugins may stay template-only. Sources: boxes-dev:plugins.
  • Instructions import [supported] Repository AGENTS.md/CLAUDE.md and saved Agent guidance provide instructions; selected local agent settings/history can be included during setup. Sources: boxes-dev:instructions, boxes-dev:local.
  • Authentication [partial] MCP sign-ins can be separate for Codex and Claude. Plugin destination may be project, template or ChatGPT account; provider connector access retains that provider's authorization. Sources: boxes-dev:mcp-client, boxes-dev:plugins, boxes-dev:agents.
  • Permission scope [partial] MCP sign-ins can be separate for Codex and Claude. Plugin destination may be project, template or ChatGPT account; provider connector access retains that provider's authorization. Sources: boxes-dev:mcp-client, boxes-dev:plugins, boxes-dev:agents.
  • Integration owner [partial] MCP sign-ins can be separate for Codex and Claude. Plugin destination may be project, template or ChatGPT account; provider connector access retains that provider's authorization. Sources: boxes-dev:mcp-client, boxes-dev:plugins, boxes-dev:agents.

Sources: boxes-dev:mcp-client, boxes-dev:plugins, boxes-dev:instructions, boxes-dev:agents, boxes-dev:local

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
4 atomic answers
  • Desktop implementation [partial] The released documentation names desktop-electron-main.log as the desktop main-process log, supporting Electron. Full build configuration was not public. Sources: boxes-dev:runtime-desktop.
  • Mobile implementation [unknown] Mobile implementation is not established. 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.
  • Hybrids [unknown] Hybrids is not established. 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.
  • Implementation evidence [partial] Inspected public npm runtime 1.0.1135 documentation at the recorded path and SHA-256; no upstream Git commit is published. Mobile framework remains unknown. Sources: boxes-dev:runtime-desktop.

Sources: boxes-dev:runtime-desktop, boxes-dev:privacy

Planning and context

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
official-integration
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
9 atomic answers
  • Local creation [supported] Users start a thread by prompting Codex/Claude in a prepared project; new work normally gets a devbox. Sources: boxes-dev:threads.
  • Prompt intake [supported] Users start a thread by prompting Codex/Claude in a prepared project; new work normally gets a devbox. Sources: boxes-dev:threads.
  • External import [supported] Slack mentions, Linear delegation and optional PR follow-ups can trigger managed agent work with source context. Sources: boxes-dev:slack, boxes-dev:linear, boxes-dev:git.
  • Chat git triggers [supported] Slack mentions, Linear delegation and optional PR follow-ups can trigger managed agent work with source context. Sources: boxes-dev:slack, boxes-dev:linear, boxes-dev:git.
  • Authoritative tracker [supported] Linear remains the external issue authority; its issue identifier/title and Agent Session link identify connected work. Boxes.dev uses distinct thread/devbox IDs. Sources: boxes-dev:linear, boxes-dev:commands.
  • Stable ids [supported] Linear remains the external issue authority; its issue identifier/title and Agent Session link identify connected work. Boxes.dev uses distinct thread/devbox IDs. Sources: boxes-dev:linear, boxes-dev:commands.
  • Sync [partial] Progress, questions, final answers and attached result URLs flow back to Linear, while its linked user's follow-ups reach the same thread. General issue-field sync is unestablished. Sources: boxes-dev:linear.
  • Supported edits [partial] Follow up or stop in the linked Linear Agent Session; other users cannot control that thread through their replies. Issue administration remains in Linear. Sources: boxes-dev:linear.
  • External roundtrips [partial] Follow up or stop in the linked Linear Agent Session; other users cannot control that thread through their replies. Issue administration remains in Linear. Sources: boxes-dev:linear.

Sources: boxes-dev:threads, boxes-dev:linear, boxes-dev:slack, boxes-dev:git, boxes-dev:commands

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
7 atomic answers
  • Plans [partial] Codex and Claude goals retain a stated outcome across responses. They are task objectives rather than a documented structured plan entity. Sources: boxes-dev:goals.
  • Acceptance criteria [unknown] Acceptance criteria is not established. 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.
  • Editors [partial] Codex Edit goal/Replace goal changes its objective in the same thread, with pause/resume controls. Claude has different goal commands and restrictions. Sources: boxes-dev:goals.
  • Revisions [unknown] Revisions is not established. 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.
  • Amendment [partial] Codex Edit goal/Replace goal changes its objective in the same thread, with pause/resume controls. Claude has different goal commands and restrictions. Sources: boxes-dev:goals.
  • Restart persistence [partial] The saved goal panel and ongoing conversation retain the objective; guaranteed crash/restart semantics are not specified. Sources: boxes-dev:goals.

Sources: boxes-dev:goals, boxes-dev:threads

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
beta
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
10 atomic answers
  • Instructions [supported] AGENTS.md/CLAUDE.md, project Agent guidance, installed skill/plugins and shared project files provide reusable context with different update rules. Sources: boxes-dev:instructions, boxes-dev:storage, boxes-dev:plugins.
  • Skills [supported] AGENTS.md/CLAUDE.md, project Agent guidance, installed skill/plugins and shared project files provide reusable context with different update rules. Sources: boxes-dev:instructions, boxes-dev:storage, boxes-dev:plugins.
  • Project docs [supported] AGENTS.md/CLAUDE.md, project Agent guidance, installed skill/plugins and shared project files provide reusable context with different update rules. Sources: boxes-dev:instructions, boxes-dev:storage, boxes-dev:plugins.
  • Memory [partial] Claude automatic memory uses /project/.claude/memory unless overridden; Codex only shares ordinary files. The share is project-scoped and has multi-writer limitations. Sources: boxes-dev:storage.
  • Scope [partial] Claude automatic memory uses /project/.claude/memory unless overridden; Codex only shares ordinary files. The share is project-scoped and has multi-writer limitations. Sources: boxes-dev:storage.
  • Provenance [unknown] Provenance is not established. 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.
  • Correction [partial] Guidance can be edited/cleared for later devboxes; shared files can be edited and project deletion removes shared storage. Managed semantic memory correction is not established. Sources: boxes-dev:instructions, boxes-dev:storage.
  • Deletion [partial] Guidance can be edited/cleared for later devboxes; shared files can be edited and project deletion removes shared storage. Managed semantic memory correction is not established. Sources: boxes-dev:instructions, boxes-dev:storage.
  • Freshness [partial] New guidance reaches future devboxes, not existing sessions. The share has roughly one-second propagation and no strict multi-writer consistency; semantic freshness is unestablished. Sources: boxes-dev:instructions, boxes-dev:storage.
  • Takeover continuity [unknown] Takeover continuity is not established. 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.

Sources: boxes-dev:instructions, boxes-dev:storage, boxes-dev:plugins

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
10 atomic answers
  • Indexing [unknown] Indexing is not established. 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.
  • External knowledge [partial] Configured MCP servers and plugins can provide external information, subject to each service's authorization and capabilities. Built-in authoritative API retrieval is not established. Sources: boxes-dev:mcp-client, boxes-dev:plugins.
  • Multimodal inputs [supported] Threads accept files/folders and images; model image capability and custom text-only endpoint restrictions apply. Sources: boxes-dev:threads, boxes-dev:models.
  • Freshness [unknown] Freshness is not established. 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.
  • Access scope [partial] Inputs and searches belong to the selected machine/project and configured tools. Shared external systems can remain reachable by credentials. Sources: boxes-dev:files, boxes-dev:data.
  • Api retrieval [partial] Configured MCP servers and plugins can provide external information, subject to each service's authorization and capabilities. Built-in authoritative API retrieval is not established. Sources: boxes-dev:mcp-client, boxes-dev:plugins.
  • Citations [unknown] Citations is not established. 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.
  • Conflict detection [unknown] Conflict detection is not established. 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.
  • Review enforcement [unknown] Review enforcement is not established. 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.

Sources: boxes-dev:files, boxes-dev:threads, boxes-dev:mcp-client, boxes-dev:how, boxes-dev:plugins, boxes-dev:models, boxes-dev:data

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Concurrency is documented, not measured. No hands-on runs were performed, and exact simultaneous throughput is not inferred from UI tabs or package code.
5 atomic answers
  • Concurrent sessions [supported] Several agents/threads can work concurrently, including separate API runs and several threads on one devbox. Shared-box threads can edit the same files. Sources: boxes-dev:how, boxes-dev:api.
  • Concurrent tasks [supported] Several agents/threads can work concurrently, including separate API runs and several threads on one devbox. Shared-box threads can edit the same files. Sources: boxes-dev:how, boxes-dev:api.
  • Quotas [supported] Trial/Starter/Pro/Max allow 3/5/12/25 awake devboxes per user plus a Template box, subject to billing. Several threads can share a box, so this is not a session cap. Sources: boxes-dev:plans, boxes-dev:how.
  • Observed concurrency [unknown] Observed concurrency is not established. Concurrency is documented, not measured. No hands-on runs were performed, and exact simultaneous throughput is not inferred from UI tabs or package code.
  • Status visibility [supported] Thread sorting, Working groups, unread/input markers and agent-created devbox groups expose active work and attention needs. Sources: boxes-dev:organize, boxes-dev:notifications.

Sources: boxes-dev:how, boxes-dev:plans, boxes-dev:organize, boxes-dev:api, boxes-dev:notifications

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
7 atomic answers
  • Human assignment [partial] A Linear task runs under the linked person who initiated its Agent Session and that person's saved automation/environment. This is external assignment routing. Sources: boxes-dev:linear.
  • Agent assignment [partial] Automations select Codex/Claude and model settings. This chooses the session harness, not exclusive ownership of a native issue. Sources: boxes-dev:automation, boxes-dev:api.
  • Claims [unknown] Claims is not established. 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.
  • Queues [partial] Busy existing threads can queue follow-ups; scheduled runs can retry for capacity. A general ready-task dispatch queue is unestablished. Sources: boxes-dev:api, boxes-dev:schedules.
  • Routing [partial] A Linear task runs under the linked person who initiated its Agent Session and that person's saved automation/environment. This is external assignment routing. Sources: boxes-dev:linear.
  • Duplicate prevention [partial] An identical API request key replays the same run; changed input conflicts. Repeated events within one Linear Agent Session reuse its thread. These do not prevent semantically duplicate tasks. Sources: boxes-dev:api, boxes-dev:linear.
  • Ownership enforcement [unknown] Ownership enforcement is not established. 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.

Sources: boxes-dev:linear, boxes-dev:api, boxes-dev:automation, boxes-dev:schedules

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Roles [partial] Agents can create worker devboxes/threads and the sidebar retains creator grouping. A full role hierarchy and universal dedicated Coordinator availability are not established. Sources: boxes-dev:permissions, boxes-dev:organize.
  • Model harness effort [supported] Documented worker commands can start Codex/Claude threads with explicit settings, while permissions authorize creation. This is Boxes.dev tool orchestration, separate from harness-native subagents. Sources: boxes-dev:commands, boxes-dev:permissions, boxes-dev:npm-runtime.
  • Messages [partial] Permissioned agents can send and receive messages with attached files, read allowed threads and continue idle agents. Codex and Claude are both managed; automatic result acceptance is not documented. Sources: boxes-dev:commands, boxes-dev:permissions.
  • Results return [partial] Permissioned agents can send and receive messages with attached files, read allowed threads and continue idle agents. Codex and Claude are both managed; automatic result acceptance is not documented. Sources: boxes-dev:commands, boxes-dev:permissions.
  • Cross harness [partial] Permissioned agents can send and receive messages with attached files, read allowed threads and continue idle agents. Codex and Claude are both managed; automatic result acceptance is not documented. Sources: boxes-dev:commands, boxes-dev:permissions.
  • Orchestration owner [supported] Boxes.dev ships on-box delegation tools and operation permissions. Creation/read/messaging have distinct grants, both messaging endpoints need permission, and work uses the owner's connected provider accounts. Sources: boxes-dev:permissions, boxes-dev:commands.
  • Activation [supported] Boxes.dev ships on-box delegation tools and operation permissions. Creation/read/messaging have distinct grants, both messaging endpoints need permission, and work uses the owner's connected provider accounts. Sources: boxes-dev:permissions, boxes-dev:commands.
  • Authentication [supported] Boxes.dev ships on-box delegation tools and operation permissions. Creation/read/messaging have distinct grants, both messaging endpoints need permission, and work uses the owner's connected provider accounts. Sources: boxes-dev:permissions, boxes-dev:commands.
  • Live progress [partial] Created devboxes group beneath the creator with work/unread/input indicators. Allowed threads can be read and messaged later; complete retained child-review findings depend on those threads/files. Sources: boxes-dev:organize, boxes-dev:permissions.
  • Retained results [partial] Created devboxes group beneath the creator with work/unread/input indicators. Allowed threads can be read and messaged later; complete retained child-review findings depend on those threads/files. Sources: boxes-dev:organize, boxes-dev:permissions.
  • Followup [partial] Created devboxes group beneath the creator with work/unread/input indicators. Allowed threads can be read and messaged later; complete retained child-review findings depend on those threads/files. Sources: boxes-dev:organize, boxes-dev:permissions.
  • Invocation [supported] Documented worker commands can start Codex/Claude threads with explicit settings, while permissions authorize creation. This is Boxes.dev tool orchestration, separate from harness-native subagents. Sources: boxes-dev:commands, boxes-dev:permissions, boxes-dev:npm-runtime.

Sources: boxes-dev:commands, boxes-dev:permissions, boxes-dev:organize, boxes-dev:npm-runtime

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Capacity retries and skipped overlaps are documented; broader failure/retry guarantees and exact scheduler infrastructure are not exposed by the closed service.
8 atomic answers
  • Schedules [supported] Schedules specify hours/days/weeks/months, timezone and initial run date. Saved automations must be activated. Sources: boxes-dev:schedules, boxes-dev:automation.
  • Events [supported] API calls, Slack/Linear and PR follow-ups start work from external events with the required account/project connections. Sources: boxes-dev:api, boxes-dev:slack, boxes-dev:linear, boxes-dev:git.
  • Recurring tasks [supported] Schedules specify hours/days/weeks/months, timezone and initial run date. Saved automations must be activated. Sources: boxes-dev:schedules, boxes-dev:automation.
  • Completion conditions [partial] Run Ready/thread_ready means thread creation or message acceptance, not completed work. Goals can express completion conditions but still require result review. Sources: boxes-dev:schedules, boxes-dev:api, boxes-dev:goals.
  • Scheduler location [supported] The service schedules a cloud devbox run; originating laptop disconnection does not stop its agent. This is vendor-managed execution, not desktop cron. Sources: boxes-dev:schedules, boxes-dev:how.
  • Overlaps [partial] Manual/scheduled overlap can skip; independent API/Slack/Linear events can run in parallel. Scheduled capacity retries are bounded by saved intervals/windows; API idempotency is caller-supplied. Sources: boxes-dev:schedules, boxes-dev:api.
  • Retries [partial] Manual/scheduled overlap can skip; independent API/Slack/Linear events can run in parallel. Scheduled capacity retries are bounded by saved intervals/windows; API idempotency is caller-supplied. Sources: boxes-dev:schedules, boxes-dev:api.
  • Client independence [supported] The service schedules a cloud devbox run; originating laptop disconnection does not stop its agent. This is vendor-managed execution, not desktop cron. Sources: boxes-dev:schedules, boxes-dev:how.

Sources: boxes-dev:automation, boxes-dev:schedules, boxes-dev:api, boxes-dev:linear, boxes-dev:slack, boxes-dev:git, boxes-dev:goals, boxes-dev:how

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
10 atomic answers
  • Pause [partial] Sleep pauses the whole devbox; Codex goals can pause independently. This is not a universal suspend-one-process guarantee. Sources: boxes-dev:sleep, boxes-dev:goals.
  • Stop [partial] Thread controls stop responses, send Queue/Steer follow-ups and continue the saved conversation. Harness/tool timing differs, and queued messages can outlive Stop. Sources: boxes-dev:threads, boxes-dev:mcp-server.
  • Resume [partial] Thread controls stop responses, send Queue/Steer follow-ups and continue the saved conversation. Harness/tool timing differs, and queued messages can outlive Stop. Sources: boxes-dev:threads, boxes-dev:mcp-server.
  • Steer [partial] Thread controls stop responses, send Queue/Steer follow-ups and continue the saved conversation. Harness/tool timing differs, and queued messages can outlive Stop. Sources: boxes-dev:threads, boxes-dev:mcp-server.
  • Notifications [partial] Desktop/mobile alerts and unread/input markers bring questions, errors and approvals back to a thread. Quiet/mute settings alter alerts, not pending requests. Sources: boxes-dev:notifications.
  • Pending decisions [partial] Desktop/mobile alerts and unread/input markers bring questions, errors and approvals back to a thread. Quiet/mute settings alter alerts, not pending requests. Sources: boxes-dev:notifications.
  • Escalation [partial] Desktop/mobile alerts and unread/input markers bring questions, errors and approvals back to a thread. Quiet/mute settings alter alerts, not pending requests. Sources: boxes-dev:notifications.
  • Visible errors [supported] Failed startup/message requests retain repair guidance and drafts; recovery and billing/capacity errors require a user action. Sources: boxes-dev:threads, boxes-dev:sleep, boxes-dev:billing.
  • Chat terminal parity [partial] CLI native interfaces reopen saved threads, but Claude accepts control in one place at a time and asks before transfer. MCP cannot answer approval dialogs. Sources: boxes-dev:cli, boxes-dev:mcp-server.
  • Retained history [partial] Stopping preserves conversation/files; archived history can be read without an awake machine. Destroyed files require separate preservation. Sources: boxes-dev:threads, boxes-dev:organize, boxes-dev:how.

Sources: boxes-dev:threads, boxes-dev:notifications, boxes-dev:sleep, boxes-dev:mcp-server, boxes-dev:goals, boxes-dev:billing, boxes-dev:cli, boxes-dev:organize, boxes-dev:how

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
8 atomic answers
  • Fleet fixture [unknown] Fleet fixture is not established. 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.
  • Parent child [partial] Agent-created devboxes group under the devbox that created them. This relationship is not an issue/epic hierarchy. Sources: boxes-dev:organize.
  • Dependencies [unknown] Dependencies is not established. 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.
  • Attention [partial] Working-first sorting, unread/input markers, folders, search and expandable worker groups expose activity and history. Dependency-aware epic workload remains unestablished. Sources: boxes-dev:organize, boxes-dev:notifications.
  • History [partial] Working-first sorting, unread/input markers, folders, search and expandable worker groups expose activity and history. Dependency-aware epic workload remains unestablished. Sources: boxes-dev:organize, boxes-dev:notifications.
  • Workload [partial] Working-first sorting, unread/input markers, folders, search and expandable worker groups expose activity and history. Dependency-aware epic workload remains unestablished. Sources: boxes-dev:organize, boxes-dev:notifications.
  • Navigation errors [unknown] Navigation errors is not established. 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.
  • Fixture mode [partial] The source pass uses documentation and an unmodified vendor workbench image; no live fixture or navigation performance measurement was run. Sources: boxes-dev:desktop.

Sources: boxes-dev:desktop, boxes-dev:organize, boxes-dev:notifications

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
10 atomic answers
  • Quick task [partial] Start a thread with a task prompt; a saved goal expresses a longer outcome. No mandatory epic preset is shown for this path. Sources: boxes-dev:threads, boxes-dev:goals.
  • Growing epic [unknown] Growing epic is not established. 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.
  • Presets [supported] Per-project defaults/pins and per-thread model, reasoning and speed controls select supported options. Automations retain their launch configuration. Sources: boxes-dev:models, boxes-dev:schedules.
  • Natural language [partial] Start a thread with a task prompt; a saved goal expresses a longer outcome. No mandatory epic preset is shown for this path. Sources: boxes-dev:threads, boxes-dev:goals.
  • Agent configuration [supported] Per-project defaults/pins and per-thread model, reasoning and speed controls select supported options. Automations retain their launch configuration. Sources: boxes-dev:models, boxes-dev:schedules.
  • In run changes [partial] Queue/Steer lets users redirect work; Codex goals can be amended in the same thread. Provider/harness changes may require a new thread. Sources: boxes-dev:threads, boxes-dev:goals, boxes-dev:models.
  • Live roles [partial] Creator grouping and readable worker threads preserve some delegation context, without a complete role/result graph or universal Coordinator availability. Sources: boxes-dev:organize, boxes-dev:permissions.
  • Retained relationships [partial] Creator grouping and readable worker threads preserve some delegation context, without a complete role/result graph or universal Coordinator availability. Sources: boxes-dev:organize, boxes-dev:permissions.
  • Discoverability [partial] Thread/Agent permissions and integration setup are documented. Operation grants and connected provider accounts are separate prerequisites. Sources: boxes-dev:desktop, boxes-dev:permissions, boxes-dev:agents.
  • Auth friction [partial] Thread/Agent permissions and integration setup are documented. Operation grants and connected provider accounts are separate prerequisites. Sources: boxes-dev:desktop, boxes-dev:permissions, boxes-dev:agents.

Sources: boxes-dev:threads, boxes-dev:goals, boxes-dev:models, boxes-dev:permissions, boxes-dev:schedules, boxes-dev:organize, boxes-dev:desktop, boxes-dev:agents

Execution and reliability

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Local [partial] Local setup agents inspect/prepare the laptop environment, then managed cloud threads perform project work. This does not establish a selectable general local/hybrid execution backend. Sources: boxes-dev:setup, boxes-dev:how.
  • Byo remote [partial] The team brief is open to customer-infrastructure deployment discussions; no released BYO installer or self-hosted control plane is established. Sources: boxes-dev:teams.
  • Self hosted [partial] The team brief is open to customer-infrastructure deployment discussions; no released BYO installer or self-hosted control plane is established. Sources: boxes-dev:teams.
  • Managed cloud [supported] The service provisions template-derived cloud machines and bills the user's seat/box-hour allowance. Native agent provider usage is separately paid. Sources: boxes-dev:how, boxes-dev:plans.
  • Hybrid [partial] Local setup agents inspect/prepare the laptop environment, then managed cloud threads perform project work. This does not establish a selectable general local/hybrid execution backend. Sources: boxes-dev:setup, boxes-dev:how.
  • Provisioning [supported] The service provisions template-derived cloud machines and bills the user's seat/box-hour allowance. Native agent provider usage is separately paid. Sources: boxes-dev:how, boxes-dev:plans.
  • Payer [supported] The service provisions template-derived cloud machines and bills the user's seat/box-hour allowance. Native agent provider usage is separately paid. Sources: boxes-dev:how, boxes-dev:plans.
  • Resources [supported] The standard machine is 4 vCPU/8 GiB/100 GB; larger fixed sizes have box-hour multipliers and project size is chosen at creation. Sources: boxes-dev:setup, boxes-dev:plans.
  • Region [unknown] Region is not established. 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.
  • Expiry [partial] Idle sleep normally follows about five minutes and pauses work with files/memory saved. A 24-hour continuous awake interval can briefly pause/resume; maximum storage lifetime is unspecified. Sources: boxes-dev:sleep.
  • Client disconnect [partial] Accepted cloud work keeps running after the originating laptop closes and the same thread can continue on another client. Sleep, limits and provider access can still stop it. Sources: boxes-dev:how, boxes-dev:sleep.
  • Other device continuation [partial] Accepted cloud work keeps running after the originating laptop closes and the same thread can continue on another client. Sleep, limits and provider access can still stop it. Sources: boxes-dev:how, boxes-dev:sleep.

Sources: boxes-dev:how, boxes-dev:setup, boxes-dev:plans, boxes-dev:teams, boxes-dev:sleep

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Checkout [partial] Different devboxes have distinct code copies/files/processes/local services. Threads on one devbox share files and services. Sources: boxes-dev:how, boxes-dev:data.
  • Branch [unknown] Branch is not established. 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.
  • Worktree [unknown] Worktree is not established. 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.
  • Container [unknown] Container is not established. 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.
  • Vm [unknown] Vm is not established. 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.
  • Os sandbox [unknown] Os sandbox is not established. 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.
  • Filesystem [partial] Different devboxes have distinct code copies/files/processes/local services. Threads on one devbox share files and services. Sources: boxes-dev:how, boxes-dev:data.
  • Process [partial] Different devboxes have distinct code copies/files/processes/local services. Threads on one devbox share files and services. Sources: boxes-dev:how, boxes-dev:data.
  • Network [partial] Local ports are per devbox, so the same service ports can be reused. Public previews, shared storage and identical external-service credentials create explicit cross-box access paths. Sources: boxes-dev:how, boxes-dev:data, boxes-dev:storage.
  • Secrets [partial] Authorized services can decrypt saved member files/tokens, and software on the delivered machine can read/use them. Encryption in storage does not isolate secrets from agents on that machine. Sources: boxes-dev:data.
  • Code separation [partial] Different devboxes have distinct code copies/files/processes/local services. Threads on one devbox share files and services. Sources: boxes-dev:how, boxes-dev:data.
  • Security boundary [partial] Documentation establishes resource separation, while external services and delivered secrets remain shared/reachable by design. It does not establish hostile-code containment. Sources: boxes-dev:data, boxes-dev:how.

Sources: boxes-dev:how, boxes-dev:data, boxes-dev:storage

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Client disconnect [supported] The agent can continue in the cloud; saved thread history is readable without waking a machine and clients reopen the same conversation. Sources: boxes-dev:how, boxes-dev:organize.
  • Worker crash [partial] Recovery may restore memory or files from a snapshot. Reset/reboot and follow-ups are documented repair steps, not guaranteed automatic restart of every task. Sources: boxes-dev:sleep.
  • Service restart [partial] Recovery may restore memory or files from a snapshot. Reset/reboot and follow-ups are documented repair steps, not guaranteed automatic restart of every task. Sources: boxes-dev:sleep.
  • Expiry [partial] Sleep saves memory; wake can require network reconnection. Reboot stops every process and sessions do not resume, although files/history survive. Sources: boxes-dev:sleep.
  • Transcript reload [supported] The agent can continue in the cloud; saved thread history is readable without waking a machine and clients reopen the same conversation. Sources: boxes-dev:how, boxes-dev:organize.
  • Process reconnect [partial] Sleep saves memory; wake can require network reconnection. Reboot stops every process and sessions do not resume, although files/history survive. Sources: boxes-dev:sleep.
  • Task resume [partial] After reset/reboot/recovery, inspect Git/files/services, reconnect terminals and send a follow-up. Recovery notices show restored type and snapshot timestamp when known. Sources: boxes-dev:sleep.
  • State reconstruction [partial] After reset/reboot/recovery, inspect Git/files/services, reconnect terminals and send a follow-up. Recovery notices show restored type and snapshot timestamp when known. Sources: boxes-dev:sleep.
  • Context loss [partial] Reboot loses unsaved memory; recovery can lose work since the saved snapshot. Restoring archived automation history does not recover a destroyed filesystem. Sources: boxes-dev:sleep, boxes-dev:schedules.
  • Duplicate actions [unknown] Duplicate actions is not established. 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.
  • Manual repair [partial] After reset/reboot/recovery, inspect Git/files/services, reconnect terminals and send a follow-up. Recovery notices show restored type and snapshot timestamp when known. Sources: boxes-dev:sleep.
  • Multi day continuity [unknown] Multi day continuity is not established. 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.

Sources: boxes-dev:sleep, boxes-dev:organize, boxes-dev:cli, boxes-dev:schedules, boxes-dev:how

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
10 atomic answers
  • Dependencies [supported] Setup agents prepare a template, validate the app and snapshot it for future devboxes; Team Templates provide shared starting environments. Sources: boxes-dev:how, boxes-dev:setup.
  • Caches [partial] Saved dependencies in the template avoid redoing that setup for each devbox. Shared /project storage is explicitly unsuitable for package caches/build trees; general cache correctness is unestablished. Sources: boxes-dev:how, boxes-dev:storage.
  • Snapshots [supported] Setup agents prepare a template, validate the app and snapshot it for future devboxes; Team Templates provide shared starting environments. Sources: boxes-dev:how, boxes-dev:setup.
  • Services [partial] Startup scripts can launch services; separate devboxes reuse port numbers without collision. Threads on one devbox and shared hosted services still share state. Sources: boxes-dev:how, boxes-dev:lifecycle.
  • Ports [partial] Startup scripts can launch services; separate devboxes reuse port numbers without collision. Threads on one devbox and shared hosted services still share state. Sources: boxes-dev:how, boxes-dev:lifecycle.
  • Secrets [partial] Project/member environment values and files are delivered with scoped settings; agent-accessible copies still require credential hygiene. Sources: boxes-dev:environment, boxes-dev:data.
  • Duplicate installs [partial] Saved dependencies in the template avoid redoing that setup for each devbox. Shared /project storage is explicitly unsuitable for package caches/build trees; general cache correctness is unestablished. Sources: boxes-dev:how, boxes-dev:storage.
  • Collisions [partial] Startup scripts can launch services; separate devboxes reuse port numbers without collision. Threads on one devbox and shared hosted services still share state. Sources: boxes-dev:how, boxes-dev:lifecycle.
  • Remote setup [supported] Setup agents prepare a template, validate the app and snapshot it for future devboxes; Team Templates provide shared starting environments. Sources: boxes-dev:how, boxes-dev:setup.
  • Automatic repair [partial] Managed settings/member files are re-applied, and documented resets can repair machines. Arbitrary dependency/service diagnosis is not guaranteed. Sources: boxes-dev:settings, boxes-dev:data, boxes-dev:sleep.

Sources: boxes-dev:how, boxes-dev:lifecycle, boxes-dev:environment, boxes-dev:storage, boxes-dev:setup, boxes-dev:data, boxes-dev:settings, boxes-dev:sleep

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
8 atomic answers
  • Time limits [partial] Claude chat background commands default to 30 minutes with a two-hour maximum. Other sleep protections have different bounds and do not necessarily terminate commands. Sources: boxes-dev:sleep.
  • Turn limits [unknown] Turn limits is not established. 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.
  • Token limits [partial] Codex goals expose a token-budget-limited state; provider limits remain separately enforced and unknown marginal subscription cost is not zero. Sources: boxes-dev:goals, boxes-dev:models.
  • Spend limits [partial] Included hours/prepaid credits and awake capacity block new setup/wakes/runs. Existing awake connections can survive a billing block until sleep; optional auto-reload changes spend behavior. Sources: boxes-dev:billing, boxes-dev:plans.
  • Timeouts [partial] Claude chat background commands default to 30 minutes with a two-hour maximum. Other sleep protections have different bounds and do not necessarily terminate commands. Sources: boxes-dev:sleep.
  • Retries [partial] Auto account rotation and optional API fallback recover some usage limits, with restart consequences. Failed wake can return to sleep for explicit retry. General provider retries are unestablished. Sources: boxes-dev:agents, boxes-dev:sleep.
  • Provider failures [partial] Auto account rotation and optional API fallback recover some usage limits, with restart consequences. Failed wake can return to sleep for explicit retry. General provider retries are unestablished. Sources: boxes-dev:agents, boxes-dev:sleep.
  • Enforcement [partial] Included hours/prepaid credits and awake capacity block new setup/wakes/runs. Existing awake connections can survive a billing block until sleep; optional auto-reload changes spend behavior. Sources: boxes-dev:billing, boxes-dev:plans.

Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:goals, boxes-dev:sleep, boxes-dev:agents, boxes-dev:models

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
13 atomic answers
  • Logs [supported] Run history records starting/ready/skipped/failed, reason, trigger and time; threads retain agent output/errors. Ready records launch only. Sources: boxes-dev:schedules.
  • Traces [unknown] Traces is not established. 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.
  • Failure reasons [supported] Run history records starting/ready/skipped/failed, reason, trigger and time; threads retain agent output/errors. Ready records launch only. Sources: boxes-dev:schedules.
  • Usage export [unknown] Usage export is not established. 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.
  • Task stats [partial] Per-thread model/token/context charts have hourly/daily views, while automation history retains launch settings. This is partial activity accounting, not an independent task success measure. Sources: boxes-dev:models, boxes-dev:schedules.
  • Agent stats [partial] Per-thread model/token/context charts have hourly/daily views, while automation history retains launch settings. This is partial activity accounting, not an independent task success measure. Sources: boxes-dev:models, boxes-dev:schedules.
  • Project stats [partial] Compute history exposes the owner's per-box contributions; it is not a complete project/task/epic statistics model. Sources: boxes-dev:billing.
  • Time stats [partial] Per-thread model/token/context charts have hourly/daily views, while automation history retains launch settings. This is partial activity accounting, not an independent task success measure. Sources: boxes-dev:models, boxes-dev:schedules.
  • Failure status [supported] Run history records starting/ready/skipped/failed, reason, trigger and time; threads retain agent output/errors. Ready records launch only. Sources: boxes-dev:schedules.
  • Approval status [partial] Pending-input alerts remain visible; MCP calls an agent's sleeping/unresponsive work unconfirmed rather than assuming it finished. Older machine status bugs are documented. Sources: boxes-dev:notifications, boxes-dev:mcp-server.
  • Reconnect consistency [partial] Pending-input alerts remain visible; MCP calls an agent's sleeping/unresponsive work unconfirmed rather than assuming it finished. Older machine status bugs are documented. Sources: boxes-dev:notifications, boxes-dev:mcp-server.
  • Performance method [partial] This profile records source/code findings only and makes no speed or success measurements. Saved activity may differ from provider billing. Sources: boxes-dev:models.
  • Responsiveness [unknown] Responsiveness is not established. 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.

Sources: boxes-dev:models, boxes-dev:sleep, boxes-dev:schedules, boxes-dev:mcp-server, boxes-dev:billing, boxes-dev:notifications

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
14 atomic answers
  • Task cost [partial] Per-thread saved tokens/calls/context are visible, but no reconciled per-task or session dollar cost is established. Missing history is identified rather than zeroed. Sources: boxes-dev:models.
  • Session cost [partial] Per-thread saved tokens/calls/context are visible, but no reconciled per-task or session dollar cost is established. Missing history is identified rather than zeroed. Sources: boxes-dev:models.
  • Child cost [unknown] Child cost is not established. 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.
  • Epic cost [unknown] Epic cost is not established. 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.
  • Harness aggregation [unknown] Harness aggregation is not established. 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.
  • Billed vs estimated [partial] Per-thread saved tokens/calls/context are visible, but no reconciled per-task or session dollar cost is established. Missing history is identified rather than zeroed. Sources: boxes-dev:models.
  • Tokens [partial] Thread activity and subscription limits/reset times are shown. Provider accounting can differ; OpenRouter/Vercel/custom billing totals remain in their dashboards. Sources: boxes-dev:models, boxes-dev:agents.
  • Subscription allowance [partial] Thread activity and subscription limits/reset times are shown. Provider accounting can differ; OpenRouter/Vercel/custom billing totals remain in their dashboards. Sources: boxes-dev:models, boxes-dev:agents.
  • Provider reconciliation [partial] Thread activity and subscription limits/reset times are shown. Provider accounting can differ; OpenRouter/Vercel/custom billing totals remain in their dashboards. Sources: boxes-dev:models, boxes-dev:agents.
  • Compute cost [partial] Compute history reports own box-hours for completed hourly windows, updating on the hour, with hourly/daily bars and top-six per-box contributions. It is separate from model usage. Sources: boxes-dev:billing.
  • Refresh delay [partial] Compute history reports own box-hours for completed hourly windows, updating on the hour, with hourly/daily bars and top-six per-box contributions. It is separate from model usage. Sources: boxes-dev:billing.
  • Alerts [partial] Billing shows credit/capacity blocks and optional auto-reload limits. Universal per-task dollar budget alerts are unestablished. Sources: boxes-dev:billing.
  • Export [unknown] Export is not established. 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.
  • Drilldown [partial] Compute history reports own box-hours for completed hourly windows, updating on the hour, with hourly/daily bars and top-six per-box contributions. It is separate from model usage. Sources: boxes-dev:billing.

Sources: boxes-dev:models, boxes-dev:agents, boxes-dev:billing

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Concurrency [partial] Plans cap awake devboxes per user and fix project machine size. Several threads share a machine; a team's overage credit pool is shared. Sources: boxes-dev:plans, boxes-dev:how, boxes-dev:billing.
  • Queues [partial] At capacity interactive work asks to sleep another box; schedules can retry in a configured window or sleep an idle box. Independent event runs remain subject to the same cap. Sources: boxes-dev:plans, boxes-dev:schedules.
  • Cpu ram [partial] Plans cap awake devboxes per user and fix project machine size. Several threads share a machine; a team's overage credit pool is shared. Sources: boxes-dev:plans, boxes-dev:how, boxes-dev:billing.
  • Backpressure [partial] At capacity interactive work asks to sleep another box; schedules can retry in a configured window or sleep an idle box. Independent event runs remain subject to the same cap. Sources: boxes-dev:plans, boxes-dev:schedules.
  • Host awareness [unknown] Host awareness is not established. 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.
  • Check reuse [unknown] Check reuse is not established. 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.
  • Check deduplication [unknown] Check deduplication is not established. 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.
  • Bounded tests [unknown] Bounded tests is not established. 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.
  • Cancellation [partial] Users can pause automations, stop a response or sleep machines. Queued messages and saved future checks require separate cancellation; failed wake has explicit retry/reboot paths. Sources: boxes-dev:schedules, boxes-dev:threads, boxes-dev:sleep.
  • Fairness [unknown] Fairness is not established. 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.
  • Recovery [partial] Users can pause automations, stop a response or sleep machines. Queued messages and saved future checks require separate cancellation; failed wake has explicit retry/reboot paths. Sources: boxes-dev:schedules, boxes-dev:threads, boxes-dev:sleep.
  • Shared limits [partial] Plans cap awake devboxes per user and fix project machine size. Several threads share a machine; a team's overage credit pool is shared. Sources: boxes-dev:plans, boxes-dev:how, boxes-dev:billing.

Sources: boxes-dev:plans, boxes-dev:schedules, boxes-dev:sleep, boxes-dev:how, boxes-dev:billing, boxes-dev:threads

Human collaboration and control

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
official-integration
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
11 atomic answers
  • Visibility [supported] Authorized teammates can read shared workbench transcripts/media; Slack requests are visible in their channel and the owner's Boxes.dev thread. Private-channel tasks start private in Boxes.dev. Sources: boxes-dev:organize, boxes-dev:slack-shared-prompting.
  • Discussion [partial] Slack thread context and mentioned follow-ups support discussion around the same agent task. This does not establish a native issue discussion entity. Sources: boxes-dev:slack-shared-prompting.
  • Comments [partial] Authorized teammates can supply instructions and follow-ups in the linked Slack thread. This is separate from owner-created line comments in the workbench. Sources: boxes-dev:slack-shared-prompting.
  • Presence [unknown] Live presence indicators for other humans viewing or prompting a task are not established by the public guides or closed application. Authorized Slack follow-ups and sender attribution do not establish live presence.
  • Coprompting [supported] An owner can allow teammates to send follow-ups in linked Slack threads, including work the owner started, reaching the same agent conversation. Shared workbench views remain read-only. Both users need linked Slack accounts and active membership in the same Boxes.dev team. Sources: boxes-dev:slack-shared-prompting, boxes-dev:organize.
  • Ordering [partial] Follow-ups join the active turn as Steer by default; the automation owner can choose Queue to wait for the current turn. The guide does not define a stronger concurrent-input conflict protocol. Sources: boxes-dev:slack-shared-prompting.
  • Conflicts [unknown] Formal conflict handling for simultaneous instructions from several humans is not established by the Slack guide or closed backend.
  • Attribution [supported] The agent is told who sent each follow-up and that it runs in the owner's project with the owner's credentials. Requests appear in Slack and in the owner's Boxes.dev thread. Sources: boxes-dev:slack-shared-prompting.
  • Permissions [supported] The owner grants selected or any linked teammates access, with No one as the default. Teammates cannot grant themselves access. Allowed channels, active team membership and owner membership in private channels constrain access. Sources: boxes-dev:slack-shared-prompting.
  • Plan restrictions [partial] Slack work uses the owner's automation, credentials and usage and is subject to awake-devbox/billing limits. A separate plan gate or guaranteed two-person trial entitlement is not enumerated. Sources: boxes-dev:slack-shared-prompting, boxes-dev:plans.
  • Owner online [partial] Work runs on the owner's cloud devbox and does not need their laptop to stay connected. Slack authorization, linked accounts and channel access still apply. Sources: boxes-dev:slack-shared-prompting, boxes-dev:how.

Sources: boxes-dev:organize, boxes-dev:roles, boxes-dev:transfer, boxes-dev:slack-shared-prompting, boxes-dev:how, boxes-dev:plans

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Documented Admin/Member controls; SSO/SCIM only advertised for custom Teams arrangements · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
9 atomic answers
  • Organization roles [supported] Admins invite/remove members, change other members' roles and manage team templates/integrations/billing; Members use published templates and their own projects. Sources: boxes-dev:roles.
  • Project roles [partial] Each person owns their projects/devboxes and agent accounts; shared workbenches are read-only. Fine-grained native task roles are unestablished. Sources: boxes-dev:roles.
  • Task roles [partial] Each person owns their projects/devboxes and agent accounts; shared workbenches are read-only. Fine-grained native task roles are unestablished. Sources: boxes-dev:roles.
  • Membership [supported] Admins invite/remove members, change other members' roles and manage team templates/integrations/billing; Members use published templates and their own projects. Sources: boxes-dev:roles.
  • Sso [partial] Teams marketing lists SSO/SAML/OIDC, SCIM, RBAC and custom terms. Treat them as sales-scoped vendor assertions, not independently inspected enforcement. Sources: boxes-dev:home.
  • Provisioning [partial] Teams marketing lists SSO/SAML/OIDC, SCIM, RBAC and custom terms. Treat them as sales-scoped vendor assertions, not independently inspected enforcement. Sources: boxes-dev:home.
  • Unauthorized access [partial] Thread links require access; removing a member offers transfer/keep/delete, stops running work and pauses automations, with credential cleanup on wake. Immediate revocation of already-read provider tokens is not guaranteed. Sources: boxes-dev:roles, boxes-dev:data.
  • Revocation [partial] Thread links require access; removing a member offers transfer/keep/delete, stops running work and pauses automations, with credential cleanup on wake. Immediate revocation of already-read provider tokens is not guaranteed. Sources: boxes-dev:roles, boxes-dev:data.
  • Plan scope [partial] Teams marketing lists SSO/SAML/OIDC, SCIM, RBAC and custom terms. Treat them as sales-scoped vendor assertions, not independently inspected enforcement. Sources: boxes-dev:home.

Sources: boxes-dev:roles, boxes-dev:home, boxes-dev:data

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
14 atomic answers
  • Command [partial] Claude normally uses Full-access unless a custom policy applies; available Auto/Manual/Plan modes and allow/ask/deny policies govern commands. Boxes.dev operation permissions are separate controls. Sources: boxes-dev:permissions.
  • Tool [partial] Claude normally uses Full-access unless a custom policy applies; available Auto/Manual/Plan modes and allow/ask/deny policies govern commands. Boxes.dev operation permissions are separate controls. Sources: boxes-dev:permissions.
  • Network [supported] Public preview links allow anyone with the URL until revoked. Revocation blocks new requests and closes WebSockets within 30 seconds, but does not erase cached responses or other paths. Sources: boxes-dev:preview.
  • Secret [partial] Files/tokens delivered to machines can be read by their processes. Certain AWS/Tailscale changes need exact action approval, rather than every credential use being prompted. Sources: boxes-dev:data, boxes-dev:permissions.
  • Delivery [unknown] Delivery is not established. 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.
  • Approver identity [supported] Owner controls permit Allow/Deny or project-wide grants; one-time Allow can enable a machine permission until revoked. Settings/template grants last three hours; certain exact integration actions must be applied within ten minutes. Sources: boxes-dev:permissions.
  • Lifetime [supported] Owner controls permit Allow/Deny or project-wide grants; one-time Allow can enable a machine permission until revoked. Settings/template grants last three hours; certain exact integration actions must be applied within ten minutes. Sources: boxes-dev:permissions.
  • Allow [supported] Owner controls permit Allow/Deny or project-wide grants; one-time Allow can enable a machine permission until revoked. Settings/template grants last three hours; certain exact integration actions must be applied within ten minutes. Sources: boxes-dev:permissions.
  • Deny [supported] Owner controls permit Allow/Deny or project-wide grants; one-time Allow can enable a machine permission until revoked. Settings/template grants last three hours; certain exact integration actions must be applied within ten minutes. Sources: boxes-dev:permissions.
  • Revoke [supported] Owner controls permit Allow/Deny or project-wide grants; one-time Allow can enable a machine permission until revoked. Settings/template grants last three hours; certain exact integration actions must be applied within ten minutes. Sources: boxes-dev:permissions.
  • Tunnels [supported] Public preview links allow anyone with the URL until revoked. Revocation blocks new requests and closes WebSockets within 30 seconds, but does not erase cached responses or other paths. Sources: boxes-dev:preview.
  • Defaults [partial] Claude normally uses Full-access unless a custom policy applies; available Auto/Manual/Plan modes and allow/ask/deny policies govern commands. Boxes.dev operation permissions are separate controls. Sources: boxes-dev:permissions.
  • Safer modes [partial] Claude normally uses Full-access unless a custom policy applies; available Auto/Manual/Plan modes and allow/ask/deny policies govern commands. Boxes.dev operation permissions are separate controls. Sources: boxes-dev:permissions.
  • Enforcement [partial] The docs describe product permission requests and separate harness command policies. Closed enforcement code was unavailable, so this is a documented control, not independently audited isolation. Sources: boxes-dev:permissions.

Sources: boxes-dev:permissions, boxes-dev:preview, boxes-dev:data

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
11 atomic answers
  • Actions [partial] Saved conversations and message labels retain who supplied teammate-agent input; automation runs retain prompt/source/model settings despite later configuration edits. Sources: boxes-dev:permissions, boxes-dev:schedules, boxes-dev:organize.
  • Approvals [partial] Pending product permission requests show scope and owner choices. A complete persistent export of every approval/denial is unestablished. Sources: boxes-dev:permissions.
  • Edits [unknown] Edits is not established. 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.
  • Discussion [partial] Saved conversations and message labels retain who supplied teammate-agent input; automation runs retain prompt/source/model settings despite later configuration edits. Sources: boxes-dev:permissions, boxes-dev:schedules, boxes-dev:organize.
  • Decisions [unknown] Decisions is not established. 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.
  • Cross user persistence [unknown] Cross user persistence is not established. 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.
  • Cross session persistence [partial] Saved conversations and message labels retain who supplied teammate-agent input; automation runs retain prompt/source/model settings despite later configuration edits. Sources: boxes-dev:permissions, boxes-dev:schedules, boxes-dev:organize.
  • Export [partial] Copy transcript exports user messages and final agent replies as Markdown, not a full action/audit stream. Sources: boxes-dev:organize.
  • Mutability [partial] Threads/runs can be archived, restored or explicitly deleted; history can be rewound. Advertised audit logs lack an accessible retention/integrity contract in this pass. Sources: boxes-dev:organize, boxes-dev:schedules, boxes-dev:mcp-server, boxes-dev:home.
  • Retention [partial] Threads/runs can be archived, restored or explicitly deleted; history can be rewound. Advertised audit logs lack an accessible retention/integrity contract in this pass. Sources: boxes-dev:organize, boxes-dev:schedules, boxes-dev:mcp-server, boxes-dev:home.
  • Integrity [partial] Threads/runs can be archived, restored or explicitly deleted; history can be rewound. Advertised audit logs lack an accessible retention/integrity contract in this pass. Sources: boxes-dev:organize, boxes-dev:schedules, boxes-dev:mcp-server, boxes-dev:home.

Sources: boxes-dev:organize, boxes-dev:permissions, boxes-dev:schedules, boxes-dev:home, boxes-dev:mcp-server

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
13 atomic answers
  • Pending reviews [unknown] Pending reviews is not established. 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.
  • Change understanding [supported] Open changed files/ranges/PRs in Git/Review, inspect their diffs, navigate to Files and open retained conversation evidence. Sources: boxes-dev:comments, boxes-dev:git.
  • Evidence navigation [supported] Open changed files/ranges/PRs in Git/Review, inspect their diffs, navigate to Files and open retained conversation evidence. Sources: boxes-dev:comments, boxes-dev:git.
  • Comments [supported] Collect file/diff comments into a Code review attachment, edit or remove them, then send the batch as feedback to Codex/Claude. These are not GitHub PR comments. Sources: boxes-dev:comments.
  • Request changes [supported] Collect file/diff comments into a Code review attachment, edit or remove them, then send the batch as feedback to Codex/Claude. These are not GitHub PR comments. Sources: boxes-dev:comments.
  • Shipping guidance [partial] Stage/commit/push/Create PR and PR check/feedback/conflict actions provide next steps; they do not constitute a mandatory independent-review gate. Sources: boxes-dev:git.
  • Effort [unknown] Effort is not established. 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.
  • Missed evidence [unknown] Missed evidence is not established. 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.
  • Keyboard [partial] Desktop shortcuts and mobile file/diff review are documented; full keyboard accessibility and review-quality outcomes were not tested. Sources: boxes-dev:desktop, boxes-dev:mobile.
  • Narrow screen [partial] Desktop shortcuts and mobile file/diff review are documented; full keyboard accessibility and review-quality outcomes were not tested. Sources: boxes-dev:desktop, boxes-dev:mobile.
  • Context switching [unknown] Context switching is not established. 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.
  • Roles [unknown] Roles is not established. 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.
  • Retained context [partial] Comments carry selected file/diff context, but line contents can change and the reviewer must check the revision. Sources: boxes-dev:comments.

Sources: boxes-dev:comments, boxes-dev:git, boxes-dev:mobile, boxes-dev:desktop

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Ongoing takeover [unsupported] Transfer requires an idle agent; it does not transfer an actively running process. Sources: boxes-dev:transfer.
  • Same task [partial] The conversation moves with its history and packaged Git/local changes. Other required data depends on the source agent's package and files already on the destination are preserved. Sources: boxes-dev:transfer.
  • Session history [partial] The conversation moves with its history and packaged Git/local changes. Other required data depends on the source agent's package and files already on the destination are preserved. Sources: boxes-dev:transfer.
  • Decisions [unknown] Decisions is not established. 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.
  • Artifacts [partial] The conversation moves with its history and packaged Git/local changes. Other required data depends on the source agent's package and files already on the destination are preserved. Sources: boxes-dev:transfer.
  • Permissions [partial] Recipient credentials/environment are used. Environment files are excluded, processes are not migrated, and extra-variable/file collisions have explicit limits. Sources: boxes-dev:transfer.
  • Runtime context [partial] Recipient credentials/environment are used. Environment files are excluded, processes are not migrated, and extra-variable/file collisions have explicit limits. Sources: boxes-dev:transfer.
  • Owner disconnect [unknown] Owner disconnect is not established. 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.
  • Ownership [supported] The recipient becomes the continuing owner; the source archives after success, transfer origin is shown and commits retain authors. Sources: boxes-dev:transfer.
  • Attribution [supported] The recipient becomes the continuing owner; the source archives after success, transfer origin is shown and commits retain authors. Sources: boxes-dev:transfer.
  • Context loss [partial] Ignored/out-of-repo data requires agent packaging; failed application retains a package/manual recovery path. It is not guaranteed complete runtime reproduction. Sources: boxes-dev:transfer.
  • Harness transfer [partial] The documented transfer preserves a Codex or Claude conversation in that harness; provider switching in Codex starts without old history. Cross-harness conversion is unestablished. Sources: boxes-dev:transfer, boxes-dev:agents.

Sources: boxes-dev:transfer, boxes-dev:roles, boxes-dev:agents

Verification and delivery

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
13 atomic answers
  • Diffs [partial] Diffs and file previews include text, Markdown, PDFs, images and video. Some published media/saved attachments remain available from history; local file links still depend on current machine contents. Sources: boxes-dev:files, boxes-dev:organize.
  • Documents [partial] Diffs and file previews include text, Markdown, PDFs, images and video. Some published media/saved attachments remain available from history; local file links still depend on current machine contents. Sources: boxes-dev:files, boxes-dev:organize.
  • Screenshots [partial] Diffs and file previews include text, Markdown, PDFs, images and video. Some published media/saved attachments remain available from history; local file links still depend on current machine contents. Sources: boxes-dev:files, boxes-dev:organize.
  • Recordings [partial] Diffs and file previews include text, Markdown, PDFs, images and video. Some published media/saved attachments remain available from history; local file links still depend on current machine contents. Sources: boxes-dev:files, boxes-dev:organize.
  • Previews [supported] Public port links and Project URLs expose a running app, which needs an available machine and explicit sharing. Sources: boxes-dev:preview.
  • Test outputs [unknown] Test outputs is not established. 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.
  • Reviewer outputs [unknown] Reviewer outputs is not established. 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.
  • Persistence [partial] History/attachments link to a thread; destroying a machine archives history but deletes its files. Path-linked media can show changed file contents, so exact-revision artifact retention is incomplete. Sources: boxes-dev:organize, boxes-dev:schedules, boxes-dev:files.
  • Child findings [unknown] Child findings is not established. 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.
  • Prompt leakage [partial] Shared transcripts expose prompts/replies to authorized readers; public app links expose app content to anyone with the URL. Neither is a claim of automatic secret redaction. Sources: boxes-dev:organize, boxes-dev:preview, boxes-dev:data.

Sources: boxes-dev:files, boxes-dev:organize, boxes-dev:preview, boxes-dev:schedules, boxes-dev:data

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
11 atomic answers
  • Tests [partial] Verification can be requested in prompts/goals, and PR checks can trigger agent follow-ups. Required test/lint/type/CI/spec or independent review policy is unestablished. Sources: boxes-dev:instructions, boxes-dev:goals, boxes-dev:git.
  • Lint [partial] Verification can be requested in prompts/goals, and PR checks can trigger agent follow-ups. Required test/lint/type/CI/spec or independent review policy is unestablished. Sources: boxes-dev:instructions, boxes-dev:goals, boxes-dev:git.
  • Types [partial] Verification can be requested in prompts/goals, and PR checks can trigger agent follow-ups. Required test/lint/type/CI/spec or independent review policy is unestablished. Sources: boxes-dev:instructions, boxes-dev:goals, boxes-dev:git.
  • Ci [partial] Verification can be requested in prompts/goals, and PR checks can trigger agent follow-ups. Required test/lint/type/CI/spec or independent review policy is unestablished. Sources: boxes-dev:instructions, boxes-dev:goals, boxes-dev:git.
  • Independent review [partial] Verification can be requested in prompts/goals, and PR checks can trigger agent follow-ups. Required test/lint/type/CI/spec or independent review policy is unestablished. Sources: boxes-dev:instructions, boxes-dev:goals, boxes-dev:git.
  • Spec checks [partial] Verification can be requested in prompts/goals, and PR checks can trigger agent follow-ups. Required test/lint/type/CI/spec or independent review policy is unestablished. Sources: boxes-dev:instructions, boxes-dev:goals, boxes-dev:git.
  • Required checks [partial] Commit requires staged changes, a message, no unresolved conflicts and no other Git action. Pull-and-push only pushes after a successful pull. Broader failed-check blocking is unestablished. Sources: boxes-dev:git.
  • Failure blocking [partial] Commit requires staged changes, a message, no unresolved conflicts and no other Git action. Pull-and-push only pushes after a successful pull. Broader failed-check blocking is unestablished. Sources: boxes-dev:git.
  • Requirement conflicts [unknown] Requirement conflicts is not established. 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.
  • Configured policy [partial] Repository instructions and harness command policies can guide work; the sources do not establish a universal product-enforced quality gate. Sources: boxes-dev:instructions, boxes-dev:permissions.
  • Enforced policy [partial] Repository instructions and harness command policies can guide work; the sources do not establish a universal product-enforced quality gate. Sources: boxes-dev:instructions, boxes-dev:permissions.

Sources: boxes-dev:instructions, boxes-dev:goals, boxes-dev:git, boxes-dev:permissions

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
9 atomic answers
  • Branches [supported] The UI creates/publishes branches, stages hunks, commits, creates draft/reviewer-configured PRs and displays the linked PR state. Sources: boxes-dev:git, boxes-dev:branches.
  • Worktrees [unknown] Worktrees is not established. 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.
  • Commits [supported] The UI creates/publishes branches, stages hunks, commits, creates draft/reviewer-configured PRs and displays the linked PR state. Sources: boxes-dev:git, boxes-dev:branches.
  • Pull requests [supported] The UI creates/publishes branches, stages hunks, commits, creates draft/reviewer-configured PRs and displays the linked PR state. Sources: boxes-dev:git, boxes-dev:branches.
  • Comments [supported] Optional follow-ups batch eligible human/bot feedback and failed checks, then queue work on the responsible agent. Certain bot edits/approvals/self-comments do not trigger work. Sources: boxes-dev:git.
  • Ci response [supported] Optional follow-ups batch eligible human/bot feedback and failed checks, then queue work on the responsible agent. Certain bot edits/approvals/self-comments do not trigger work. Sources: boxes-dev:git.
  • Rebase [supported] Pull-and-push offers repository-default/rebase/merge strategies and only pushes on successful pull. Conflict follow-ups follow repository policy, throttle repeated conflict work and may dismiss GitHub approvals. Sources: boxes-dev:git.
  • Conflicts [supported] Pull-and-push offers repository-default/rebase/merge strategies and only pushes on successful pull. Conflict follow-ups follow repository policy, throttle repeated conflict work and may dismiss GitHub approvals. Sources: boxes-dev:git.
  • Product state [supported] The UI creates/publishes branches, stages hunks, commits, creates draft/reviewer-configured PRs and displays the linked PR state. Sources: boxes-dev:git, boxes-dev:branches.

Sources: boxes-dev:git, boxes-dev:branches

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
6 atomic answers
  • Approve [partial] Review/check state comes from GitHub and commits/branches can change. A product-owned human approval bound to the exact candidate revision is not established. Sources: boxes-dev:git.
  • Merge [supported] Git/Review offers merge for an existing PR, subject to GitHub readiness/permissions and selected merge strategy. This is distinct from PR creation. Sources: boxes-dev:git.
  • Release [unknown] Release is not established. 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.
  • Deploy [unknown] Deploy is not established. 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.
  • Exact revision [partial] Review/check state comes from GitHub and commits/branches can change. A product-owned human approval bound to the exact candidate revision is not established. Sources: boxes-dev:git.
  • Authority enforcement [partial] Review/check state comes from GitHub and commits/branches can change. A product-owned human approval bound to the exact candidate revision is not established. Sources: boxes-dev:git.

Sources: boxes-dev:git, boxes-dev:agents

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
9 atomic answers
  • Delivery status [partial] A merged PR sends its saved thread a landing notice without requesting edits; an agent turn ending alone does not establish delivery. Sources: boxes-dev:git.
  • Retained evidence [partial] Optional Add thread links to commits inserts the selected thread URL when available. PR state/follow-ups link work to its conversation; thread access restrictions still apply. Sources: boxes-dev:git.
  • Rollback [partial] The UI can Revert selected unstaged files/hunks and amend when offered. Full deployment rollback is not established. Sources: boxes-dev:git.
  • Revert [partial] The UI can Revert selected unstaged files/hunks and amend when offered. Full deployment rollback is not established. Sources: boxes-dev:git.
  • Stale approval invalidation [unknown] Stale approval invalidation is not established. 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.

Sources: boxes-dev:git, boxes-dev:comments

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Review queue [partial] User folders and grouped devboxes can organize review work, but a first-class cross-task review queue is not established. Sources: boxes-dev:organize.
  • Summaries [partial] Thread replies, diffs and media supply context; they are not a complete retained child-review gallery or risk-ranked queue. Sources: boxes-dev:organize, boxes-dev:files.
  • Grouping [partial] User folders and grouped devboxes can organize review work, but a first-class cross-task review queue is not established. Sources: boxes-dev:organize.
  • Risk size filters [unknown] Risk size filters is not established. 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.
  • Findings [partial] Thread replies, diffs and media supply context; they are not a complete retained child-review gallery or risk-ranked queue. Sources: boxes-dev:organize, boxes-dev:files.
  • Artifacts [partial] Thread replies, diffs and media supply context; they are not a complete retained child-review gallery or risk-ranked queue. Sources: boxes-dev:organize, boxes-dev:files.
  • Request changes [partial] A Code review attachment batches comments for one thread, then Git actions expose commit/push/PR/merge steps. Sources: boxes-dev:comments, boxes-dev:git.
  • Exact revision approval [unknown] Exact revision approval is not established. 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.
  • Dependency queues [unknown] Dependency queues is not established. 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.
  • Next actions [partial] A Code review attachment batches comments for one thread, then Git actions expose commit/push/PR/merge steps. Sources: boxes-dev:comments, boxes-dev:git.
  • Stale approval invalidation [unknown] Stale approval invalidation is not established. 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.
  • Check deduplication [unknown] Check deduplication is not established. 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.

Sources: boxes-dev:organize, boxes-dev:comments, boxes-dev:git, boxes-dev:files

Ownership, privacy and economics

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
6 atomic answers
  • Client license [partial] The published workstation CLI shim, bootstrap and runtime package metadata are UNLICENSED. This is not an open-source license grant, and does not establish every desktop/mobile component license. Sources: boxes-dev:npm-cli, boxes-dev:npm-runtime.
  • Server license [partial] The hosted service is offered under the vendor's service agreement and any signed cover page. Server source/license is not publicly established. Sources: boxes-dev:terms.
  • Hosted extensions [partial] The hosted service is offered under the vendor's service agreement and any signed cover page. Server source/license is not publicly established. Sources: boxes-dev:terms.
  • Source visibility [partial] Inspected published npm 1.0.1135 packages at recorded SHA-256 pins. Full app/server repositories and upstream Git commits were not found; these are distribution pins, not Git source inspection. Sources: boxes-dev:npm-runtime, boxes-dev:npm-cli.
  • Source revision [partial] Inspected published npm 1.0.1135 packages at recorded SHA-256 pins. Full app/server repositories and upstream Git commits were not found; these are distribution pins, not Git source inspection. Sources: boxes-dev:npm-runtime, boxes-dev:npm-cli.
  • Hosted parity [unknown] Hosted parity is not established. 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.

Sources: boxes-dev:terms, boxes-dev:npm-cli, boxes-dev:npm-runtime, boxes-dev:runtime-desktop

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
8 atomic answers
  • Self hosting [partial] The team brief invites customer-infrastructure discussions, but no downloadable full core/control plane is established. Sources: boxes-dev:teams.
  • Vendor dependencies [partial] Ordinary work uses Boxes.dev account/provisioning/relay and cloud billing; saved code can leave through Git or downloads. Continued account-free orchestration is unestablished. Sources: boxes-dev:how, boxes-dev:setup, boxes-dev:plans, boxes-dev:files.
  • Export [partial] Copy transcript produces Markdown of user and final agent messages; files/code use downloads/Git. This is not a complete agent/tool/account history export. Sources: boxes-dev:organize, boxes-dev:files.
  • Import [partial] Setup and dvb threads import can copy selected local Codex/Claude native history into the project. Import compatibility is scoped to supported native sessions. Sources: boxes-dev:threads, boxes-dev:local.
  • Formats [partial] Copy transcript produces Markdown of user and final agent messages; files/code use downloads/Git. This is not a complete agent/tool/account history export. Sources: boxes-dev:organize, boxes-dev:files.
  • Cancellation [partial] Billing help describes cancellation ending paid seats at the billing period end, while the posted order form separately requires at least 30 days non-renewal notice; the applicable customer agreement needs confirmation, as recorded in OWN-09. Account deletion removes owned machines/data with billing and backup exceptions. No complete history export on cancellation is guaranteed. Sources: boxes-dev:billing, boxes-dev:terms, boxes-dev:data.
  • Account independence [partial] Ordinary work uses Boxes.dev account/provisioning/relay and cloud billing; saved code can leave through Git or downloads. Continued account-free orchestration is unestablished. Sources: boxes-dev:how, boxes-dev:setup, boxes-dev:plans, boxes-dev:files.
  • History portability [partial] Copy transcript produces Markdown of user and final agent messages; files/code use downloads/Git. This is not a complete agent/tool/account history export. Sources: boxes-dev:organize, boxes-dev:files.

Sources: boxes-dev:files, boxes-dev:organize, boxes-dev:threads, boxes-dev:data, boxes-dev:teams, boxes-dev:how, boxes-dev:setup, boxes-dev:plans, boxes-dev:local, boxes-dev:billing, boxes-dev:terms

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
15 atomic answers
  • Code data [supported] Selected code/config/history uploads reach cloud machines; saved thread history also resides in Boxes.dev. Model providers receive task context under their own terms and OpenAI may generate session titles. Sources: boxes-dev:data, boxes-dev:privacy.
  • Prompts [supported] Selected code/config/history uploads reach cloud machines; saved thread history also resides in Boxes.dev. Model providers receive task context under their own terms and OpenAI may generate session titles. Sources: boxes-dev:data, boxes-dev:privacy.
  • Credentials [supported] Integration tokens and member files use scoped encrypted storage but authorized services decrypt them and machine processes can read delivered credentials. Selected private keys can be copied during setup. Revocation must also happen at the provider. Sources: boxes-dev:data.
  • Logs [partial] Project files/terminal history usually live on the devbox; metadata, saved threads, snippets, activity and diagnostic logs are also stored centrally. Shared/published media have separate visibility. Sources: boxes-dev:data, boxes-dev:organize.
  • Artifacts [partial] Project files/terminal history usually live on the devbox; metadata, saved threads, snippets, activity and diagnostic logs are also stored centrally. Shared/published media have separate visibility. Sources: boxes-dev:data, boxes-dev:organize.
  • Retention [partial] Replay is generally retained up to 30 days. Slack connection data is deleted within 14 business days of disconnect/uninstall, but thread content can remain. Account deletion has billing/legal/backup exceptions without a fixed backup expiry. Sources: boxes-dev:privacy, boxes-dev:data.
  • Deletion [partial] Replay is generally retained up to 30 days. Slack connection data is deleted within 14 business days of disconnect/uninstall, but thread content can remain. Account deletion has billing/legal/backup exceptions without a fixed backup expiry. Sources: boxes-dev:privacy, boxes-dev:data.
  • Training [partial] Google integration/Slack data have specific training-use restrictions. No general no-training promise for every customer-content type or every model provider is established. Sources: boxes-dev:privacy.
  • Residency [partial] The policy lists Convex, Cloudflare, Expo, OpenAI title generation, Amplitude and Sentry, with a generically named hosting provider. Data may be processed in the US and other provider locations; selectable residency is unestablished. Sources: boxes-dev:privacy.
  • Subprocessors [partial] The policy lists Convex, Cloudflare, Expo, OpenAI title generation, Amplitude and Sentry, with a generically named hosting provider. Data may be processed in the US and other provider locations; selectable residency is unestablished. Sources: boxes-dev:privacy.
  • Telemetry disclosure [supported] The policy/data guide disclose product analytics, Sentry crash/app logs and masked replay, with different mobile versus web/desktop text masking. Sources: boxes-dev:privacy, boxes-dev:data.
  • Telemetry defaults [unknown] Telemetry defaults is not established. 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.
  • Telemetry controls [unknown] Telemetry controls is not established. 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.
  • Provider separation [supported] Agent-provider terms govern their prompt/context/output processing separately from Boxes.dev orchestration and title generation. Sources: boxes-dev:privacy.

Sources: boxes-dev:data, boxes-dev:privacy, boxes-dev:organize

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Trial, Starter, Pro and Max public monthly billing; custom Teams arrangements separate · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
12 atomic answers
  • Currency [supported] Self-serve paid prices are USD per seat per month; paid plans require at least one paid seat. Seat additions charge pro rata and removal credits unused time on the next bill. Sources: boxes-dev:plans, boxes-dev:billing.
  • Interval [supported] Self-serve paid prices are USD per seat per month; paid plans require at least one paid seat. Seat additions charge pro rata and removal credits unused time on the next bill. Sources: boxes-dev:plans, boxes-dev:billing.
  • Seats [supported] Self-serve paid prices are USD per seat per month; paid plans require at least one paid seat. Seat additions charge pro rata and removal credits unused time on the next bill. Sources: boxes-dev:plans, boxes-dev:billing.
  • Seat minimum [supported] Self-serve paid prices are USD per seat per month; paid plans require at least one paid seat. Seat additions charge pro rata and removal credits unused time on the next bill. Sources: boxes-dev:plans, boxes-dev:billing.
  • Workspace fees [unknown] Workspace fees is not established. 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.
  • Included usage [supported] Trial gives 20 box-hours; Starter/Pro/Max give 50/300/750 per paid user per billing period with per-user capacity/project caps. Trial starts at first machine use and ends on expiry or exhaustion. Sources: boxes-dev:plans.
  • Credits [supported] Further usage draws shared prepaid credits at USD 0.40/box-hour before discounts. Credit purchases require an active paid plan, start at USD 20 and have a USD 1,000/team/month cap; auto-reload is optional. Sources: boxes-dev:plans, boxes-dev:billing.
  • Trial [supported] Trial gives 20 box-hours; Starter/Pro/Max give 50/300/750 per paid user per billing period with per-user capacity/project caps. Trial starts at first machine use and ends on expiry or exhaustion. Sources: boxes-dev:plans.
  • Overages [supported] Further usage draws shared prepaid credits at USD 0.40/box-hour before discounts. Credit purchases require an active paid plan, start at USD 20 and have a USD 1,000/team/month cap; auto-reload is optional. Sources: boxes-dev:plans, boxes-dev:billing.
  • Taxes [unknown] Taxes is not established. 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.
  • Model cost [supported] Native provider subscription/API billing is additional; Boxes.dev does not sell model tokens. Sources: boxes-dev:home, boxes-dev:plans, boxes-dev:agents.
  • Compute cost [partial] One box-hour is one awake standard 4-vCPU/8-GiB hour. Template awake time counts, sleep does not. Larger instances have multipliers; mobile devices/builders use separate credits and rates. Sources: boxes-dev:plans, boxes-dev:billing.

Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:home, boxes-dev:agents

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Illustrative Starter monthly scenario, not a measured benchmark or provider-cost quote · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
11 atomic answers
  • One person [partial] Under the stated 50-box-hour/person monthly Starter scenario, seat charges are USD 19 for one, USD 38 for two collaborating people and USD 95 for five. Provider/model bills and taxes are additional unknowns. Arithmetic uses the public USD 19 seat rate. Sources: boxes-dev:plans.
  • Two people [partial] Under the stated 50-box-hour/person monthly Starter scenario, seat charges are USD 19 for one, USD 38 for two collaborating people and USD 95 for five. Provider/model bills and taxes are additional unknowns. Arithmetic uses the public USD 19 seat rate. Sources: boxes-dev:plans.
  • Five people [partial] Under the stated 50-box-hour/person monthly Starter scenario, seat charges are USD 19 for one, USD 38 for two collaborating people and USD 95 for five. Provider/model bills and taxes are additional unknowns. Arithmetic uses the public USD 19 seat rate. Sources: boxes-dev:plans.
  • Task assumptions [partial] Assume 10 tasks/person/month, 4 awake standard box-hours each, no more than 2 work boxes concurrently/person, and 10 awake template hours/person. This totals 50 box-hours/person and fits Starter's five-awake-box cap plus template. Shared external services still need coordination. Sources: boxes-dev:plans, boxes-dev:how.
  • Concurrency [partial] Assume 10 tasks/person/month, 4 awake standard box-hours each, no more than 2 work boxes concurrently/person, and 10 awake template hours/person. This totals 50 box-hours/person and fits Starter's five-awake-box cap plus template. Shared external services still need coordination. Sources: boxes-dev:plans, boxes-dev:how.
  • Tokens [partial] No token/task amount is measured or assumed; use the user's existing native subscriptions, with marginal allowance and API costs unknown. Mobile/build services and taxes are excluded because their scenario inputs are not specified. Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:agents.
  • Compute hours [partial] Assume 10 tasks/person/month, 4 awake standard box-hours each, no more than 2 work boxes concurrently/person, and 10 awake template hours/person. This totals 50 box-hours/person and fits Starter's five-awake-box cap plus template. Shared external services still need coordination. Sources: boxes-dev:plans, boxes-dev:how.
  • Fixed cost [partial] Under the stated 50-box-hour/person monthly Starter scenario, seat charges are USD 19 for one, USD 38 for two collaborating people and USD 95 for five. Provider/model bills and taxes are additional unknowns. Arithmetic uses the public USD 19 seat rate. Sources: boxes-dev:plans.
  • Variable cost [partial] The scenario consumes each user's 50 included hours and adds no compute overage. An extra 10 standard hours/person would meter USD 4/person at the undiscounted rate, drawing shared prepaid credit bought in minimum USD 20 purchases. Sources: boxes-dev:plans, boxes-dev:billing.
  • Included cost [partial] The scenario consumes each user's 50 included hours and adds no compute overage. An extra 10 standard hours/person would meter USD 4/person at the undiscounted rate, drawing shared prepaid credit bought in minimum USD 20 purchases. Sources: boxes-dev:plans, boxes-dev:billing.
  • Unknown cost [partial] No token/task amount is measured or assumed; use the user's existing native subscriptions, with marginal allowance and API costs unknown. Mobile/build services and taxes are excluded because their scenario inputs are not specified. Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:agents.

Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:how, boxes-dev:agents

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
8 atomic answers
  • Release stage [partial] Public distributions and current self-serve plan/onboarding docs exist, but a formal GA declaration and all signup/region restrictions remain unknown. The Android waitlist wording is preserved as an access caveat. Sources: boxes-dev:plans, boxes-dev:android, boxes-dev:ios.
  • Access restrictions [partial] Public distributions and current self-serve plan/onboarding docs exist, but a formal GA declaration and all signup/region restrictions remain unknown. The Android waitlist wording is preserved as an access caveat. Sources: boxes-dev:plans, boxes-dev:android, boxes-dev:ios.
  • Support [supported] Email, public support page, in-app feedback and CLI report-bug are documented; security has a separate channel. Sources: boxes-dev:support, boxes-dev:security.
  • Response commitments [partial] Vulnerability reports have a three-business-day acknowledgement commitment. It does not establish a general product-support response SLA. Sources: boxes-dev:security, boxes-dev:support.
  • Release activity [supported] The official changelog dates release 1.0.1135 to November 19, with earlier November 16/17 releases. Retrieval and app-store relative dates are not release dates. Sources: boxes-dev:release.
  • Status history [unknown] Status history is not established. 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.
  • Deprecation [unknown] Deprecation is not established. 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.
  • Export options [partial] Files/Git and Markdown transcript copy provide partial exit options, not complete account history export. Sources: boxes-dev:files, boxes-dev:organize.

Sources: boxes-dev:release, boxes-dev:plans, boxes-dev:android, boxes-dev:ios, boxes-dev:support, boxes-dev:security, boxes-dev:files, boxes-dev:organize

No sourced public finding not-published

No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
10 atomic answers
  • Ongoing free [unsupported] The complete public plan list has Trial plus paid Starter/Pro/Max/custom Teams. It establishes finite trial access, not a recurring free compute allowance. Sources: boxes-dev:plans.
  • Trial [partial] Trial starts on first machine use and includes 20 box-hours/user, 3 awake devboxes plus template and 2 projects. It can end by expiry or exhausted hours; exact duration is not specified. Sources: boxes-dev:plans.
  • Credits trial [partial] Trial starts on first machine use and includes 20 box-hours/user, 3 awake devboxes plus template and 2 projects. It can end by expiry or exhausted hours; exact duration is not specified. Sources: boxes-dev:plans.
  • Self host cost [unknown] Self host cost is not established. 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.
  • Paid only [partial] Initial evaluation can be free but continued compute needs a paid seat after trial. Android's early-access/waitlist wording conflicts with an unqualified signup assumption. Sources: boxes-dev:plans, boxes-dev:android.
  • Early access [partial] Initial evaluation can be free but continued compute needs a paid seat after trial. Android's early-access/waitlist wording conflicts with an unqualified signup assumption. Sources: boxes-dev:plans, boxes-dev:android.
  • Free scenarios [partial] A trial can evaluate cloud threads, BYO subscriptions/API, mobile continuation and file/diff review within 20 box-hours. Authorized teammates can also prompt the same agent via Slack, while workbench links stay read-only. Exact two-person trial entitlements and each member's account eligibility remain unestablished; native issue management remains unknown. Sources: boxes-dev:plans, boxes-dev:mobile, boxes-dev:agents, boxes-dev:organize, boxes-dev:slack-shared-prompting.
  • Card required [supported] Some teams must add a payment method; Billing shows the requirement. Starting without a card is documented and later requirements do not interrupt remaining trial. Sources: boxes-dev:plans.
  • Usage caps [partial] The 20-hour and machine/project caps bound evaluation. Trial exhaustion/expiry blocks starting/waking until an admin assigns a paid seat or updates billing. Sources: boxes-dev:plans, boxes-dev:billing.
  • Paid evaluation [partial] The 20-hour and machine/project caps bound evaluation. Trial exhaustion/expiry blocks starting/waking until an admin assigns a paid seat or updates billing. Sources: boxes-dev:plans, boxes-dev:billing.

Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:mobile, boxes-dev:agents, boxes-dev:android, boxes-dev:organize, boxes-dev:slack-shared-prompting

Agent cross-checked partial

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.

Scope
Surfaces: 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 · Plan: Public Trial, Starter, Pro and Max unless a separate team/feature scope is stated · OS: Linux cloud runtime · Execution modes: vendor-managed-cloud · Region: Not specified · Harness: Native Codex and Claude Code; provider features remain harness-specific
Availability
generally-available
Delivery
native
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • 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.
9 atomic answers
  • Units [supported] Public tables define standard and larger-machine box-hours, included per-seat hours, per-user machine/project caps and USD 0.40 paid overage before credit discounts. Sources: boxes-dev:plans.
  • Included limits [supported] Public tables define standard and larger-machine box-hours, included per-seat hours, per-user machine/project caps and USD 0.40 paid overage before credit discounts. Sources: boxes-dev:plans.
  • Overages [supported] Public tables define standard and larger-machine box-hours, included per-seat hours, per-user machine/project caps and USD 0.40 paid overage before credit discounts. Sources: boxes-dev:plans.
  • Compute markup [partial] Compute has a public metered retail rate; infrastructure wholesale cost/markup is not disclosed, so no pass-through or margin claim is made. Sources: boxes-dev:plans.
  • Model markup [supported] The vendor says it does not sell tokens; agent-provider usage is separately paid, rather than passed through as a Boxes.dev token fee. Sources: boxes-dev:home.
  • Minimum commitment [partial] Paid plans need at least one paid seat; overage credit purchases start at USD 20. Enterprise minimums remain quote-specific. Sources: boxes-dev:billing.
  • Cancellation [partial] Billing describes cancellation at period end; the posted order form says at least 30 days' non-renewal notice and separately signed agreements can replace it. The applicable contractual notice needs confirmation. Sources: boxes-dev:billing, boxes-dev:terms.
  • Sales only unknowns [partial] Partially specified: self-serve prices are public, while enterprise pools/resources/terms, taxes and all separate mobile/build rates are not resolved by that table. Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:teams.
  • Transparency classification [partial] Partially specified: self-serve prices are public, while enterprise pools/resources/terms, taxes and all separate mobile/build rates are not resolved by that table. Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:teams.

Sources: boxes-dev:plans, boxes-dev:billing, boxes-dev:home, boxes-dev:terms, boxes-dev:teams

Sources

boxes-dev:home

Boxes.dev product and plans

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.

Kind
vendor-claimed
Locator
Manage your agents; Pricing; For Teams
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:how

How Boxes.dev works

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.

Kind
documented
Locator
Start a thread, get a machine; Continue from any device; Return later
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:desktop

Tour the desktop app

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.

Kind
documented
Locator
Opening platform paragraph; Find your way around; tools and keyboard shortcuts
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:mobile

Use Boxes.dev on your phone

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.

Kind
documented
Locator
Install and open a project; Start or continue a task; Review files and use a terminal
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:cli

Install and use the CLI

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.

Kind
documented
Locator
Install and sign in; switchboard; native interfaces; Agent permissions
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:setup

Choose project setup

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.

Kind
documented
Locator
Choose your starting point; Before you begin; Where setup starts
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:notifications

Notifications

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.

Kind
documented
Locator
Attention markers; desktop defaults; quiet hours; mobile push
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:roles

Team access and roles

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.

Kind
documented
Locator
Members/Admins; remove member; shared environments; static egress
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:billing

Manage billing and usage

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.

Kind
documented
Locator
Hourly history; seat and cancellation rules; credit limits; mobile devices
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:ios

Boxes.dev App Store listing

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.

Kind
documented
Locator
Compatibility; Version History; account prerequisite
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:android

Boxes.dev Google Play listing

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.

Kind
documented
Locator
About this app; Updated on
Source date
2026-11-19
Retrieved
2026-11-21
boxes-dev:npm-cli

Workstation CLI distribution 1.0.1135

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.

Kind
documented
Locator
package.json os/cpu/license/bin; tarball standalone-manifest.json and scripts/postinstall.mjs
Source date
2026-11-19
Retrieved
2026-11-21
boxes-dev:agents

Connect Codex and Claude

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.

Kind
documented
Locator
Connect an account; Add a model provider; account switching and limits
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:models

Models, reasoning, and usage

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.

Kind
documented
Locator
Model and effort pickers; provider restrictions; Inspect recorded activity
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:plans

Plans, seats, and box-hours

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.

Kind
documented
Locator
Self-serve plans; trial rules; capacity; larger machines; Team Template billing
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:local

Local folder setup

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.

Kind
documented
Locator
Review the setup scans; Check the final bundle; Fine-tune what gets copied
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:commands

Agent command reference

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.

Kind
documented
Locator
Resource commands; thread start, read, send, interrupt, wait, artifacts and permissions
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:mcp-server

Connect an outside assistant

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.

Kind
documented
Locator
Connect your assistant; Find or start a task; Stop current work
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:schedules

Schedules and run history

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.

Kind
documented
Locator
Capacity and overlap behavior; run states; cleanup; Slack output
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:api

Trigger an automation through the API

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.

Kind
documented
Locator
Idempotency; configurable input; existing targets; accepted run; status endpoint
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:git

Commit, push, and open a pull request

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.

Kind
documented
Locator
Review/commit; PR creation; merge; automated follow-ups; attribution
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:release

Boxes.dev changelog

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.

Kind
documented
Locator
November 19, 2026, Version 1.0.1135; November 17, Version 1.0.1134
Source date
2026-11-19
Retrieved
2026-11-21
boxes-dev:npm-runtime

Published CLI runtime 1.0.1135

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.

Kind
documented
Locator
package/package.json; dist/bin/dvb.mjs lines 300360-302304; dist/product-docs/references/agent-tools.md and onbox-agent-tools.md
Source date
2026-11-19
Retrieved
2026-11-21
boxes-dev:mcp-client

Add MCP servers

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.

Kind
documented
Locator
Add and authorize a server; project and agent scope
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:plugins

Install agent plugins

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.

Kind
documented
Locator
Destinations; managed plugins; Update or remove
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:instructions

Give useful instructions

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.

Kind
documented
Locator
Ask for checks; Save instructions for future work
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:privacy

Boxes.dev privacy policy

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.

Kind
documented
Locator
Sections 2, 4, 5, 7, 9 and 10
Source date
2026-10-21
Retrieved
2026-11-21
boxes-dev:runtime-desktop

Versioned product documentation in the CLI runtime

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.

Kind
documented
Locator
package/dist/product-docs/references/security-and-data.md, Desktop app logs, line 344
Source date
2026-11-19
Retrieved
2026-11-21
boxes-dev:slack

Work from Slack

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.

Kind
documented
Locator
Team connection; linked account; start and continue requests
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:linear

Work from Linear

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.

Kind
documented
Locator
Start and follow a task; Send a follow-up; Attach work products
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:threads

Start and continue a thread

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.

Kind
documented
Locator
Queue versus Steer; Stop; drafts; attachments; import
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:goals

Keep an agent working toward a goal

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.

Kind
documented
Locator
Set a useful goal; Follow progress; Review before finishing; Claude goals
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:storage

Shared project storage

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.

Kind
documented
Locator
Share Claude project memory; Understand persistence; consistency cautions
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:files

Browse, edit, and transfer files

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.

Kind
documented
Locator
Workspace search; previews; uploads/downloads; conflict handling
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:data

Your data and credentials

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.

Kind
documented
Locator
Copied files; credentials; machine sharing; stored history; deletion
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:organize

Organize and share threads

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.

Kind
documented
Locator
Grouping; search; sharing restrictions; Copy transcript; subagent conversations
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:automation

Create an automation

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.

Kind
documented
Locator
Create, pause, activate, Run now and agent editing
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:permissions

Agent permissions

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.

Kind
documented
Locator
Create and read threads; Message other agents; temporary grants; Claude modes
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:sleep

Sleep, wake, and recover a devbox

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.

Kind
documented
Locator
Automatic sleep; timed checks; Reset; Reboot; recovery notice
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:teams

Boxes.dev for teams

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.

Kind
vendor-claimed
Locator
Infrastructure options; Plans sized around your workflow
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:settings

Agent settings

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.

Kind
documented
Locator
Project JSON/TOML; synchronization; validation; team inheritance
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:lifecycle

Startup, teardown, and maintenance

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.

Kind
documented
Locator
Startup; teardown; template maintenance and GitHub watches
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:environment

Environment files and secrets

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.

Kind
documented
Locator
Environment files; member overrides; propagation
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:transfer

Transfer a thread to a teammate

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.

Kind
documented
Locator
Before transfer; How your work moves; failure handling
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:slack-shared-prompting

Slack teammate authorization and follow-ups

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.

Kind
documented
Locator
Follow up in the same Slack thread; Let teammates start work in your project; private-channel and owner authorization rules
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:preview

Share a running app

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.

Kind
documented
Locator
Public links; stopping sharing
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:comments

Review code and leave comments

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.

Kind
documented
Locator
Comment on file/diff; Review and send the batch; Check the revision
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:branches

Review branch history and add repositories

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.

Kind
documented
Locator
Branch history; repository selector; branch operations
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:terms

Boxes.dev terms of service

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.

Kind
documented
Locator
Cloud Service; Subscription Period; Non-Renewal Notice; data deletion and backups
Source date
2026-10-20
Retrieved
2026-11-21
boxes-dev:support

Contact support

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.

Kind
documented
Locator
Feedback channels; CLI reports; diagnostics
Source date
Not stated
Retrieved
2026-11-21
boxes-dev:security

Security at Boxes.dev

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.

Kind
documented
Locator
Credential guidance; Vulnerability Disclosure Policy; What to expect
Source date
Not stated
Retrieved
2026-11-21

Comparisons with Boxes.dev

Compare Boxes.dev with any other product on adecomparison.com.