Who is this for first? +
Small agencies, studios, freelancers, and founder-led teams that maintain several client codebases and still receive important work through email or GitHub comments.
Is this autonomous? +
As far as you set it, per project. Launching work always takes a person: you in the dashboard, or a trusted approver commenting /approve on the GitHub issue. After that, Supervised waits for your Approve & Commit once the independent verifier passes, and Automatic commits and opens the pull request for you. Merging and sending the client reply are always yours.
What does the verifier check? +
After a run reports PASS, a second session with no access to the first one’s reasoning gets the contract, the diff, and the changed files. It re-runs the tests and browser checks itself and returns VERIFIED or REJECTED with feedback. Approve & Commit needs VERIFIED or a typed override, and overrides stay visible on the issue and in the pull request.
What happens when the verifier rejects a fix? +
On a Supervised project the feedback sits on the issue and one click resumes the run with it. On an Automatic project Keanu resumes once on its own (you choose 0 to 3 resumes), then stops and marks the issue Needs you.
What if the feature already exists, or the bug does not reproduce? +
Keanu checks before you approve. A read-only session searches the code for the capability, reads the client’s screenshots, and, when your dev server is up, opens the page and follows the client’s steps. The issue shows the finding with its evidence: the file and route where the feature lives, or what happened on each step. For a feature that exists or a question, a reply is drafted for you to send. Approve stays available either way; the decision is yours, the reading is not.
Can I check what Keanu does before I install it? +
Yes. The Verify it yourself page lists every claim on this site, says whether code or a prompt enforces it, and names the file on your Mac to read or the string to grep for. It also shows how to try the install in a throwaway macOS VM first.
Where does the code run? +
On your Mac, against your own repos, dev servers, and GitHub account, on the agent plan you already have. Prompts and diffs go only to the agent you choose: Anthropic for Claude Code, OpenAI for Codex. No Keanu server sees your code.
What is Founding Developer? +
It is a paid self-service subscription for experienced developers who want local install docs, the starter Wayfinder flow, and setup guidance without a concierge rollout. The founding price is locked while the subscription remains active.
What do I get with self-service? +
You get access to the licensed Keanu runtime, the starter Wayfinder flow, setup documentation, GitHub/model provider configuration guidance, and product updates included with your active subscription.
Why is this priced above AI coding assistants? +
Keanu is not another editor assistant. It works alongside Cursor, Copilot, Claude Code, Codex, and GitHub to manage the client-issue-to-verified-PR workflow around those tools.
Which models does it use? +
Your choice at install: Claude Code, Codex, or both, each on your own plan. With both, a run that hits a usage limit on one continues on the other; the fallback setting on a project can keep it on one agent.
Which plan should I choose? +
Choose by how many client projects you run through Keanu: Founding Developer covers 1, Developer Pro 5, and Agency 20. Every plan is self-serve. If you want Keanu configured with you around a real client project, approval rules, and verification, book a 90-minute paid setup session.
What happens after I subscribe? +
You receive the next steps for local setup, including access instructions, setup documentation, and the starter Wayfinder flow for your first active project.