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.
Here is what happens, step by step.
- 01step
Codus leases the port
Every folder gets its own slot in a local port registry. When you boot a project, codus stamps the requested port and watches what your dev server actually picks.
- 02step
Collision detected
If the dev server drifts because something else holds the port, codus reclaims the registry entry and updates the preview URL. Stale service workers from the previous project are evicted so the old app doesn't keep loading.
- 03step
Valet and Herd auto-rewrite
For Laravel Valet and Herd users, codus rewrites your local reverse-proxy config so the new port is wired up instantly. Your stable hostname (app.foo.test) keeps working without you touching it.
"Port 3000 is already in use" is one of the most-Googled dev errors.
In a monorepo with 6+ apps, port collisions are constant. Killing processes, rewriting .env files, restarting Valet. Codus eliminates the entire category by owning the port registry and rewriting your local reverse proxy for you.
More of what makes codus different.
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.
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.
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.
Try codus on your codebase.
£99 per seat / month. Unlimited usage. Bring your own Claude Code or Codex account.