codus
Features

Twelve things no other coding agent does.

Cursor, Windsurf and Claude Code run the agent. Codus runs the workflow around it. Pick any one to see how it works.

Codus Brain

Meet the Brain. The agent that runs your agents.

An orchestrator with persistent memory that delegates to every quadrant across every tab and window. And now it multiplies: run a Brain swarm, several Brains side by side, and they message each other.

codus · brain
inbox0
Brain 1
brain · drawer chat
youShip checkout v2 — web and api.
delegated
brain swarm · every tab, every windoworchestrating
See the Brain at work
Self-healing loop

It ships. It looks. It fixes its own bugs.

The agent that screenshots its own work, spots the broken pixel, and reships until the page actually looks right.

preview · localhost:3001/checkout
verify failed
your cart3 items
Mechanical keyboard× 1
$89.00
USB-C cable, 2m× 2
$12.20
Notebook · Field× 1
$14.00
assert failed · total === 0
total$0.00
verify loop · q1self-healing · 3 attempts max
Watch the heal loop
Visual planner

Draw the architecture. Codus writes the code.

Sketch a diagram. Codus reads the nodes, the edges, and the dependencies, then ships the workflow.

planner · checkout v2 · q2
planning…
project
Checkout v2
feature
Cart UI
feature
Stripe API
feature
Receipts
task
a11y tests
task
Webhook retry
task
MJML template
cloud planner · q27 nodes · drilled 2 levels
Open the planner
Agent behaviour

You set the bar. Codus holds it.

Sliders for testing rigor, security review and response detail — plus a 2D style pad for visual fidelity. Global defaults, per-project overrides, applied live.

settings · agent behaviour
global default
Testing rigor3/10
Security review5/10
Style pad
functionalhigh craft
codus.verify
smoke test · ok
agent behaviour · resolved live, no restartdefaults
See the rigor dials
Mobile companion

Queue a feature. Walk away. Get screenshots.

Assign a task from your phone. Codus runs it on your Mac. Screenshots in three viewports land in your notifications when it's done.

codus mobile · 4G
tasks · 12 today
Cart layout · 5-col grid
queued
Stripe webhook retry
done
README polish
done
a11y · contrast pass
done
desktop · 1440
tablet · 1024
mobile · 390
phone-driven · q13 viewports captured · pushed to phone
See the phone loop
Logs in everywhere

Captchas, 2FA, passkeys. All solved.

Cloudflare Turnstile, hCaptcha, reCAPTCHA. All auto-solved. TOTP codes auto-typed. WebAuthn passkeys auto-stored. Agents log in everywhere, every time.

acme corp · sign in
idle

Sign in to your account

codus filled this for you · vault unlocked

email
 
password
 
2fa code
 
Verifying you are human…
cloudflare turnstile · auto-solved
solving
auth vault · q1captcha · totp · webauthn · all auto
How the vault logs in
Auto-port collision

Run 6 dev servers at once. Forget port 3000.

Per-folder port registry. Auto-rebinds your Valet and Herd setup when ports drift. The "port already in use" error is dead.

port registry · ~/.codus
4 ports leased
web · marketing
:3000running
api · payments
:4040running
docs · site
:5173running
mobile · web
:19006idle
new
admin · dashboard
queued
port registry · daemoncollision-free · valet auto-rebind
See ports auto-heal
Tabs × quadrants

Four agents per tab. As many tabs as you want.

Every tab is a 2x2 grid of independent agent sessions. Stack tabs for every project you have running. Ten tabs is forty parallel agents on one Mac.

codus
4 running
web · marketing
api · payments
infra · pg
q1 · web · cart
fix grid overflow
queued
1
2
3
q2 · api · stripe
idempotency keys
queued
1
2
3
q3 · infra · pg
index on user_id
queued
1
2
3
q4 · docs · readme
v0.2 features
queued
1
2
3
3 tabs open · 12 agents runningsynced to cloud planner
Tour the quadrants
Claude accounts

Every Claude account you own, on one meter.

Run codus across several Claude accounts, see exactly how much of each is left, and move a quadrant or the whole app to another account in one click.

claude accounts · usageresets 17:00
[email protected]everywhere
5h
week
model
[email protected]Q3 only
5h
week
model
[email protected]signed out
5h
week
model
See the usage meter
Picture-in-picture

Browsers that float while you keep typing.

Any quadrant's preview pops out as a chromeless picture-in-picture over your work, one of them or all four at once, each with its own inline address bar.

codus · 4 quadrantspip · all four
Q1 · api
Q2 · web
Q3 · infra
Q4 · docs
localhost:3002/checkout
Float a preview
MCP hot-load

New tools reach running agents in seconds.

Add any MCP server in Settings and its tools go live in every agent, including agents mid-conversation. No restart, no new session.

mcp · hot-loadseconds to live
settings · mcp servers
+ internal-crm · http://10.0.0.4:4010
added
state
Connected · 12 tools
live
Q2 · agent, mid-conversation
crm_lookup_account now available
no restart
See tools hot-load
Agent identity

Your agents have their own email and phone.

A codus mail address and a rentable real mobile number let agents sign up for the services your work needs and catch their own verification codes.

signup · autonomous0 interruptions
mail · [email protected]
Verify your account: code 481 923
caught
sms · +44 7•••
Your one-time code is 302 114
caught
vault
api.data.gov credentials stored
encrypted
See a signup run itself
Unattended

Brief it at midnight,
wake up to four live products.

You give it the idea in a sentence. A research crew works out what that market already has and where the gap is, coding agents write the entire product from the database to the landing page, and the same run then registers the domains, puts it live on Vercel with every setting and password already filled in, points the web address at it and sets up the billing. Every other agent tool stops at the code and leaves the rest to you, which is why so little of it ever reaches the internet, whereas what is waiting for you in the morning here is not a plan or a half-built draft but four finished products already serving real visitors.

One night, nobody watching

Seven hours you were asleep for.

The run below is the whole distance from a sentence to a real web address you can open, with no approval step in the middle waiting on you to come back to your desk.

unattended run · 4 productsrunning
23:40
brief
One line accepted, four products queued
queued
23:58
research
Competitors pulled apart, pricing and gaps mapped
queued
00:12
naming
Availability checked, domains registered at GoDaddy
queued
01:35
build
App, sign-in, billing and landing page written and reviewed
queued
03:02
deploy
Pushed live to Vercel, every setting and password filled in
queued
04:18
dns
Web addresses pointed, security sorted, sites answering
queued
05:50
monetise
Stripe products created, ad units and analytics wired in
queued

It works out what to build

A research crew takes the idea apart before a line is written, reading the products already serving that market, what they charge, what their reviewers complain about and which corner of it nobody has covered, then comes back with the version worth building rather than the one you first described.

It writes the whole product

Not an empty starter: the app itself, the sign-in, the database, the billing, the landing page and the words that sell it, built by the same coding agents and put through the same review as any other codus work before it is allowed to deploy.

It buys the domain

Availability and price are checked across the registrars you have connected, then the name is registered and paid for on your account without waking you up to confirm it.

It deploys to Vercel

The project is created, the site is pushed live, and every setting and password it needs is filled in, so what is waiting in the morning is a working site rather than code somebody still has to put online.

It wires the money in

Stripe products, the payment page and the plumbing that tells your app when someone has paid, for the SaaS builds, ad units and analytics for the content builds, configured as part of the run rather than left as a to-do.

It runs on a schedule

Set it once and the run fires every morning on its own, so the question stops being whether you had time to build this week and becomes which of the four you want to keep.

Connect the accounts it spends and publishes on once in integrations, set the nightly brief, and the only decision left in the morning is which of them is worth keeping.