Scrapybara, Inc. · Capy: Cloud Coding Agent with Parallel Subagents, PR Review, and 50+ Models
Capy is a cloud coding agent that takes a task from the web app, desktop app, Slack, Linear, or its API, works on an isolated Ubuntu VM with your repositories cloned, and opens a pull request that it keeps fixing when CI fails or reviewers comment. It suits engineering teams that want background agents across many models on one shared credit balance, with no per-seat fees.
Best for
Engineering teams on GitHub that want to hand backlog tickets, migrations, and recurring maintenance to cloud agents across many models, with one shared credit balance, unlimited members, and pull requests that follow up on CI and review on their own
Not ideal for
Teams on GitLab or Bitbucket, organizations that must keep execution inside their own cloud without an Enterprise contract, and anyone who needs a predictable flat monthly cost
Who it's for
Engineering teams and technical founders on GitHub who want to delegate coding, review, and maintenance work to cloud agents and choose models per task
Capy is for teams that want background coding agents but also want to choose and mix models themselves. Pricing is credits with no per-seat fees, and you can run models on subscriptions you already pay for, so a large team can try it without a seat negotiation. The flip side is that spend follows tokens and machine hours, so set auto-reload limits and watch which models your threads default to. The workflow details are mature: subagents on separate machines, stacked pull requests, a review loop that triages its own findings, and a git proxy that keeps GitHub tokens off the VM. The constraints that rule it out are mostly structural: GitHub only, and running in your own cloud only on an Enterprise contract.
Who should use it
Engineering teams on GitHub that want to hand tickets, migrations, reviews, and scheduled maintenance to cloud agents, especially teams that switch between Claude, GPT, Gemini, and open-weight models or already pay for Claude, ChatGPT, Copilot, or SuperGrok, and teams that want to add many members without per-seat costs.
Who should skip it
Teams whose code lives on GitLab or Bitbucket, organizations that need execution in their own cloud but not an Enterprise contract, and teams that need a fixed monthly cost rather than usage-based credits.
Capy Lite
$20
Billed monthly
Capy Pro
$100
Billed monthly
Capy Max
$200–$1,000
Billed monthly
Enterprise
Custom
Free tier limits: No free cloud plan. The first seven days of monthly Capy Lite cost $1 with a verified card (one intro per card and organization). A desktop-app thread that runs on your own computer with a model your connected subscription serves spends no Capy credits, and Capy can sponsor an allowance for approved open-source projects.
Note: Credits are one dollar balance shared by the organization and cover model tokens at per-model rates and machine time while a VM is awake, plus two minutes as it goes to sleep: $0.10/hour (Small, 1 vCPU) to $1.60/hour (Hyper, 16 vCPU), with Large ($0.40/hour) as the default and a Big Guy size (16 vCPU, 128 GB) at $3.20/hour on request. Unused plan credits do not roll over. Top-ups are 1:1 with a $5 minimum, and auto-reload is available. Model usage on a connected Claude, Codex, Copilot, or SuperGrok subscription or on your own API key does not draw on the balance, but cloud machine time does.
Context window
Up to 1.05M tokens, depending on the model
API pricing
Threads started through the API are billable runs like other threads: model tokens and hourly machine time from the organization's Capy credit balance, unless a connected subscription or key covers the model
Available models
Clearing backlog tickets from Linear
Delegating an issue starts a Capy thread that reports its plan and progress back into Linear, works on a prepared cloud VM, and opens a pull request that keeps responding to CI and review, so small tickets get done without an engineer setting up a local session.
Large migrations split across subagents
Capy can split a migration by directory into subagents on separate machines, each shipping its own pull request, or stack dependent changes so every pull request shows only its own diff.
Automated review on every push
With automatic review on, the review agent posts severity-ranked findings inline on GitHub and enforces conventions written in AGENTS.md, and on pull requests Capy opened, the thread fixes high-severity findings itself.
Capy vs. Devin
Devin is Cognition's autonomous software engineer: it takes work from Slack, Microsoft Teams, Linear, Jira, the web app, or the API and runs it in its own cloud VM. Capy covers the same delegate-to-a-cloud-agent workflow from Slack, Linear, GitHub comments, its apps, or the API. The differences are that Capy lets you pick from more than 50 models per thread or subagent, bills one shared credit balance with unlimited members, and can run models on connected Claude, Codex, Copilot, or SuperGrok subscriptions.
Capy vs. Replicas
Replicas hosts third-party harnesses such as Claude Code, Codex, and Cursor in cloud VMs, on your own credentials, and charges per minute of VM runtime against a monthly plan that includes usage. Capy runs its own agent across many models and charges model tokens and machine hours from one credit balance, with optional subscriptions and keys. Replicas fits teams that want to keep their chosen agent CLIs, and Capy fits teams that want one agent with a wide model choice.
Capy vs. Factory Droid
Factory's Droids run the same agent across a desktop app, CLI, IDE integrations, CI, and Slack, with Missions for planned multi-step work. Capy is centered on cloud threads, each with its own VM and subagents, plus a review agent and event-driven automations. Its desktop app can also run threads locally. Factory fits teams that want the agent inside their editors and terminals, and Capy fits teams that mainly delegate work to cloud machines.
Capy vs. OpenAI Codex
Codex is OpenAI's coding agent across a CLI, IDE extensions, cloud tasks, and ChatGPT, and it runs on OpenAI models. Capy can run GPT models on a connected ChatGPT (Codex) subscription as well, and adds Claude, Gemini, Grok, and open-weight models, subagents on separate machines, Slack and Linear delegation, and automations. Codex fits teams standardized on OpenAI, and Capy fits teams that want to mix providers.
What is Capy?
Capy is a cloud coding agent. You describe a task in a thread, from the web or desktop app, Slack, Linear, or the API. Capy starts an isolated cloud VM with your GitHub repositories, makes and tests the change, opens a pull request, and keeps working on it when CI fails or reviewers comment.
How much does Capy cost?
Capy Lite is $20 a month with $20 of credits, Capy Pro is $100 a month with $105 of credits, and Capy Max runs from $200 to $1,000 a month in $100 steps, with 110% of the price in credits. Annual billing is 20% off, and Enterprise is custom. Credits pay for model tokens and hourly machine time, from $0.10 an hour for the smallest machine to $1.60 an hour for Hyper, the largest a plan can start, or $3.20 for the on-request Big Guy size. Every plan has unlimited members, and the first seven days of Lite cost $1.
Is there a free version of Capy?
There is no free cloud plan. The first seven days of monthly Capy Lite cost $1, then $20 a month. Free paths are narrow: a desktop-app thread that runs on your own computer with a model your connected subscription serves spends no Capy credits, and Capy can sponsor an allowance for approved open-source projects.
Which models does Capy support?
Capy's pricing docs listed 60 models on October 22, 2026, including Claude Opus 5.5 (the default), Claude Sonnet 5.5, Claude Haiku 5.5, GPT-6 Astra, GPT-6 Sol, Gemini 4 Argon, Gemini 3.8 Flash, Grok 4.7, Kimi K3, GLM-5.3, DeepSeek V4 Pro, Qwen3.8 Max, MiniMax M3, and Meta's Muse Spark. You can pick a model per thread and per subagent.
Can I use my ChatGPT or Claude subscription with Capy?
Yes, both. A connected ChatGPT (Codex), GitHub Copilot, or SuperGrok subscription runs the models its plan includes instead of Capy credits. Since Capy 0.5.0 (October 22, 2026) you can also connect a Claude Pro or Max subscription: Claude models then run in Claude Code mode, a harness built on the Claude Agent SDK, with no Capy token fee. Cloud machine time still bills Capy credits, and API keys and gateways need a paid Capy plan.
Does Capy run on my computer or in the cloud?
Both. By default each thread runs on an isolated cloud VM. With the desktop app for macOS, Windows, or Linux installed, a thread can instead work in a folder on your own computer with your git credentials, and a thread can move between a device and the cloud.
Capy vs Devin: what is the difference?
Both take tickets from Slack, Linear, or an API and work in their own cloud VMs to open pull requests. Capy puts the whole organization on one shared credit balance with unlimited members, lets you choose among more than 50 models per thread or subagent, and can run models on connected Claude, Codex, Copilot, or SuperGrok subscriptions. Devin is Cognition's own agent and also works with Microsoft Teams and Jira.

Cognition
Engineering teams with a steady backlog of well-scoped tickets who want to delegate them asynchronously from Slack, Teams, or their issue tracker and review the resulting PRs
PaidReplicas
Engineering teams already using Claude Code, Codex, or Cursor who want those agents running in configured cloud VMs, triggered from Slack, Linear, GitHub, GitLab, or automations, with PRs that follow up on CI failures and reviews
PaidFactory
Engineering organizations that want one model-agnostic agent platform across local coding, CI automation, code review, and long-running missions, with enterprise deployment and governance options
Paid
OpenAI
Developers and teams already paying for ChatGPT Plus, Pro, Business, or Enterprise who want one coding agent across the terminal, IDE, and parallel cloud tasks
FreemiumCapy is built around threads: durable conversations with one agent that keep running on Capy's servers after you close the laptop. Each thread gets its own cloud machine, an Ubuntu 24.04 VM with Docker, Node, Python, and a desktop with Chrome, and the agent can split large work into subagents. Subagents that write code boot their own fresh machines, so parallel changes cannot collide, and they can run side by side or stack one pull request on top of another. When the work is done, Capy pushes to a capy/ branch and opens the pull request. It then wakes up on its own when a CI check fails, when a reviewer comments, or when the pull request merges. A built-in review agent posts findings inline on GitHub, and the thread that owns the pull request sorts them and fixes the serious ones before reporting back. Automations run prompts on a cron schedule or on GitHub, Slack, Linear, and webhook events. What sets Capy apart from other cloud agents is the commercial model. It runs its own agent, not third-party CLIs, across more than 50 models from Anthropic, OpenAI, Google, xAI, Moonshot, Z.ai, DeepSeek, Qwen, MiniMax, Xiaomi, Meta, and others. All usage draws from one dollar balance shared by the whole organization, and plans have unlimited members. You can also connect a ChatGPT (Codex), GitHub Copilot, or SuperGrok subscription, or your own API keys, so those models do not use Capy credits. Since October 2026 a Claude Pro or Max subscription can be connected too, and it runs Claude models in a separate Claude Code mode built on the Claude Agent SDK. Capy relaunched as V2 in August 2026, and its desktop app for macOS, Windows, and Linux, released in September 2026, can also run threads in a local folder on your own computer, and a thread can move between a device and the cloud. Plans run from Capy Lite at $20 a month to Capy Max at up to $1,000, with cloud machines billed hourly from the same credits. The tradeoffs: cloud work always costs credits, even when a subscription covers the model, model and machine costs vary with use, GitHub is the only documented code host, and running Capy in your own cloud requires an Enterprise plan.
Capy 0.5.0 runs Claude models on a connected Claude Pro or Max subscription in a Claude Code mode built on the Claude Agent SDK, with Capy's tools, machines, subagents, and pull requests working the same inside it. Capy also became an OIDC issuer for project machines, so they can get short-lived credentials in Google Cloud, AWS, Azure, and Vault instead of holding long-lived keys. The release adds automations in private threads and per-member accounts on organization MCP servers.
Capy 0.4.6 made threads and projects private to the people you choose, let each thread set when it compacts, allowed more than one subscription per provider, and added Claude Haiku 5.5.
Capy 0.4.4 added a marketplace of plugins whose MCP servers and skills are ready in every thread, a guide on every reviewed pull request, models Capy does not list yet on your own key, and desktop threads with no project.
Capy 0.4.3 renamed a thread's child agents to subagents across the app, CLI, Slack, and docs, and GPT-6 models running on a Codex subscription now use their full 1.05M-token context window instead of 400K. The desktop app also starts faster.
Capy 0.4.0 lets threads run on your own subscriptions, API keys, coding plans, and gateways in a set order before falling back to Capy credits, adds reviewing and merging stacked pull requests inside Capy, and made Claude Opus 5.5 the default model.
Capy 0.2.0 added Windows and Linux builds of the desktop app, which first shipped for macOS on September 7. Threads can run in a folder on your Mac or Windows PC with your own git credentials, and setup can import Claude Code and Codex histories.
Capy relaunched as V2, a cloud coding agent in which each thread gets its own cloud machine with your repositories cloned, opens the pull request, and wakes on CI, review, and merge events. Work can start from the web app, Slack, Linear, or the API.
Are you the founder? Claim this listing →