Describe the change. Towercab ships it as pull requests you can follow.
Towercab is an orchestrator for Claude Code that runs on your own machine. You describe a change as an intent, a short Markdown file; Towercab turns it into a spec, a plan and the code, as pull requests you follow on GitHub.

How it works
Spec PR in the target repo: the requirements the change adds or alters, in plain sentences.
Plan PR in your intents repo: the approach and why, the steps, the risks, and a checklist of the access the worker expects to need (network domains, protected files). Untick what you refuse.
Code PR in the target repo: written test-first, checked locally and in CI, reviewed by a separate Claude session, with a description that says what it does, why, and what to check.
Ship, for a repo with a
liveblock in itsTOWERCAB.md: Towercab waits until your platform says the merge commit is live, then runs the repo's end-to-end suites against the live URL. Every change has to bring e2e tests for what it adds. When a suite fails twice, Towercab asks the platform for the last good version, runs the smoke suites against it, and has the worker fix the cause in a new PR that ships the same way. Two failed fixes and it reverts the change and hands the intent back to you. Your platform does the deploys; Towercab only asks it to deploy the last good version or a revert, as the deploy contract describes. Without aliveblock, merged means done.


Safety
Towercab's work arrives as pull requests, and code decides whether they may merge: at a1–a3 you merge every change yourself, and at a4–a5 Towercab merges only what passes every check and its risk rules allow. Each run is sandboxed and can't touch your keys, other repos or protected files.
Status
Early, and built for one person: it runs on one machine, for one owner, and is used daily by its
author. Version 1 (Rust) is on branch rust.
Cost: Towercab itself is free; the Claude Code runs it starts use your own Claude subscription or API key, and the web page shows what each intent cost.
Requirements
- Linux with systemd (
towercab upinstalls a user service) - Node.js 22.18 or newer
bwrap(bubblewrap), the sandbox for checks and Claude Code runsgit, andgh2.46 or newer, logged in as you- the Claude Code CLI (
claude), logged in - a GitHub App for Towercab, made from ops/github-app.json
Quickstart
Clone and install:
git clone https://github.com/MajidBabaeifar/towercab.git && cd towercab && npm ci && npm run build:uiRegister the GitHub App from
ops/github-app.json, install it on your intents repo and every repo Towercab should work in, and save its private key as~/.config/towercab/app.pem(mode 600).Copy config.example.toml to
~/.config/towercab/config.tomland replace its placeholders (it lists every setting with a comment). The smallest working file is:[intents] remote = "https://github.com/<you>/intents.git" [github] app_id = 123456 me = "<your login>"Check the setup with
bin/towercab doctor, add a repo withbin/towercab repo add <you>/web(it checks the App can reach it, takes its default branch and clones it), then start the service withbin/towercab upand open the page withbin/towercab ui. More repos can be added later from the page or withrepo add, without a restart.Add an intent with the page's "New intent" form, with
bin/towercab add "web: Log in with a magic link" u3 i4(at a terminal both first check for intents that overlap yours), or with the/intentClaude Code skill (./install.shlinks it).Optional, for plans that need a secret in a SOPS file (specs/ship.md, SHIP-33..36): install
sops(a version withset --value-stdin) and make the age key readable by the Towercab service only (SOPS_AGE_KEY_FILEin its environment). Towercab never passes it to a worker.
A hosted version is planned.