Agents write faster than you can read.

calmdev runs your Claude Code sessions in parallel and brings you only what needs you. You keep up with your code, and you sign it.

You are on the list. One e-mail the day calmdev opens.

That address does not look complete. Check it and send again.

Too many tries from here. Wait a few minutes, then send again.

That did not go through. Type your address and send again.

The list could not be reached. Try again in a moment.

One e-mail the day calmdev opens, nothing else. How your address is kept

Nothing to watch. One list calls you.

The Flow of calmdev on a sample project, redrawn here and played in a loop.
  1. Three sessions work side by side, each on its own branch.
  2. One commits its work and moves to its next step, on its own.
  3. One is done. It waits under For you for your review.
  4. One wants to push. It stops at the wall, until your click.

What you get back.

Up to date
Back from a break, one line per session says what it did. When Claude Code changes, the update to your project’s rules comes as a short diff.
On the right track
Each task is compared with the decisions your project wrote down. A clash is said in one line.
Able to sign
The Review opens on the riskiest files, and no push leaves without your click.

Less to hold in your head.

Most tools for agents help you run more agents. calmdev looks after the person in the middle: what you have to remember, read and decide.

Six terminals to keep an eye on.
One list.A question, a finished session, a push: each waits in For you, one line and one button.
Back from a break: where was each session?
Since you left.One line per session says what it did while you were away.
A diff too long to read with care.
The risk first.The Review opens on the riskiest files, with a few plain points to understand before you sign.
A decision made last month, forgotten today.
A written memory.Each task is compared with the decisions your project wrote down, and a clash is said in one line.
A new Claude Code release, and habits already old.
Rules that keep up.calmdev proposes the change to your project’s rules as a short diff, a reason per line. Only your click writes it.

Agents can run all night. You cannot sign code you never read, or a push that left without you.

calmdev is built on one question: do you come out of it surer of the work, and able to stand behind it? Automation is only the means.

Open by default. Three walls.

A session reads the web and the package registries, runs your tools and writes where the work needs. Three things never happen without you.

  • No secret is ever read.

    No session opens an env file, a key or the keychain. It is refused, with the path that works.

  • No push leaves without your click.

    A push or a release to production waits in For you, with the exact command. Only you answer it.

  • Nothing is sent in your name.

    A signed-in request, a post to a service: same list, same click.

Nothing is ever pushed on its own, not even on request. You review your plans and you answer for what you ship.

The three walls, as the app shows them: one refusal, two requests.

Your day: three short moments

You ask, you answer, you sign. In between, the sessions work and you do not watch. The bar is one day: the wide part is theirs.

The plan comes back, with its budget.

The questions come once, grouped, each with its recommended answer. Then a plan of sessions in waves, each with its model and its budget. Nothing runs until you launch it.

The plan and its budget, before anything runs.

The Flow shows who does what.

Each session works in its own worktree, on its own branch. They never write over each other, nor over main. The Flow shows who does what, and the tests that prove it.

The Flow: who does what, and the proof of it.

One list, one button each.

A permission, a question, a finished session: everything that waits for a human lands in For you, one line each, with its one button.

For you: one line per thing that waits, each with its one button.

A red suite does not merge.

The Review puts the riskiest files first, with a few plain points to check. A red test suite does not merge: the gate names the tests and offers to run them again.

The Review: the diff, before you sign.

Stay the one who signs.

calmdev opens first to developers who already work with Claude Code, and it is free for a developer working alone. Leave your address: one e-mail the day it opens.

You are on the list. One e-mail the day calmdev opens.

One e-mail the day calmdev opens, nothing else. How your address is kept