The terminal you already work in is enough to run a company, if something keeps the plan, the state, the review bar, and the human gates in one place. That something is Casa.
Where Casa lives
Casa is not an app you switch to. It is an operating layer that installs into the harness you already run: Claude Code, Codex, Grok Build, OpenClaw, Hermes, or any shell-capable agent. There is no account, no waitlist, and no hosted runtime. Your model plan does the reasoning; Casa supplies the order.
Install is three steps in every harness: clone the repository, open your project, and run /casa-start. An empty folder starts a founder interview; an existing project gets scanned first. From that point on, the company has an operating record.
- MIT licensed, engine covered by 281 tests, zero runtime dependencies, Node 20 or later.
- 174 playbooks across 11 departments, selected by business fit and readiness.
- Everything Casa produces lives as Markdown and JSONL in your repository.
What a session opens on
Every session starts the same way: Casa reads the company brain, names the binding constraint, and ranks what is ready. You never open a blank chat and re-explain the business. The company is already loaded.
The demo below is InboxPilot, a synthetic demo company we use across the site. One command reads the state, surfaces the constraint that binds next progress, proposes the move it drives, and stops where a founder decision is required.
Order is the product
More capable agents make order load-bearing. When one model can draft the market map, the product spec, and the launch copy in an afternoon, the scarce thing is no longer capability. It is a durable plan, dependencies that hold, work that has a review bar, and consequential actions that wait for a human.
Casa separates rules from judgment. Deterministic code owns eligibility, dependency math, gates, and state transitions. The model reasons inside the eligible set and produces the work. A prompt phrased differently cannot un-block blocked work.
Your harness, your plan, your files. Casa adds the operating system.
Where it goes from here
A Casa company does not end at the terminal. Attested operating work can be registered in the Capx registry, where Terminal reads it and exposes it as a public operating record. When the company is ready for a market, Launchpad gives its agent token a presale that settles itself.
Those layers are optional and separable. Casa alone is a complete operating loop: read, decide, make, review, gate, commit. The rest of the stack exists for the day the company wants a public record and a market.