Skip to content

Run a task and follow up

A task is one ask to one agent, in your project. This guide covers the loop you use every day: start it, follow it, send follow-ups, and stop it when it goes the wrong way.

Start a task

Press New task (N or ⌘L), type what you want and press Enter. Above the box, pick the project. In the footer, pick the mode (Plan, Edits or Full auto), the harness and model, and where it runs (This computer or another machine). The + button adds files, a goal, delegates, a second agent to compare, or a later start.

In the browser (wisp --browser, or your cloud wisp) it’s the same window, menus and keys.

Each task runs in its own git worktree by default, so tasks never step on each other. See Worktrees and shipping a PR.

Watch it

The task page shows what the agent does, step by step, then its answer as cards: a summary, the diff, the tests. The list on the left says which tasks work, which need you and which are done. J and K move to the next and previous task; V opens the full transcript.

A finished task: the agent's report as cards, with a summary, the diff and the testsA finished task: the agent's report as cards, with a summary, the diff and the tests

Follow up

Press / to jump to the reply box under the answer, type, and press Enter. While the agent works, the Queue button decides what a follow-up does: it waits for the turn to end, or it interrupts now. Queued follow-ups show above the box. Drag them to change the order, edit them, Combine with the next one, or Send now.

To ask something without stopping the run, open the task’s ⋯ at its top right → Task options › Side discussion…, or type /btw is this safe?. The answer shows beside the run, and the run carries on.

The task's ⋯ menu open on Task options, with Set goal…, Side discussion… and the other task optionsThe task's ⋯ menu open on Task options, with Set goal…, Side discussion… and the other task options

You can also schedule a follow-up for later: Start later in the + menu, or wisp later add <id> --text "check the deploy" --in 60 (minutes).

Stop it

Press Stop in the reply box while it works, and confirm. Queued follow-ups stay, held until you send one.

A held turn

wisp holds a turn before it starts when something needs your yes: the repo asks to run its own programs (hooks, MCP servers, a worktree setup script), the harness changed since wisp last ran it, or the turn would push a usage window past your line (see Budgets and usage). The task shows Held and says why.

The held card has Trust and start, Run without them (without the repo’s own programs) and Skip this run. A turn held for a usage window offers Start now or Wait.

Carry on yourself

To take the conversation into the harness’s own window, open the task’s ⋯ menu, Open in (in the TUI, o). When you come back, wisp picks the task up where you left it.