tnee.
docs/core concepts/Plans & checklists

plans:
the steps, ticked as they land.

Ask for one thing and tonee just does it. Ask for six, and it says what the six are before it starts. Then it marks each one off as it happens, so you're never watching a spinner wondering which part it's on.

01 /When you get a checklist

A checklist appears when a request has enough moving parts that a single sentence of confirmation wouldn't tell you much. "Turn the kick down 2 dB" doesn't get one. "Set up a sidechain, carve the pads, and match the send levels" does.

✓Read the mix: kick, pads, bass
✓Add Compressor to PAD WRM, sidechain from KICK
◐Carve 250-400 Hz on the pads
○Match send levels across both
Declared once
The list is fixed at the start of the turn. tonee can't quietly add a step halfway through and pretend it was always there.
Its own bubble
The checklist sits above the reply rather than inside it: what was done, kept separate from what was said about it.
One list per turn
Send a new message and the old checklist stays put in the conversation. It's a record, not a live dashboard.
Not a to-do list
You can't tick, reorder or add items. It reflects what tonee is doing; to change the work, tell it.

02 /Reading the marks

○
PENDING
Declared but not started. tonee said it would do this before it began.
◐
DOING
The step in flight right now, the one place your eye should go while a reply is streaming.
✓
DONE
Landed, and struck through. The whole list ends up like this on a turn that went cleanly.
✓
UNCONFIRMED
Ticked, with a quiet note beside it: tonee marked it done, but nothing matching it showed up in your set.
✕
ERROR
The turn stopped before this step finished.
Struck through is good: a finished turn is a list of crossed-off steps. It reads like completion, not cancellation.

03 /Checked against your set

A tick that only meant "the model believes it did this" would be worth very little. That's exactly the claim you'd want to verify. So the ticks aren't taken on trust: as the turn runs, each step is compared against the changes that actually reached your set.

Steps that change something
A step like "add a compressor" has to be matched by a real change in the same area before its tick stands unqualified.
Steps that only look
Reading, checking and listening aren't expected to change anything, so they're ticked without needing a match.
No match, but the turn did work
The step still shows a tick, with "unconfirmed" beside it. The check is additive: it never takes a tick away, it annotates one.
Deliberately forgiving
A related change is enough. An exact match isn't required. The flag is there for the clear case, not to nitpick wording.

For the definitive record of what changed (not what was claimed), the action log in the Live session panel lists every committed write.

04 /When a step goes wrong

A turn doesn't always finish the list. When it doesn't, no step is left spinning: every one ends up in a settled state so the checklist is never ambiguous about where things stopped.

You cancelled a change
Steps past that point never ran. Nothing reached your set. See Permission modes.
You sent a new message
The turn is abandoned where it stood. The half-finished checklist stays in the conversation as the record of how far it got.
Something errored
The failing step is marked, and tonee explains what happened in the reply beneath it.
It says "unconfirmed"
Worth a look at your set. Usually the change landed somewhere the check didn't recognise, but occasionally it means it didn't land at all.
A stopped turn doesn't roll back: steps that already landed stay landed. The checklist tells you which ones those were; say "undo" to reverse them.
← ListeningNext · Tracks & clips →
© 2026 tonee studio
docstermsprivacysecuritycontact
tonee is not affiliated, associated, authorized, endorsed by, or in any way officially connected with Ableton AG. Ableton® and Push® are registered trademarks, and Live™ and Max for Live™ are trademarks, of Ableton AG.