# Braid: Frequently Asked Questions

What Braid is built for, what you get from it, and how to start.

## Why Braid

### What is Braid?

Braid is a decision intelligence layer for AI coding agents. While your agent works, Braid records what it does. When the change is ready, Braid shows the decisions inside it: the question, the approach your agent chose, the ones it set aside, and the code each decision shaped.

### What problem does Braid solve?

Coding agents write code faster than anyone can read it. A diff shows what changed, but not why. The reasons stay in the agent’s session, and they get lost when the change moves to a pull request, to main and later to production. Braid keeps the reasons with the change, as decisions you can read.

### What value do I get from Braid?

You know what you ship. You see what your agent chose, what it set aside and why, without reading the whole diff or the session. You spend your time on the few decisions that no test checks. Your teammates get the same reasons on the pull request. And months later, the reasons are still there when someone asks why the code is the way it is.

### What is Braid built for?

Braid is built for the way software gets made now: you direct coding agents, and they write most of the code. It keeps a person in charge of the choices, even when no person writes or reads every line.

### Who is Braid for?

Developers who direct Claude Code or Codex and want to own what they merge. Teammates who check those changes on pull requests. And engineering teams who need to know, months later, why their code is the way it is.

### Why does Braid focus on decisions, not code?

Because code is cheap now. An agent can write a thousand lines in minutes, but the choices behind them still matter: how to store the data, what to check, what to leave out. A change has many lines but only a few decisions. Decisions are what a person can read and own.

### How do developers use Braid?

Prompt your agent as usual. When the change is ready, ask it to reconstruct the intent. Read the decisions, and open the code behind any of them. If you disagree with one, tell your agent what to change and why. Then reconstruct the intent again.

### How do teams use Braid?

When you open a pull request, Braid comments the intent on it. Your teammates read the decisions first, and then the diff. They see what the agent chose and what it set aside, so nobody has to guess what the agent was thinking.

### How is Braid different from AI code review tools?

Most AI code review tools read the finished diff and comment on it. Braid records the work while your agent does it, so it knows the choices your agent made and the ones it set aside. It shows each choice with the code and the checks behind it.

## Using Braid

### Which coding agents and platforms does Braid work with?

Braid works with Claude Code and Codex, including the subagents they start. It runs on macOS and needs Git 2.25 or later.

### Do I have to change how I work?

No. Keep prompting your agent the way you always do. After you install Braid, it records your agent sessions on its own. When a change is ready, ask your agent to “reconstruct the intent”, or run `braid intent` in a terminal.

### What is a decision?

A decision is a choice your agent made while it worked. Each decision shows the question the agent had to answer, the check that covers it, the approach the agent chose and why, and the other approaches it considered and why it did not take them.

### Who writes the decisions?

Your coding agent writes them, from the work that Braid recorded. Each decision shows which model wrote it. It links to the code and to the steps your agent took, so you can check it yourself.

### Do my agent sessions leave my machine?

Braid records your agent sessions on your machine, and they stay there. When you want your team to read a change, you push its intent, and Braid comments it on the pull request.

### Does Braid replace code review?

No. Braid works next to your pull request. Your reviewers read the decisions first, and then the diff.

### How do I share a change with my team?

Ask your agent to push the branch and open a pull request. Braid’s skills push the intent and comment it on the pull request, and your teammates open the full review from that comment. The Braid GitHub App must be installed on the repository.

### How do I install Braid?

In a terminal, run `curl -fsSL https://braidkit.io/cli/install.sh | bash`. The installer signs you in with GitHub, adds the Braid GitHub App and sets up your coding agent. The [Quickstart](https://docs.braidkit.io/quickstart/) takes you through a first change on a sample app.

### How do I stop or remove Braid?

To stop recording, run `braid hooks uninstall claude` or `braid hooks uninstall codex`. To remove Braid, run `braid uninstall`.

## More

- [Home](https://braidkit.io/index.md)
- [Docs](https://docs.braidkit.io/)
- [Discord](https://discord.gg/gCTB7mC3Hq)
- [Email](mailto:hello@braidkit.io)
