50 of 51 criteria have a sourced finding; 46 were also cross-checked by a second agent. Every comparison that includes Capy 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.
Web and desktop clients are documented, a headless Dock CLI hosts threads, and docs state there is no mobile app.
Scope
Surfaces: Capy browser and hosted agent service, Capy desktop 0.7.2, Paired local computer execution, Capy managed execution machines · Version: Capy 0.8.0 (changelog, download, pricing and docs retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud, paired local execution · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-12
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
9 atomic answers
Desktop os [partial] Stable 0.8.0 ships macOS Apple Silicon and Intel, Windows x64, and Linux x64 and arm64. The desktop app needs a desktop session; minimum OS versions were not established. Sources: capy:nov12-download, capy:nov06-desktop.
Mobile apps [unsupported] Docs state there is no mobile app; phones use capy.ai in the browser. Sources: capy:nov06-faq.
Browser [supported] The web app starts agent threads. Sources: capy:nov06-welcome.
Mobile browser [partial] A phone browser can follow threads and review pull requests; on iPhone or iPad adding it to the Home Screen enables push. Review parity was not tested. Sources: capy:nov06-faq, capy:nov06-desktop.
Cli [partial] capy dock is a headless device runner, not a task-control CLI. Sources: capy:nov06-dock.
Editor extensions [unknown] Editor extensions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Task actions [supported] Web threads accept steer, interrupt and queue messages, plus Stop run. Status is set by Capy, not by hand. Sources: capy:nov06-threads.
Notifications [supported] Notification settings control alerts for finished threads and requests, including system and push. Sources: capy:nov06-desktop, capy:nov06-threads.
Cross device continuity [partial] Continue on moves a thread between cloud and devices with branch, commits and uncommitted changes; running processes and ignored files stay behind. Not tested. Sources: capy:nov06-desktop.
Capy runs its own agent plus a Claude Code mode, with a wide provider catalog; other native harnesses were not found.
Scope
Surfaces: Capy browser and hosted agent service, Capy desktop 0.7.2, Paired local computer execution, Capy managed execution machines · Version: Capy 0.8.0 (changelog, download, pricing and docs retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud, paired local execution · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-12
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
5 atomic answers
Harnesses [partial] Capy runs its own agent; Claude Code mode runs on the Claude Agent SDK with Capy tools and subagents. Other external harnesses were not found. Sources: capy:nov06-models-and-pricing.
Model providers [supported] Anthropic, OpenAI, Google, xAI and others, plus gateways, coding plans and custom OpenAI-compatible endpoints; 0.8.0 adds Claude Fable 5.2, Morph (own key) and Ramp Router as a gateway. Sources: capy:nov12-cl080, capy:nov06-models-and-pricing.
Custom adapters [unknown] Custom adapters: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Session integration [partial] Desktop can import selected local Codex and Claude Code sessions; Claude Code mode embeds the Agent SDK. Sources: capy:nov06-download, capy:nov06-models-and-pricing.
Mixed harness operation [partial] A thread picks Capy agent or Claude Code mode by model tab; each subagent can use its own model or connected subscription. Not tested. Sources: capy:nov06-models-and-pricing, capy:nov06-subagents.
Subscriptions, keys and gateways work on every plan; cloud machine time, images and reviews always bill Capy credits.
Scope
Surfaces: Capy browser and hosted agent service, Capy desktop 0.7.2, Paired local computer execution, Capy managed execution machines · Version: Capy 0.8.0 (changelog, download, pricing and docs retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud, paired local execution · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-12
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
The download and pricing pages list only ChatGPT (Codex), Copilot and SuperGrok subscriptions; they omit Claude but no longer say it cannot connect.
7 atomic answers
Agent subscriptions [supported] Docs list Claude Pro or Max (as Claude Code), Codex, GitHub Copilot and SuperGrok subscriptions, and the 0.8.0 note covers Claude-subscription threads. The download and pricing pages name only ChatGPT, Copilot and SuperGrok but no longer say Claude cannot be connected. Sources: capy:nov12-models-and-pricing, capy:nov12-cl080, capy:nov12-download, capy:nov12-pricing-page.
Api accounts [supported] API keys, gateways, coding plans and custom endpoints work on every plan, the free plan included. Sources: capy:nov06-faq, capy:nov06-models-and-pricing.
Vendor credits [supported] Model tokens on credits, machine time, generated images and reviews draw from one organization balance. Sources: capy:nov06-models-and-pricing, capy:nov06-faq.
Local models [partial] Any public HTTPS OpenAI-compatible endpoint works, so localhost is rejected and a tunnel is needed. Ollama Cloud is a listed gateway. Sources: capy:nov06-faq, capy:nov06-models-and-pricing.
Account switching [supported] Connections run in order; Claude Code, Codex and SuperGrok allow several accounts; Copilot allows one per person. Sources: capy:nov06-models-and-pricing.
Vendor account requirement [supported] A Capy account is required to sign in, including on the desktop app. Sources: capy:nov06-desktop.
Provider restrictions [partial] A connected subscription covers tokens only; cloud machine time and reviews still bill Capy credits. The Claude route is contested between Capy pages. Sources: capy:nov06-faq, capy:nov06-download.
Cloud GitHub onboarding, repoless projects, desktop folders and Dock pairing are documented.
Scope
Surfaces: Capy managed execution machines, Capy desktop 0.7.2, Dock CLI headless device, Paired local computer execution, Capy browser and hosted agent service · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud, paired local execution · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
7 atomic answers
First task setup [supported] Sign in, connect the GitHub App, select project repositories and send a model-selected prompt. Sources: capy:nov06-quickstart.
No git [partial] Repoless projects support research and planning, and the desktop app can start threads with no project. No-Git coding was not tested. Sources: capy:nov06-projects, capy:nov06-cl046.
Local git without remote [unknown] Local git without remote: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Hosted git [supported] GitHub.com through the Capy GitHub App. GitHub Enterprise Server and other git hosts are unsupported. Sources: capy:nov06-github, capy:nov06-projects.
A public bearer-key API covers threads, Captains, automations, reviews, usage and issues; capy dock is a device runner.
Scope
Surfaces: Slack, Linear and public API · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
8 atomic answers
Cli [partial] capy dock status, doctor and dirs manage a device. No CLI for creating or steering threads was found. Sources: capy:nov06-dock.
Sdk [unknown] Sdk: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Mcp server [unknown] Mcp server: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Webhooks [supported] Incoming-webhook automations use a credential URL and idempotency key. Sources: capy:nov06-automations.
Authentication [supported] Bearer keys act as an explicit human or service-user principal. Sources: capy:nov06-api-reference-overview.
Stability [partial] The vendor documents additive endpoints and retained legacy /tasks routes. No compatibility test was run. Sources: capy:nov06-api-reference-overview.
MCP servers, marketplace plugins and portable repository instructions are documented.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
Not separately cross-checked
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
7 atomic answers
Mcp client [supported] Threads and their subagents call tools from configured Streamable HTTP or local STDIO MCP servers. Whether the dedicated review agent receives MCP tools is not stated on the current MCP or Review pages. Sources: capy:nov06-integrations-mcp.
Plugins [supported] Verified marketplace plugins plus GitHub plugins bundling MCP servers and skills; Claude Code, Codex and Grok manifests load, hooks are ignored. Sources: capy:nov06-plugins, capy:nov06-faq.
Custom tools [supported] User-configured MCP servers supply custom tools to threads and subagents over Streamable HTTP or STDIO. Sources: capy:gap07-mcp.
Instructions import [supported] Root/nested AGENTS.md, CLAUDE.md fallback and Cursor-style rules are read. Sources: capy:nov06-instructions.
Permission scope [supported] Servers belong to the organization or to one person (Only you) and cover all projects or one project. Any member can turn off an organization server's Enabled switch, which stops all members' threads from using it; individual tools can be hidden from the model on the server page. Sources: capy:nov06-integrations-mcp.
Integration owner [supported] Capy owns Slack, Linear, GitHub and Tailscale integrations; MCP servers and plugins are configured in Capy settings. Sources: capy:nov06-faq, capy:nov06-integrations-mcp.
Prompts, Slack, Linear delegation and native Issues feed durable threads.
Scope
Surfaces: Capy browser and hosted agent service, Slack, Linear and public API · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
Prompt intake [supported] A first prompt creates an agent thread. Sources: capy:nov06-quickstart.
External import [supported] Delegating a Linear issue creates a native session mapped one-to-one to a Capy thread. Sources: capy:nov06-integrations-linear.
Authoritative tracker [partial] Native Issues can hold organization work; Linear stays authoritative for delegated Linear issues. Sources: capy:nov06-cl070, capy:nov06-integrations-linear.
Stable ids [supported] Project codes prefix threads, such as HOME-14; issues have their own codes in the API. Sources: capy:nov06-threads, capy:nov06-api-issues.
Supported edits [partial] Capy may move a delegated Linear issue into a started state and assign itself. Wider Linear edits were not established. Sources: capy:nov06-integrations-linear.
External roundtrips [supported] Later prompts in the same Linear agent session continue its Capy thread. Sources: capy:nov06-integrations-linear.
There is no plan mode; plans live in prompts, Captain notes and Drive, with no acceptance-criteria field.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
7 atomic answers
Plans [partial] No plan mode exists; ask for a spec and the agent waits. A Captain keeps its plan in NOTES.md, and subagent drafts hold prompts. Sources: capy:nov06-faq, capy:nov06-async, capy:nov06-captains.
Acceptance criteria [unknown] Acceptance criteria: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Editors [supported] Subagents start as editable title-and-prompt drafts. Sources: capy:nov06-subagents.
Revisions [partial] Drive keeps saved versions for 24 hours; Edit message keeps the original with a version switcher. Sources: capy:nov06-drive, capy:nov06-threads.
Implementation links [partial] Issues show linked pull requests. A plan file has no documented link to code. Sources: capy:nov06-cl070.
Amendment [supported] Steer, queue or interrupt during a run; subagent drafts stay editable before start. Sources: capy:nov06-threads, capy:nov06-subagents.
Restart persistence [partial] Thread messages and tool output are stored in Capy cloud, and a Captain rereads its plan each wake. Installed-product resume was not tested. Sources: capy:nov06-admin-security, capy:nov06-faq.
Blockers [supported] An issue can block another or relate to it, and the list shows what blocks it. Sources: capy:nov06-cl070, capy:nov06-api-issues.
Readiness [partial] Blocker display and status filters exist; draft subagents do nothing until started. Sources: capy:nov06-cl070, capy:nov06-subagents.
Enforcement [unknown] Enforcement: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
State propagation [partial] Thread status reflects its subagents; a Captain rewrites its digest as crew state changes. Sources: capy:nov06-threads, capy:nov06-captains.
Task to epic [supported] Promote to Captain turns a thread into a Captain. Sources: capy:nov06-captains.
Identity retention [supported] A promoted thread keeps history, pull requests, machine, Slack thread, project, model and members. Sources: capy:nov06-captains.
Workflow constraints [supported] Parallel writers need disjoint files and fresh machines; dependent or overlapping work uses sequential stacked PRs. Sources: capy:nov06-subagents.
Memory [partial] Changelog entries describe Memory keeping what you teach across threads and review findings citing it. It was an experiment when introduced, and current status was not established. Sources: capy:nov06-changelog.
Scope [supported] Organization, personal, project and project-personal drives separate shared and personal context. Sources: capy:nov06-drive.
Provenance [supported] Drive history names saved versions and the threads that made them. Sources: capy:nov06-drive.
Correction [supported] Restore brings back an earlier version as a new version. Sources: capy:nov06-drive.
Deletion [supported] Agents can update or remove saved Drive files on request. Sources: capy:nov06-drive.
Freshness [partial] Repository instruction changes apply to later threads and subagents; Settings shows what loads before the first message. Sources: capy:nov06-instructions, capy:nov06-cl070.
Takeover continuity [partial] Anyone with access can read another thread; @ mention or a code lets an agent pick up from it. Sources: capy:nov06-async.
Images, files and scoped Slack context are documented; architecture indexing and review enforcement are unverified.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.8.0 (changelog, download, pricing and docs retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-12
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
10 atomic answers
Code search [unknown] Code search: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Indexing [unknown] Indexing: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
External knowledge [partial] Slack integration lets agents read and search workspace messages within configured access. Sources: capy:nov06-integrations-slack.
Multimodal inputs [supported] Images and files can be attached to thread or Slack prompts; 0.8.0 adds comments pinned on images and video frames and voice input in every composer. Sources: capy:nov12-cl080, capy:nov06-threads, capy:nov06-integrations-slack.
Freshness [unknown] Freshness: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Access scope [unknown] Access scope: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Api retrieval [unknown] Api retrieval: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Citations [partial] A review finding lists the rules, memory and telemetry it rests on, per changelog. Sources: capy:nov06-changelog.
Conflict detection [unknown] Conflict detection: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Review enforcement [partial] The review agent enforces repository AGENTS.md conventions as findings. Sources: capy:nov06-review.
Edit [supported] Issue fields update in the app and API; thread titles and subagent drafts are editable. Sources: capy:nov06-api-issues, capy:nov06-threads.
Discuss [supported] Issues have comments, and the owning thread wakes on a comment. Sources: capy:nov06-cl070.
Prioritize [unknown] Prioritize: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Project epic views [partial] Issue views cover For you, Assigned to me and Mentioned; sub-issues nest, and 0.8.0 adds a Display menu that groups and orders issues. An epic board was not established. Sources: capy:nov12-cl080, capy:nov06-cl070.
Idea parking [supported] An issue can exist without a running thread; threads pick up work from Issues. Sources: capy:nov06-cl070, capy:nov06-api-issues.
Explicit dispatch [partial] Issues link to threads, and Captains take work from them. An explicit ready-to-dispatch control was not established. Sources: capy:nov06-cl070, capy:nov06-api-issues.
Task session separation [supported] Issues are separate records linked to threads and pull requests. Sources: capy:nov06-api-issues.
Durable states [supported] Issue states are configurable through the API, and threads have Working, Waiting, Failed and Idle. Sources: capy:nov06-api-issues, capy:nov06-threads.
External tracker requirement [supported] Web threads are usable without a Linear connection. Sources: capy:nov06-quickstart.
Update [supported] Threads update and close issues. Sources: capy:nov06-cl070.
Claim [partial] The thread that owns an issue wakes on comments. A claim operation was not found. Sources: capy:nov06-cl070.
Assign [unknown] Assign: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Children [supported] Subagents form a visible positional hierarchy. Sources: capy:nov06-subagents.
Results [supported] Children send summaries and blocked questions to their parent. Sources: capy:nov06-subagents.
Human visibility [supported] Draft title/prompt and child status are inspectable. Sources: capy:nov06-subagents.
Attribution [unknown] Attribution: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Conflicts [unknown] Conflicts: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Repository specification files and Drive support an instruction-based spec workflow with human and agent edits and short version history. Dedicated specification links and drift detection remain unknown.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy docs retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-07
This is a file and instruction workflow; dedicated specification governance and drift checks were not established.
9 atomic answers
Persistent requirements [partial] A user can request a repository spec before implementation and save approved checklists or reference files in Drive across threads. This is a file workflow, not a separate specification entity. Sources: capy:gap07-async, capy:gap07-drive.
Human edits [partial] People can edit Drive files in the browser; this can include manually saved specifications. Sources: capy:gap07-drive.
Agent edits [partial] Agents can update or remove saved Drive files on request and automatically save changes as work completes. Sources: capy:gap07-drive.
Revisions [partial] Drive history names the threads that saved versions and restores an older version as a new one; history lasts 24 hours. Sources: capy:gap07-drive.
Approvals [partial] The documented spec-first prompt asks the agent to stop for changes or a go-ahead. This is instruction-based approval, not an enforced specification gate. Sources: capy:gap07-async.
Implementation links [unknown] Implementation links: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Later retrieval [partial] Files saved in a Drive scope are available to subsequent threads in that scope. Sources: capy:gap07-drive.
Drift detection [unknown] Drift detection: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Review integration [unknown] Review integration: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Concurrent child agents and thread-level activity aggregation are documented.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
5 atomic answers
Concurrent sessions [supported] Subagents can work in parallel with separate conversations. Sources: capy:nov06-subagents.
Concurrent tasks [supported] Parallel writers use disjoint files and separate PRs. Sources: capy:nov06-subagents.
Quotas [partial] Pricing lists unlimited concurrent threads, bounded by plan RAM capacity: Lite 128 GB, Pro 512 GB, Max 1 TB. Capacity enforcement not tested. Sources: capy:nov06-pricing-page.
Observed concurrency [unknown] Observed concurrency: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Status visibility [supported] Active thread status includes its working subagents. Sources: capy:nov06-threads.
Duplicate prevention [partial] API thread creation uses requestId for retries of the same creation. This is not task ownership locking. Sources: capy:nov06-api-reference-overview.
Ownership enforcement [unknown] Ownership enforcement: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Model harness effort [partial] Each child can choose a model or connected subscription; Claude Code mode is a separate harness. Effort per child was not established. Sources: capy:nov06-subagents, capy:nov06-models-and-pricing.
Messages [supported] Children send summaries or blocked questions; the parent reads interim progress on demand. Sources: capy:nov06-subagents.
Results return [supported] Final summaries wake the parent. Sources: capy:nov06-subagents.
Orchestration owner [supported] The thread agent coordinates children; sibling threads can coordinate long-lived work. Sources: capy:nov06-subagents.
Activation [supported] Ask the agent to split work; child drafts wait until started. Sources: capy:nov06-subagents.
Authentication [unknown] Authentication: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Live progress [partial] Interim progress is read on demand, not streamed into the parent automatically. Sources: capy:nov06-subagents.
Stored prompts support cron, GitHub/Slack events, webhooks and standing or fresh threads.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
8 atomic answers
Schedules [supported] Five-field cron with IANA timezone and a five-minute minimum. Sources: capy:nov06-automations.
Events [supported] GitHub, Slack, incoming webhooks and on-demand triggers, plus agent timers and watches. Sources: capy:nov06-automations, capy:nov06-async.
Recurring tasks [supported] An automation can create a new thread per run or reuse one standing thread. Sources: capy:nov06-automations.
Completion conditions [unknown] Completion conditions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Overlaps [unknown] Overlaps: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Retries [partial] Webhook Idempotency-Key deduplicates retries of one delivery. General failed-run retry policy remains unverified. Sources: capy:nov06-automations.
Client independence [partial] The agent loop runs in the cloud after the tab closes. A device thread still needs that device. Sources: capy:nov06-async, capy:nov06-desktop.
Steer, interrupt and queued messages coexist with Stop run, Needs you and Failed status.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
10 atomic answers
Pause [unknown] Pause: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Stop [supported] Stop run stops the agent; interrupt stops the current generation; subagents keep running. Sources: capy:nov06-threads, capy:nov06-async.
Resume [supported] A message continues the thread, and a message or Unarchive restores an archived one. Sources: capy:nov06-threads.
Steer [supported] Steer delivers at the next step; Queue waits for the active work to finish. Sources: capy:nov06-threads.
Notifications [supported] Notification settings cover requests and failures. Sources: capy:nov06-threads.
Escalation [supported] Blocked child questions surface to the parent. Sources: capy:nov06-subagents.
Visible errors [supported] Failed status with a persistent error card. Sources: capy:nov06-threads.
Chat terminal parity [unknown] Chat terminal parity: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Retained history [supported] Threads keep conversation, machines, subagents and pull requests. Sources: capy:nov06-threads.
Status, Needs you, Captain digests and issue blockers support an overview; no fleet fixture was run.
Scope
Surfaces: Capy managed execution machines, Capy browser and hosted agent service · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
8 atomic answers
Fleet fixture [unknown] Fleet fixture: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Parent child [supported] Child positional hierarchy and statuses are documented. Sources: capy:nov06-subagents.
Dependencies [partial] Issue lists show blockers. A graph view was not found. Sources: capy:nov06-cl070.
History [partial] Full-text search covers thread titles, codes, subagent titles and message content. Archived-search coverage was not established. Sources: capy:nov06-threads.
Navigation errors [unknown] Navigation errors: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Fixture mode [unknown] Fixture mode: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Live roles [partial] Overview lists subagents, pull requests and side threads; a Captain lists its crew. Sources: capy:nov06-async, capy:nov06-captains.
Discoverability [partial] Docs compare side chats, forks, subagents and crew threads. Sources: capy:nov06-async.
Auth friction [partial] Crew threads use the owner’s GitHub access and connections; reviews bill credits. Sources: capy:nov06-captains, capy:nov06-review.
Hybrid [supported] Continue on moves a thread between cloud and devices, and a Captain can run on either. Sources: capy:nov06-desktop, capy:nov06-captains.
Expiry [supported] A machine sleeps about 2 minutes after work stops. A cloud machine sleeping for 14 days is deleted; the thread remains, its next run recreates the environment and unpushed changes are lost. Sources: capy:nov21-machines-retention, capy:nov21-cl080-retention.
Client disconnect [supported] Cloud threads continue after the laptop closes; device threads wait up to 24 hours while offline. Sources: capy:nov06-desktop.
Other device continuation [partial] Any browser can start, follow and reply while the device is online. Sources: capy:nov06-desktop.
Cloud threads use Firecracker microVMs; device threads use worktrees and are explicitly not sandboxed.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
12 atomic answers
Checkout [supported] Fresh writers start from a clean upstream checkout; a device thread can use Current checkout. Sources: capy:nov06-subagents, capy:nov06-desktop.
Branch [supported] Agents push their own branch and never the base branch. Sources: capy:nov06-pull-requests.
Worktree [supported] New worktree is the default on devices, under ~/.capy/worktrees. Sources: capy:nov06-desktop.
Container [partial] Docker runs inside the VM. The product does not isolate work in containers. Sources: capy:nov06-machines.
Vm [supported] Firecracker microVM with its own kernel, per cloud thread. Sources: capy:nov06-machines.
Os sandbox [unsupported] On a device the agent acts as you, and a linked folder is not a sandbox. Sources: capy:nov06-admin-security.
Filesystem [partial] Shared children see parent uncommitted files; separate machines transfer files explicitly. Sources: capy:nov06-subagents, capy:nov06-machines.
Process [unknown] Process: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Network [unknown] Network: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Secrets [partial] Variables are encrypted and hidden from prompts, but code on the machine can read them. Sources: capy:nov06-secrets.
Code separation [supported] Parallel writers use disjoint files and fresh machines. Sources: capy:nov06-subagents.
Security boundary [partial] Cloud machines hold no GitHub token and are isolated from other customers. Device threads have no sandbox. Sources: capy:nov06-admin-security, capy:nov06-machines.
Thread history persists; an expired cloud machine is recreated from Setup and unpushed work is lost.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.8.0 (changelog, download, pricing and docs retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-21
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
Retention and machine replacement were rechecked on 2026-11-21. Other execution details retain their original source dates.
12 atomic answers
Client disconnect [supported] Managed cloud thread history persists after client closure. Sources: capy:nov06-threads.
Worker crash [unknown] Worker crash: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Service restart [unknown] Service restart: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Expiry [supported] A cloud machine sleeping for 14 days is deleted. The thread remains; its next run recreates the environment and unpushed changes are lost. Sources: capy:nov21-machines-retention, capy:nov21-cl080-retention.
Transcript reload [partial] Messages and tool output are stored in Capy cloud. Sources: capy:nov06-admin-security.
Process reconnect [unsupported] Sleep preserves disk, but memory/processes/connections do not survive; startup scripts restart configured services. Sources: capy:nov06-machines.
Task resume [partial] A message continues a thread; a device thread continues on reconnect. Sources: capy:nov06-desktop.
State reconstruction [partial] A deleted machine is recreated from the dev environment setup and unpushed work is lost. Durable machine identity is not established by these sources. Sources: capy:nov21-machines-retention, capy:nov21-cl080-retention.
Context loss [partial] Pushed code and Drive files survive replacement; unpushed edits and scratch state do not. Sources: capy:nov06-machines.
Duplicate actions [unknown] Duplicate actions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Manual repair [partial] Ask Capy to rebuild lost work from the thread history. Sources: capy:nov06-trouble.
Caches [supported] Project snapshots cache the post-setup filesystem, including installed dependencies. A restored checkout runs refresh only when its HEAD changes. Sources: capy:gap07-environment.
Snapshots [supported] Snapshot restores use the setup recipe; missing/failed snapshots fall back to fresh setup. Sources: capy:nov06-environment.
Services [supported] Ordered startup entries run per boot and can publish service ports. Sources: capy:nov06-environment.
Ports [partial] Exposed ports get preview URLs while the machine is awake; some ports are reserved. Sources: capy:nov06-machines.
Secrets [partial] Project variables are loaded at boot; scoped encrypted secrets are written to authorized machines. Command output can reveal values. Sources: capy:nov06-environment, capy:nov06-admin-security.
Duplicate installs [partial] A snapshot restore skips clone and initialize; missing or failed snapshots fall back to full setup. This reduces repeated setup but does not prove all installs are deduplicated. Sources: capy:gap07-environment.
Collisions [unknown] Collisions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Remote setup [supported] Project setup can be changed in the app, agent tools or repository .capy/setup.json. Sources: capy:nov06-environment.
Automatic repair [partial] A failed setup still starts the machine with a warning; capy-setup can repair setup. Sources: capy:nov06-trouble, capy:nov06-skills.
Credits and connection exhaustion have visible stop/recovery behavior; broad failure guarantees are unverified.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
8 atomic answers
Time limits [partial] A waited-on command keeps a machine awake for at most 6 hours. Sources: capy:nov06-async.
Turn limits [unknown] Turn limits: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Token limits [unknown] Token limits: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Spend limits [supported] Out-of-credit threads stop; adding balance plus a new message resumes. Auto-reload can have a hard monthly cap. Sources: capy:nov06-admin-billing.
Timeouts [partial] initialize defaults to 900 s and refresh to 300 s. Sources: capy:nov06-environment.
Retries [unknown] Retries: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Provider failures [partial] A limited subscription or disabled, signed-out or rejected connection can wait or fall through under owner/org settings. An API key with no credit fails with its provider error; fallback settings do not apply. Sources: capy:nov06-models-and-pricing.
Enforcement [partial] Auto-reloads exceeding the configured cap are refused. This is not a total organization spend cap. Sources: capy:nov06-admin-billing.
Live progress and spend/token breakdowns are documented; aggregate metrics were not tested.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
13 atomic answers
Logs [supported] Thread view shows commands, diffs and todo progress. Sources: capy:nov06-quickstart.
Traces [unknown] Traces: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Agent stats [partial] Usage splits by member, model and thread. Sources: capy:nov06-admin-billing.
Project stats [unknown] Project stats: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Failure status [supported] Errors influence aggregate thread status. Sources: capy:nov06-threads.
Approval status [partial] Needs you covers answers, decisions, approvals and credits. Sources: capy:nov06-threads.
Reconnect consistency [unknown] Reconnect consistency: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Performance method [unknown] Performance method: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Responsiveness [unknown] Responsiveness: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Session cost [supported] A thread is the session unit and shows machine, model and image spend. Sources: capy:nov06-faq.
Child cost [unknown] Child cost: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Epic cost [unknown] Epic cost: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Harness aggregation [unknown] Harness aggregation: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Billed vs estimated [unknown] Billed vs estimated: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Subscription allowance [partial] Usage splits Capy credits from subscriptions and keys; subscription meters refresh in Settings. Sources: capy:nov06-admin-billing, capy:nov06-faq.
Provider reconciliation [unknown] Provider reconciliation: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Refresh delay [unknown] Refresh delay: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Alerts [unknown] Alerts: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Export [supported] The API exports usage by hour or day per member, billing item or thread. Sources: capy:nov06-api-reference-overview.
Drilldown [partial] Thread cost breaks down machine, model and image spend. Sources: capy:nov06-faq.
Plan-specific cloud machine and concurrent-RAM limits are documented; compute-aware arbitration and verification reuse remain unverified.
Scope
Surfaces: Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-07
Only published capacity configuration was checked; no runtime scheduling or test-reuse scenario was run.
12 atomic answers
Concurrency [partial] Awake-machine memory caps at 128 GB, 512 GB and 1 TB by plan. Sources: capy:nov06-machines.
Queues [partial] A new machine waits up to one minute for room, then fails. Sources: capy:nov06-machines.
Cpu ram [supported] Plan gates sizes up to 4, 8 or 16 vCPU; memory is a hard limit. Sources: capy:nov06-machines.
Backpressure [partial] Same one-minute wait, then Cloud machine couldn’t start. Sources: capy:nov06-machines.
Host awareness [partial] Docs explicitly warn that side chats on the same machine compete for heavy-command resources; adaptive host scheduling is not established. Sources: capy:gap07-async.
Check reuse [unknown] Check reuse: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Check deduplication [partial] Re-reviews are incremental and do not flag the same issue twice. Sources: capy:nov06-review.
Bounded tests [unknown] Bounded tests: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Cancellation [partial] Stop run cancels the timers and background commands the thread is waiting on; its subagents keep running. Sources: capy:gap07-async.
Fairness [unknown] Fairness: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Recovery [unknown] Recovery: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Shared limits [supported] Limits apply to the organization; service-user threads default to half. Sources: capy:nov06-machines.
Work is shared in an organization by default, and anyone with access can write in a thread; live ordering was not tested.
Scope
Surfaces: Capy browser and hosted agent service, Slack, Linear and public API · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
11 atomic answers
Visibility [supported] New work is visible to the organization unless made private. Sources: capy:nov06-admin-security.
Discussion [supported] Several teammates can reply in a synced Slack thread. Sources: capy:nov06-integrations-slack.
Comments [partial] Issue comments and thread replies to teammates exist. Sources: capy:nov06-cl070.
Presence [unknown] Presence: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Coprompting [partial] Anyone who can see a thread can write in it. Ordering was not tested. Sources: capy:nov06-admin-security.
Ordering [unknown] Ordering: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Conflicts [unknown] Conflicts: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Attribution [partial] Linked Slack identities attribute messages to their Capy users; unlinked teammate replies can still reach the agent. Sources: capy:nov06-integrations-slack.
Permissions [supported] Shared or private access per project, thread, Captain and folder. Sources: capy:nov06-admin-security.
Plan restrictions [supported] Every plan includes unlimited members with no member fee. Sources: capy:nov06-admin-members.
Owner online [partial] A thread on someone’s computer holds a message until its owner allows it. Sources: capy:nov06-async.
Org roles, membership changes and private thread/project sharing are documented; enforcement was not tested.
Scope
Surfaces: Capy browser and hosted agent service, Slack, Linear and public API · Version: Capy 0.8.0 (changelog, download, pricing and docs retrieved 2026-11-12) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-12
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
9 atomic answers
Organization roles [supported] Owner/admin/member roles separate billing, administration and thread work. Sources: capy:nov06-admin-members.
Project roles [partial] Private projects have an owner and added people. Sources: capy:nov06-admin-security.
Membership [supported] Invitations, role changes and member removal are documented. Sources: capy:nov06-admin-members.
Sso [partial] 0.8.0 adds Identity and access: DNS-verified domains, Google Workspace sign-in as a paid add-on, other SAML or OIDC providers by contact, and required MFA with passkeys or an authenticator app. Pricing still lists SSO / SAML only for Enterprise. Not tested. Sources: capy:nov12-cl080, capy:nov12-pricing-page.
Provisioning [partial] Email invitations add members; admins can permit verified email-domain joining. SCIM provisioning was not established. Sources: capy:gap07-members.
Unauthorized access [unknown] Unauthorized access: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Plan scope [partial] Roles appear on every plan. Pricing lists the audit log on every plan and SSO / SAML only under Enterprise; the 0.8.0 note sells Google Workspace sign-in as an add-on. Sources: capy:nov12-pricing-page, capy:nov12-cl080, capy:nov06-admin-members.
Device access has approve, deny and always-allow controls; the merge rule is an instruction, and cloud commands have no per-command approval found.
Scope
Surfaces: Capy browser and hosted agent service, Capy desktop 0.7.2, Paired local computer execution, Dock CLI headless device, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-07) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud, paired local execution · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-06 (16 days old)
Agent cross-check
Not separately cross-checked
Some atomic questions remain unknown.
14 atomic answers
Command [partial] Personal devices ask before a thread from elsewhere runs a command there. No per-command approval was found for cloud machines. Sources: capy:nov06-admin-security, capy:nov06-faq.
Network [partial] The optional Tailscale integration limits private-service reachability through the user tailnet ACLs. General internet egress approval was not established. Sources: capy:gap07-tailscale.
Secret [partial] Environment variable requests surface as Needs you; values are not shown to the agent. Sources: capy:nov06-threads, capy:nov06-secrets.
Delivery [partial] Capy’s instructions forbid merge or auto-merge unless asked in the conversation. Sources: capy:nov06-admin-security.
Approver identity [partial] Device owner approves on a personal device. Sources: capy:nov06-admin-security.
Lifetime [partial] Per-machine Tailscale auth keys expire after five minutes and are not saved in snapshots. This is not a general tool-approval lifetime. Sources: capy:gap07-tailscale.
Tunnels [partial] Optional Tailscale gives enabled cloud projects private network access without public exposure. It is not a user-facing remote-client tunnel. Sources: capy:gap07-tailscale.
Defaults [partial] Devices start Personal; new work starts shared. Sources: capy:nov06-admin-security.
Safer modes [partial] Personal device access and private work narrow reach. Sources: capy:nov06-admin-security.
Enforcement [partial] The merge rule is an instruction Capy follows; GitHub access still applies. Sources: capy:nov06-admin-security.
Threads retain conversation/activity and Drive retains attributed file versions; immutable audit guarantees are unverified.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
11 atomic answers
Actions [partial] Commands and diffs are visible during work. Sources: capy:nov06-quickstart.
Approvals [unknown] Approvals: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Edits [supported] Drive history lists saved versions and originating threads. Sources: capy:nov06-drive.
Discussion [supported] Server-stored threads retain the full conversation. Sources: capy:nov06-threads.
Decisions [unknown] Decisions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Cross user persistence [partial] Shared threads stay in the organization after a member leaves; admins can transfer private work. Sources: capy:nov06-faq, capy:nov06-admin-security.
Cross session persistence [supported] Conversation history and thread state are stored encrypted on Capy backend. Sources: capy:nov06-admin-security.
Export [partial] No export button; list threads and messages through the API. Sources: capy:nov06-faq.
Retention [supported] Threads, files and settings stay until deleted; on request, permanent deletion within 30 days. Sources: capy:nov06-admin-security.
Integrity [unknown] Integrity: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Comments [supported] Human PR comments wake the owning thread; 0.8.0 adds notes pinned on images and video frames, sent to Capy as one message. Sources: capy:nov12-cl080, capy:nov06-pull-requests.
Request changes [supported] Comment on the PR to request revisions; the thread responds. Sources: capy:nov06-quickstart.
Shipping guidance [supported] Quickstart describes human review followed by merge. Sources: capy:nov06-quickstart.
Effort [unknown] Effort: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Missed evidence [unknown] Missed evidence: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Narrow screen [partial] Phones can review pull requests in the browser. Sources: capy:nov06-faq.
Context switching [unknown] Context switching: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Roles [unknown] Roles: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Retained context [partial] Findings persist in Capy and GitHub. Sources: capy:nov06-review.
Ownership transfer exists and shared threads are open to teammates; runtime takeover was not tested.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
12 atomic answers
Ongoing takeover [partial] Transfer ownership changes the owner; anyone with access can already write in the thread. Sources: capy:nov06-faq, capy:nov06-admin-security.
Same task [supported] The same thread continues. Sources: capy:nov06-faq.
Session history [partial] Thread history is retained independently of client closure. Takeover parity was not tested. Sources: capy:nov06-threads.
Decisions [unknown] Decisions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Artifacts [unknown] Artifacts: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Permissions [supported] Specific-person sharing and ask-for-access flow are documented. Sources: capy:nov06-release.
Runtime context [partial] A Captain or thread keeps acting with its owner’s GitHub access and connections. Sources: capy:nov06-captains, capy:nov06-faq.
Owner disconnect [partial] Cloud threads run without the owner; device threads depend on the device. Sources: capy:nov06-async, capy:nov06-desktop.
Ownership [supported] Transfer ownership hands a thread to another person. Sources: capy:nov06-faq.
Context loss [unknown] Context loss: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Harness transfer [unknown] Harness transfer: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Screenshots [partial] Crew threads leave screenshots in renders/ on the Captain Drive. Sources: capy:nov06-captains.
Recordings [unknown] Recordings: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Test outputs [unknown] Test outputs: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Reviewer outputs [supported] PR review findings persist in Capy and GitHub. Sources: capy:nov06-review.
Gallery [unknown] Gallery: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Task links [unknown] Task links: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Revision links [unknown] Revision links: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Persistence [partial] Pushed code and Drive files survive replacement; unsaved checkout files do not. Sources: capy:nov06-machines, capy:nov06-drive.
Child findings [supported] Completed children return summaries to the parent. Sources: capy:nov06-subagents.
Prompt leakage [unknown] Prompt leakage: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
CI failures trigger repair and dedicated reviews triage findings; spec gates and enforced branch policy are unverified.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-07
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
11 atomic answers
Tests [partial] Named test commands such as pnpm test run on demand by a person or agent. They do not run automatically. Sources: capy:gap07-environment.
Lint [partial] A named pnpm lint command can be configured and run on demand. No automatic lint gate was established. Sources: capy:gap07-environment.
Types [partial] The command system explicitly includes typecheck actions, run on demand rather than automatically. Sources: capy:gap07-environment.
Ci [supported] Failing checks wake the thread to fix and re-push. Sources: capy:nov06-pull-requests.
Independent review [supported] A dedicated reviewer checks a real checkout at the PR exact head. Sources: capy:nov06-review.
Spec checks [unknown] Spec checks: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Required checks [partial] GitHub branch protection owns branch rules; the Merge menu shows when GitHub does not allow a merge yet. Required-check enforcement was not tested. Sources: capy:nov06-pull-requests.
Failure blocking [partial] The Merge menu shows Waiting on checks; Force merge needs a GitHub bypass permission. Sources: capy:nov06-pull-requests.
Requirement conflicts [unknown] Requirement conflicts: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Configured policy [supported] Repository review mode and finding thresholds are configurable. Sources: capy:nov06-review.
The documented merge rule requires a specific explicit ask; technical authority enforcement is unverified.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
6 atomic answers
Approve [unknown] Approve: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Merge [supported] Capy merges only when asked for that merge; the page offers three methods, auto-merge and force merge. Sources: capy:nov06-pull-requests, capy:nov06-faq.
Release [unknown] Release: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Deploy [unknown] Deploy: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Exact revision [partial] Review runs pin to an exact PR head; revision-specific merge approval was not established. Sources: capy:nov06-review.
Authority enforcement [partial] Merges post as the connected GitHub account; Force merge needs bypass rights on GitHub. Sources: capy:nov06-pull-requests.
PR links and merge events connect results to durable threads; rollback mechanics are unverified.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
9 atomic answers
Commit links [unknown] Commit links: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Pr links [supported] The thread reports its opened PR link. Sources: capy:nov06-quickstart.
Build links [unknown] Build links: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Deployment links [partial] Vercel preview deployments appear on pull request pages. Production deployment links were not established. Sources: capy:nov06-vercel.
Delivery status [supported] Merge wakes the thread within the thread-age window. Sources: capy:nov06-pull-requests.
Retained evidence [supported] Threads retain PR and child history. Sources: capy:nov06-threads.
Rollback [unknown] Rollback: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Revert [unknown] Revert: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Stale approval invalidation [unknown] Stale approval invalidation: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Summaries [partial] Pull requests get a guide; 0.8.0 groups each file into one chapter and has guides for Capy’s own pull requests ready before you look. Sources: capy:nov12-cl080.
Grouping [unknown] Grouping: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Risk size filters [unknown] Risk size filters: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Artifacts [unknown] Artifacts: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Request changes [partial] Comment on the PR, or message the owning thread. Sources: capy:nov06-pull-requests.
Exact revision approval [partial] Review runs at the PR’s exact head. Approval itself stays on GitHub. Sources: capy:nov06-review.
Dependency queues [partial] Stacks merge bottom-up, and a native stack merges below layers in one step; 0.8.0 stack badges also cover Graphite, spr and hand-made chains. Sources: capy:nov12-cl080, capy:nov06-pull-requests.
Next actions [partial] A Captain digest lists what needs you. Sources: capy:nov06-captains.
Stale approval invalidation [unknown] Stale approval invalidation: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Check deduplication [partial] Re-reviews are incremental. Sources: capy:nov06-review.
The Capy application and hosted service use vendor-authored terms. Capy and its licensors retain rights in the software, interfaces and platform, and restrict modification, distribution and reverse engineering without permission.
Scope
Surfaces: Capy browser and hosted agent service, Capy desktop 0.7.2, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-13 (9 days old)
Agent cross-check
Not separately cross-checked
Only the named documented or inspected parts are established; other atomic questions retain their recorded gaps.
6 atomic answers
Client license [supported] The terms cover desktop pairing and the Capy software, with vendor-reserved intellectual property rights. Sources: capy:gap-license.
Server license [supported] The hosted platform is covered by the same vendor terms and retained rights. Sources: capy:gap-license.
Hosted extensions [unknown] Hosted extensions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Source visibility [unknown] Source visibility: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Source revision [unknown] Source revision: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Hosted parity [unknown] Hosted parity: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Export [partial] No export button; use the API. Sources: capy:nov06-faq.
Import [supported] Desktop can import selected Codex/Claude Code sessions into chosen projects. Sources: capy:nov06-download.
Formats [unknown] Formats: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Cancellation [supported] Self-serve plans can stop renewal while retaining access through the paid cycle. Sources: capy:nov06-admin-billing.
Account independence [unsupported] Threads on a device still need sign-in and Capy cloud storage. Sources: capy:nov06-desktop, capy:nov06-faq.
History portability [unknown] History portability: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Capy documents storage, retention, deletion, subprocessors and telemetry, and provider terms apply on your own keys.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
15 atomic answers
Code data [partial] Device files stay on disk, but anything read or printed joins the transcript; cloud machines hold checkouts. Sources: capy:nov06-admin-security.
Prompts [supported] Messages and tool calls are stored in Capy cloud. Sources: capy:nov06-admin-security.
Credentials [supported] Cloud machines hold no GitHub token; variables are encrypted at rest. Sources: capy:nov06-admin-security.
Logs [partial] Desktop crash dumps and logs stay local unless exported. Sources: capy:nov06-admin-security.
Artifacts [partial] Drive files stay until deleted; machine scratch files go with the machine. Sources: capy:nov06-admin-security.
Retention [supported] Stored until deleted; sleeping machines are deleted after 30 days; zero retention by Enterprise agreement. Sources: capy:nov06-admin-security.
Deletion [supported] Delete controls exist; deleted data can be restored, with permanent deletion within 30 days on request. Sources: capy:nov06-admin-security.
Training [partial] Capy states no training on non-public content unless opted in or agreed; provider processing follows provider terms. Sources: capy:nov06-security-page.
Subprocessors [supported] A public Subprocessors page exists. Sources: capy:nov06-subproc.
Telemetry disclosure [supported] Product analytics and desktop telemetry are described. Sources: capy:nov06-admin-security.
Telemetry defaults [partial] Apps send errors, performance data and update checks; no third-party analytics or session recording. Sources: capy:nov06-admin-security.
Telemetry controls [unknown] Telemetry controls: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Consent prompt [unknown] Consent prompt: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Provider separation [supported] On your own key, your provider agreement applies; some background requests stay on Capy accounts under zero retention. Sources: capy:nov06-admin-security.
Interval [supported] Lite $20, Pro $100, Max $200 to $1,000 monthly; annual plans bill upfront at 20% less. Sources: capy:nov06-models-and-pricing.
Seats [supported] Every plan has unlimited members and no per-seat price. Sources: capy:nov06-admin-members.
Seat minimum [unknown] Seat minimum: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Workspace fees [supported] No charge for members or Team workspaces. Sources: capy:nov06-admin-billing.
Included usage [supported] Lite $20, Pro $105, Max 110% of monthly price in credits. Sources: capy:nov06-models-and-pricing.
Credits [supported] One org balance pays hosted models and cloud machine time. Sources: capy:nov06-models-and-pricing.
Trial [supported] Monthly Lite introductory seven days cost $1 with a verified card, then $20 monthly. Sources: capy:nov06-pricing-page.
Overages [supported] Add credits manually or through bounded auto-reload when usage exceeds the grant. Sources: capy:nov06-admin-billing.
Taxes [unknown] Taxes: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Model cost [supported] Models have token rates on Capy credits; connected subscriptions/keys do not draw model charges from Capy balance. Sources: capy:nov06-models-and-pricing.
Compute cost [supported] Cloud VM rates range from Small $0.10/hour through on-request Big Guy $3.20/hour; sleeping VMs cost nothing. Sources: capy:nov06-machines.
Only the fixed and variable rate parts of a scenario can be priced from public sources.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy pricing and docs retrieved 2026-11-07 · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-06 (16 days old)
Agent cross-check
Not separately cross-checked
Some atomic questions remain unknown.
11 atomic answers
One person [unknown] One person: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Two people [unknown] Two people: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Five people [unknown] Five people: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Task assumptions [unknown] Task assumptions: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Concurrency [unknown] Concurrency: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Tokens [unknown] Tokens: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Compute hours [unknown] Compute hours: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Included cost [unknown] Included cost: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Unknown cost [partial] Subscription and API costs sit with the provider. Sources: capy:nov06-faq.
Response commitments [unknown] Response commitments: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Release activity [supported] Releases 0.8.0 on Nov 10, 0.7.2 on Nov 1, 0.7.0 on Oct 31, 0.6.0 on Oct 27 and 0.5.0 on Oct 22, 2026. Sources: capy:nov12-cl080, capy:nov06-changelog.
Status history [unknown] Status history: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Capy publicly states SOC 2 Type II and provides a Trust Center; the report scope and period were not inspected.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
9 atomic answers
Iso scope [unknown] Iso scope: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Iso issuer [unknown] Iso issuer: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Iso validity [unknown] Iso validity: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Soc2 scope [unknown] Soc2 scope: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Soc2 period [unknown] Soc2 period: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Local threads on your own subscriptions or keys need no plan; cloud threads need a plan or balance.
Scope
Surfaces: Capy desktop 0.7.2, Paired local computer execution, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud, paired local execution · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
10 atomic answers
Ongoing free [partial] Threads on your own computer with a connected subscription or key need no plan or balance; provider cost remains. Sources: capy:nov06-faq.
Trial [supported] Monthly Lite has a $1 seven-day introductory period. Sources: capy:nov06-pricing-page.
Credits trial [unknown] Credits trial: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Self host cost [unknown] Self host cost: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Early access [unknown] Early access: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Free scenarios [partial] Local threads on BYO subscriptions and keys work on the free plan; cloud threads need a plan or balance. Sources: capy:nov06-faq.
Card required [partial] The Lite paid introduction requires a verified card. This does not cover every local/subscription route. Sources: capy:nov06-pricing-page.
Usage caps [partial] Free has 1 GB of Drive storage. Sources: capy:nov06-drive.
Paid evaluation [supported] The paid Lite introduction renews at $20/month unless cancelled. Sources: capy:nov06-models-and-pricing.
Public plan, model and hourly machine rates exist, with cancel/top-up controls and custom enterprise terms.
Scope
Surfaces: Capy browser and hosted agent service, Capy managed execution machines · Version: Capy 0.7.2 (docs and site retrieved 2026-11-06) · Plan: Not specified · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Capy agent
Availability
generally-available
Delivery
native
Checked
2026-11-06 (16 days old)
Agent cross-check
2026-11-06
Remaining atomic behavior is unverified; this is a documentation pass, not a hands-on test.
9 atomic answers
Units [supported] Plans grant dollar credits, models bill tokens and cloud machines bill awake time. Sources: capy:nov06-models-and-pricing.
Included limits [supported] Public pricing lists plan-specific concurrent RAM and machine-size limits. Sources: capy:nov06-pricing-page.
Overages [supported] Manual minimum $5 credit purchases or capped auto-reload are documented. Sources: capy:nov06-admin-billing.
Compute markup [unknown] Compute markup: Official docs, downloads, pricing and changelog checked on 2026-11-06 did not establish this. No installed-client or authenticated scenario was run.
Offers 0.8.0 for macOS Apple Silicon and Intel, Windows x64 and Linux x64/arm64. The subscription FAQ names ChatGPT (Codex), Copilot and SuperGrok; it no longer says a Claude subscription cannot be connected and does not mention Claude subscriptions.
0.8.0 adds split panes; an Identity and access page with DNS-verified domains, Google Workspace sign-in as a paid add-on and other SAML or OIDC providers by contact; required MFA with passkeys, authenticator apps or backup codes; pinned comments on images and video frames sent together; PR guides ready in advance for Capy PRs; stack badges for Graphite, spr or hand-made chains; an Issues Display menu; voice input in every composer; Claude Fable 5.2, Morph and Ramp Router; Claude-subscription threads stay on one account. It says a cloud workspace asleep for more than 14 days is cleared; the thread stays and restarts from Setup.
Lite $20/month ($16 annual) with $20 credits and a $1 first week on monthly Lite; Pro $100 ($80 annual) with $105 credits; Max $200–$1,000 at 110% credits; Enterprise custom. SSO / SAML is listed only for Enterprise; Google Workspace sign-in is not mentioned. FAQ names ChatGPT (Codex), GitHub Copilot and SuperGrok subscriptions.
A Claude Pro or Max plan connects through Claude Code with a claude setup-token token; Codex, GitHub Copilot and SuperGrok subscriptions run their plans’ models; own keys, gateways and subscriptions work on every plan, the free plan included.
Captains and Issues GA on 31 October 2026; issues hold blockers, relations, labels, due dates and sub-issues; threads file, update and close issues; Issues are in the public API.
Kind
vendor-claimed
Locator
Captains and Issues are GA; Dock CLI; Issues improvements
Users can request a repository spec before changes. Stop run cancels waiting timers and background commands but leaves subagents running; shared-machine side chats compete for resources.
A machine sleeps about 2 minutes after the thread stops working. A machine that sleeps for 14 days is deleted; if Capy can't resume a machine, the thread gets a fresh one from the dev environment and unpushed work is lost.
Cloud machines join a tailnet as ephemeral tagged nodes. User ACLs control private service access; machine auth keys expire after five minutes and are absent from snapshots.
The vendor terms cover the Capy platform, desktop device pairing and agents. Capy and licensors retain rights in the service software and restrict modification, redistribution and reverse engineering without permission.
Vendor states SOC 2 Type II with report in Trust Center; provider terms govern provider processing; enterprise SSO and audit/export options by agreement.