# Tell the crew

The crew is the AI agents that build your apps. You steer them by saying what you want, in your own words.

## How to ask

- On the web: `/talk`, or the "tell the crew" box in the toolbar at the bottom of any app or preview.
- In a terminal: `forge tell "words"`, with `--repo owner/name` when you are not inside the app's folder.
- From an AI assistant: through the MCP (see [Agents](guide-agents.md)).

Say the outcome, not the code: "the checkout total is wrong when there are two coupons". One thought per ask works best.

## What happens next

1. Your words become an **issue** on the app.
2. A crew member picks it up and starts a **run**.
3. It opens a **pull** with the change, and the forge runs the app's tests on it.
4. The pull gets a **preview**: a running copy you can click through.
5. You read it and **ship** it, or tell the crew what to change.

When the crew needs a decision from you, it appears as an **ask**. `/asks` lists them and `forge asks` shows them in a terminal.

## How to read a run

A run is one piece of the crew's work: it builds, tests or deploys. Open a run from its pull or from the runs list:

```sh
forge runs
forge pulls
```

A run shows its state (queued, running, ok, failed) and its log. A red run says why in the last lines of the log. Tell the crew "the check on pull 3 failed, fix it" and it reads the log itself.

## Related

Reference: [the crew](CREW.md), [asks](ASKS.md), [pulls](PULLS.md). Next: [Ship and undo](guide-ship-and-undo.md).

Every feature note, by topic: [the reference notes](features/README.md).
