tnee.
docs/getting started/First conversation

first conversation:
how to talk to it.

tonee isn't a command-line tool with a fixed vocabulary. It reads your set, infers what you mean, and asks when it isn't sure. This page covers how that works in practice.

01 /How tonee reads your set

Before every reply, tonee mirrors your Live session: track names, clip states, device chains, send levels, tempo, and scene names. It doesn't guess; it reads. That's why you can say "the pad track" instead of "track 3", and it knows what you mean.

Nothing is sent to the AI backend except this structured state snapshot and your message. No audio. No MIDI data. No file contents.

What gets mirrored: track names, types, armed state, clip names and colors, device chains in order, send levels, master tempo, and scene names. Automation values are included from v1.4+.

02 /Talking naturally

You don't need to learn a command syntax. Describe what you're trying to achieve. Production language works fine. tonee understands gear names, genre vocabulary, and Ableton-specific terms.

works well
"make the reverb tail shorter on the vox"
"duck the pads harder under the kick"
"the snare feels thin, add some body around 200 hz"
"raise the send to the plate by 2 dB"
less useful
"fix track 3 device parameter 7"
"set EQ Eight band 2 gain to -3.0"
"modify the compressor"
"do something with the send"

Vague intent ("do something with the send") will get a clarifying question. Specific intent with natural language ("raise the send to the plate by 2 dB") executes directly.

03 /When it asks, when it acts

tonee defaults to conservative. If a request could apply to multiple tracks or its interpretation could cause an unwanted change, it asks one short clarifying question before doing anything.

▸ you: warm up the bass
▸ tonee: You have SUB BASS and BASS GTR. Which one, or both?
▸ you: just the sub
✓ tool: added Saturator (warm preset) → SUB BASS
▸ tonee: Done. Drive at -6 dB, tone at 0. Want me to dial it back a touch?

When the intent is unambiguous, it executes immediately and tells you what it did. Every change lands on the undo stack, so one ⌘Z in Live reverts it completely.

One question at a time: tonee won't fire five clarifying questions in a row. If it needs more than one piece of info, it picks the most important one and infers the rest conservatively.

04 /Session memory

Within a session, tonee remembers the full conversation. You can refer back to earlier moves: "undo the thing you did to the reverb" or "actually, do the same to the delay track" both work naturally.

Every conversation is saved to the history tab in chronological order. You can reopen any past session and continue it. tonee picks up with whatever project is currently open. History is about the conversation, not a specific file.

For things you want tonee to carry across all future chats (your preferred signal chain, how you like your reverbs, anything), just tell it to remember:

▸ you: remember that I always want the dry/wet below 25% on reverbs
✓ tonee: Got it, saved to memory. I'll default to that on every reverb from now on.

Memories persist across all sessions. Recipes replay a fixed sequence of steps; memories shape how tonee makes decisions.

05 /A full example

A realistic back-and-forth working on a vocal chain mid-session:

▸ you: the lead vocal feels harsh. nothing muddy though.
✓ tool: reading VOX LEAD → Operator → Glue Comp → Valhalla VintageVerb
▸ tonee: I'll cut around 3-5 kHz and add a soft high shelf rolloff above 12 kHz.
adding EQ Eight: bell -2.5 dB @ 4.2 kHz · shelf -1.8 dB @ 12 kHz
✓ tool: committed [#14]
▸ you: better. now the reverb is swamping it.
▸ tonee: I'll reduce the pre-delay and pull the wet mix down, which keeps the space without the wash.
VintageVerb: pre-delay 18 ms → 32 ms · mix 28% → 18%
✓ tool: committed [#15]
▸ you: save that as "clean vox"
✓ tool: recipe saved · "clean vox" · 2 steps · /run clean vox

06 /Habits that help

Name your tracks clearly
tonee uses track names to disambiguate. "VOX LEAD" beats "Audio 7".
State what you don't want
"warm, but nothing muddy" narrows the search space and gives better results than "warm".
One intent per message
Chaining requests ("warm the bass and also fix the kick transient") is fine, but separate messages give cleaner undo history.
Use ⌘Z freely
Everything is reversible. Try things. The undo guard bundles each tonee operation so one undo reverts the whole move.
Save what works
If a chain of moves sounds right, say "save that as a recipe" before you close the session.
© 2026 tonee studio
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.