Your first mission

What happens between typing a sentence and getting a result — and where you get a say.

1. You ask

Write it in plain words: “the export dialog forgets the last folder, find out why and fix it”. You do not need to name files. Nemocode searches the project itself and reads what it needs.

If the request could mean two different things, it asks before it starts — one question, with options you can pick with a key.

2. It plans

Plans are written in Plan mode (it can only read). You switch it on yourself: press Shift + Tab until the footer says plan mode on. For a bigger task the agent may ask whether to plan first; only your yes switches it on, and a no means it builds. The plan ends in a question with four answers: approve and build in auto mode, approve and ask before shell commands, keep planning (say what to change), or reject and stop. Esc means keep planning — it never releases a plan. The plan is written down with the project, so later you can see what the approach was.

If you already know what “done” looks like — “all tests pass”, “the build is clean” — say so with /goal and Nemocode keeps going until it is. See Setting a goal.

If you would rather it just builds — for unattended runs, for example — switch on Auto-approve plans under Settings ▸ General. The plan is still written down.

3. It works

You see every step as it happens: which file it reads, what it changes, which command it runs, what came back. Nothing is hidden behind a spinner.

Two things stop for you, unless you said otherwise: a shell command, and a folder outside the project. A shell command is answered with y (once), a (this command from now on) or n. A folder outside the project comes as a question with four answers: allow always, just this mission, no, never (Esc means no). See Permissions & safety and the Keys.

4. You can interrupt

Type while it works — your message is queued and starts as the next mission when this one is done. Use /steer <text> to redirect the running mission at its next step instead (with no mission running, it simply starts one), or press Esc to stop it. See Writing while it works.

5. It checks itself

A second agent can read what changed before a mission may finish and judge whether the job is actually done. If it says no, Nemocode goes back and fixes it. It is what turns “it compiles” into “it works”, but it costs a second model call per mission, so it is off by default: switch on Verify subagent under Settings ▸ General. You can also run the project's own check at any time with /verify.

6. It writes down what it learned

At the end, Nemocode proposes facts worth keeping — a decision you made, a constraint the code has to respect, something a document demands. They do not go into the memory silently: they wait at a gate. Open it with /pending and approve or reject each one.

See Project memory for what belongs in there and what does not.