# Start work

**Start work** turns one sentence into work on the board: a card, an import from Linear or Jira, a plan of several
cards, or a study. Type or say what you want done, check what Andon understood, and press Enter.

Open it with the filled **Start work** row at the top of the sidebar, or press `W` anywhere outside a text field. On a
phone it is the middle tab. `/capture` opens it too.

## Make a card

1. Press `W` and type what you want: `Fix login in winnable, urgent`.
2. Check the pills under the text: what Andon understood, such as *New card · winnable · General · Urgent*.
3. Press Enter, or click **Add card**.

The card goes to the bottom of the team's Backlog. To send it straight to Ready instead, where Autopilot can pick it
up, pick **Add card, and ready** from the button's menu. It is off when the board has no Ready column.

If the sentence names no team, the Team pill reads *Pick team*, and nothing is added until you pick one. Opened while
the board is filtered to a team, the box starts in that team instead, in the filtered project or else the team's
General project. The words and your pills still win: name another team, or take the pill off. A name the words leave
ambiguous ("Did you mean") leaves the pill empty for you to settle.

## Change what Andon understood

Each pill is something Andon read from your words: the kind of work, the team, the project, the agent, the model,
the machine, the recipe, the priority, a template. Its icon says which; hover over a pill for the word.

- Change a pill from its menu.
- Take a pill off with **×**, or press Backspace at the start of the box to take off the last one.
- A pill you set or took off stays that way: typing more never puts it back.

When neither the words nor the board's filter say where the work goes, Andon guesses the team and project a moment after you stop typing. The
empty Team pill reads *Finding team…* while it asks, and the guess shows marked **guess**. A guess never replaces a
pill you set. The guess needs a model: a Claude (Anthropic), Gemini or Vercel AI Gateway key, the workspace's or the server's, or a machine that
serves model calls ([AI backends](https://andon-docs.pages.dev/machines/ai-backends.md)).

The words can also pick the card's agent, model, machine, recipe and priority: *with Opus*, *use Codex*, *on the
Studio machine*, *as a bug fix*, *urgent*. Its words come out of the title, and the card is made with that agent or
model, so its run uses it. Take the pill off and its words go back in the title. A model alone brings its agent:
*with Opus* runs Claude Code. Andon only offers the models in **Models offered** on **Settings → Automation**, and
only your own machines.

The agent and model are read straight from the words, as you type and without a model key, when they follow
*using*, *use*, *with* or *via*: *using Codex*, *with Fable 5.2*, *via the Gemini CLI agent*, *using Codex and gpt-6*.
A model's name can be written as its label, its id (*claude-fable-5-2*), or its family alone (*with Opus*: the first
Opus in your list). A name that is part of the work stays in the title: "Add chat with Codex sessions" is a card about
Codex. Other phrasings, and the machine, recipe and priority, come from the guess and show marked **guess**.

## Examples

| You type | Pills | Enter does |
|---|---|---|
| `Fix login in winnable with Opus, urgent` | New card · winnable · General · Claude Code · Opus 5.5 · Urgent | Adds "Fix login", to run with Opus, at Urgent |
| `Fix login in winnable using Codex` | New card · winnable · General · Codex | Adds "Fix login", to run with Codex |
| `Add forgot password to winnable` | New card · winnable · General | Adds "Add forgot password" to the winnable team's General project |
| `Add invoices to the Billing project for winnable` | New card · winnable · Billing *new* | Makes the Billing project, then adds the card to it |
| `Import DRO-454 from Linear` | Import · Linear · DRO-454 | Looks the issue up and shows it to import |
| `Import my issues from Jira` | Import · Jira · Assigned to me | Lists your open Jira issues to pick from |
| `Plan a billing area for winnable` | Plan · winnable · General | Proposes one card or several to refine and accept |
| `Study why the board is slow for winnable` | Study · winnable · General | Adds a Study card and starts its run |

## Import issues

Start a sentence with *import*, *pull in* or *bring in*, or type an issue key such as `DRO-454` with the tracker's
name.

1. Type `Import DRO-454 from Linear`, or `Import my issues from Linear`.
2. Click **Find issues**. Andon shows the issues it found, ticked.
3. Untick what you don't want, and import.

Only open issues are found. An issue already on the board shows as such, with a link to its card. An issue whose card
was archived is listed unticked: tick it to bring the card back. Cards go to the Backlog of the team and project in
the pills.

Start work imports from **Linear** and **Jira**, through the connection the team uses. If the tracker isn't
connected, the box says so before anything runs. For GitHub, use the board's **Import** button. To keep a Linear
backlog flowing in, set up an import rule: see [Integrations](https://andon-docs.pages.dev/guide/integrations.md).

## Plan several cards

Ask for a plan with *plan*, *break it down*, *split it into* or *as an epic*, or write 30 words or more. A pasted brief
is planned too (below).

1. Type the request and press Enter, or click **Plan it**. When an agent plans, the button reads **Plan on a
   machine** and the plan comes back on a card (see [Who plans](#who-plans)).
2. If something would change the plan, Andon asks first, under **What are you building?**. Answer what you can and
   press Enter, or click **Skip, plan it now** to plan on sensible assumptions.
3. Andon proposes one card, or up to 20 steps. Edit a step's title and notes, untick it or remove it, or add your own.
4. To change the plan, type what to change in the box under it ("merge the first two", "add an admin screen") and
   click **Update plan**. Go round as often as you like.
5. Click **Add a workstream of N steps**.
6. Andon asks **Start it now?** **Start it** moves the first step into Working. **Not now** leaves the workstream in
   the Backlog for you to start later.

**Just one card** adds the request as a single card instead. If planning fails, the box says why and offers **Add as
one card**.

The request becomes the workstream's parent card, and the steps its children, each waiting for the one before. Each
step starts by itself when the one before it is done. A step whose run asks for review waits in Review until you
move it to Done. See [Workstreams](https://andon-docs.pages.dev/guide/workstreams.md).

### Who plans

On a plan, the **Planner** pill picks who plans:

- **AI, here in the box**: the plan comes back in the box. It runs on the workspace's AI backend (Claude by default),
  so it needs a Claude (Anthropic), Gemini or Vercel AI Gateway key, or a machine that serves model calls.
- **Agent on a machine**: Andon adds one card with the **Plan a workstream** recipe and starts its run. The agent
  reads the card and the code, may ask you up to two questions on the card, and proposes the steps as **Proposed
  plan** on the card for you to edit and approve. It needs a machine online.

Andon remembers your choice. When none of those can answer, an agent on a machine plans, when one can.

Plans, team guesses and suggested titles are limited, per person and per workspace, so one person can't spend the
workspace's key without end: 20 plans per person and 100 per workspace in 10 minutes, and 60 guesses and 60 titles per
person (300 per workspace). Over the limit, the box says to wait a little and try again.

### Paste a brief

The box takes up to 50,000 characters, so a whole spec or brief can go in. Text of 500 characters or more, or three
or more long lines, is read as a brief: the button reads **Break it down**, and a note under the box gives its size.

Only the brief's first line is read for a team and project, so `# Billing for winnable` files it in the winnable team.
Andon breaks the rest into the cards that build it, in build order, and puts each requirement into the card it
belongs to. A long brief can take a minute; the box counts the seconds.

## Study it first

Some requests are questions before they are work: *is the Settings area finished?*, *why is the board slow?*

1. Type the question.
2. Click **Study it first**, beside the go button. Or start with *study*, and the button reads **Study it**.

Andon adds one card with the **Study** recipe, starts its run and opens the card. The run reads the code, tries the
app, asks you on the card when it needs to, and ends with a proposal in Review. It never pushes or opens a pull
request. A study needs a team, and **Study it first** shows only when the workspace has a **Study** recipe. See
[Studies](https://andon-docs.pages.dev/guide/studies.md) for what comes next.

## Start from a template

When the team has [card templates](https://andon-docs.pages.dev/guide/templates-and-bulk-edit.md), a new card gets a **Template** pill, *No template*
until you pick one. The sentence can pick it too: `bug: login fails`, `[Bug] login fails`, or `… with the Bug
template`. The preview under the box shows the title the template makes.

## Make a new project or team

- **A project**: name one the team doesn't have, such as "to the Billing project" or "in a new project called
  Billing". The Project pill shows it marked **new**, and it is made when you press Enter. Or pick **New project…**
  from the pill.
- **A team**: pick **New team…** from the Team pill. The Add team sheet opens over the box, and the team is made when
  you click **Create team**. You need permission to add teams.

## Add screenshots and files

Paste a screenshot into the box, drop files on it, or pick them with the paperclip. Each can be up to 25 MB. They go
with the new card, on its **Context** tab, where the agent sees them. An import doesn't take files.

## Talk instead of typing

Click the mic in the box and speak: the words appear as you say them. Press Enter when you're done. **Listen as soon
as it opens**, under the box, starts listening each time the box opens.

Dictation uses your browser's own speech recognition, in Chrome, Edge and Safari, in the **Voice call language** under
**More** on **Settings → You**, else the browser's. Andon records nothing; in Chrome and Edge the browser's maker
transcribes the audio.
Firefox shows no mic. In the macOS app, macOS asks for the microphone and speech recognition the first time.

## The tour

The first time someone opens a board with no cards on a device, a short tour shows them round: Start work first,
then the Board, Needs you, the Dashboard, Teams, Progress, Machines and the account menu. ← → or Enter step through
it, and Esc closes it. **Take the tour** in the account menu starts it again.

How the box reads your words, and what it sends to the model, is in
[Start work internals](https://andon-docs.pages.dev/contributing/start-work.md).
