Agents
Let an AI agent such as Claude Code, Codex or Claude Desktop set up and bounce your sessions.
In short
Turn it on
Open Settings › Agents and switch on Allow agents to control Fast Bounce. Agent control is part of the paid plans.
Connect a tool
Under Your tools, press Set up next to Claude Code, Claude Desktop and Cowork, or Codex. Fast Bounce writes the connection into that tool for you. Each one talks to Fast Bounce on your own computer only.
Ask it what it can do
Start with "What can you do with Fast Bounce?". The agent looks at your open session, offers three things to try, and does the job you pick: "add a stem for every audio track inside the HARM folder, then bounce". Keep Fast Bounce open while it bounces.
Fast Bounce can be driven by an AI agent on your computer. The agent sees what Fast Bounce sees (your loaded sessions, their tracks, markers, buses and bounces) and can do what you do in the window: load sessions, add and edit bounces, apply presets, and start, pause or stop bouncing. You stay in charge: it only works while Fast Bounce is open and you are signed in, and Settings › Agents turns it on and off. To control Fast Bounce from your phone instead, see iPhone App.
Turn it on
Open Settings › Agents and switch on Allow agents to control Fast Bounce. The row underneath shows that Fast Bounce is listening, and later when an agent last ran a command.
Agent control is part of the Monthly, Annual and Perpetual plans. On the free plan the switch works, but every command is refused with a message that points at the plans; the agent can still read the guide and tell you what Fast Bounce does.
Connect a tool
Your tools lists the agent tools found on this computer and whether each one is set up. Press Set up and Fast Bounce writes its connection into that tool's own settings (only the Fast Bounce entry, with a backup kept next to the file). Then:
| Tool | After Set up |
|---|---|
| Claude Code | Type /mcp in Claude Code to see Fast Bounce connected. Its Fast Bounce tools work without asking, so unattended bouncing never waits on a permission prompt; the switch under the row turns that off if you'd rather approve each tool. |
| Claude Desktop and Cowork | Quit and reopen Claude Desktop. |
| Codex | Start a new Codex session. Its Fast Bounce tools work without asking too; the switch under its row turns that off, after which Codex asks only before deleting bounces or ejecting a session. |
Once a tool has talked to Fast Bounce, its row shows when it last connected. Remove takes the entry out again. If a tool isn't installed, the row says so with a link to get it.
For a tool that isn't listed, Manual setup › Show reveals the local address, the private token and paste-ready setup blocks. Regenerate token replaces the token and updates the tools you set up from the pane; tools set up by hand need the new token pasted in.
Ask it what it can do
The agent knows Fast Bounce before you say a word: when it connects, Fast Bounce tells it what the app does, to look at your status first, to show you the plan before bouncing, and to ask before deleting anything. So the first message can simply be "What can you do with Fast Bounce?". The agent looks at what you have open (Pro Tools, the loaded sessions, queued bounces), explains in a few sentences what it can do from there, and offers three things to try that fit what it sees. Pick one, or ask for something else in your own words.
Three ways to start:
| Where | How |
|---|---|
| Any tool | Ask "What can you do with Fast Bounce?", or copy an example from Try asking in Settings › Agents (each row has a Copy button). |
| Claude Code | Type /mcp__fastbounce__getting-started. The other prompts are stems, alt-mixes, album-presets, bounce-and-wait and troubleshoot; each asks you for what it needs, such as the folder or the preset name. |
| Claude Desktop and Cowork | Open the + menu in a chat: the same prompts, and the guide, command reference, examples and error codes as attachments. |
Codex gets the tools and the same help through them; ask it what it can do.
Examples to try
Each line is something to say. The agent reads your session first, so names like DRUMS, IN and OUT become the folders and markers you have.
<!-- agent-guide:examples --> <!-- Generated from fast-bounce-client-dev/src/main/agent/guide.js by scripts/sync-agent-guide.mjs. Edits here are overwritten: edit guide.js, then run the sync. -->| Say | What the agent does |
|---|---|
| "What can you do with Fast Bounce? Look at what I have open and suggest three things to try." | Reads the status and what is loaded, explains what it can do and offers three things that fit. |
| "What's loaded in Fast Bounce, and which session is open in Pro Tools?" | Lists your sessions with their bounce counts and which one Pro Tools has open. |
| "Load the session that is open in Pro Tools and show me its tracks, folders and markers." | Adds the open session to Fast Bounce and reads it: tracks, folder tree, markers and marker pairs, buses and outputs. |
| "Add one Solo stem per audio track inside the DRUMS folder, between the IN and OUT markers, then show me the plan before bouncing." | Finds the folder and the markers, adds a Batch of Solo bounces with that range, and shows the plan without starting. |
| "Add a Mix, an instrumental with the vocal tracks muted and a TV mix with the lead vocal muted, all between IN and OUT as 24-bit WAV." | Adds one Mix bounce and two Mute bounces with the tracks it finds, the marker range and the format you asked for. |
| "Bounce every clip on the SFX track as its own file, named after the clip." | Adds a Clips bounce: one file per clip on that track, timed to where each clip sits. |
| "Take " v1" off every bounce name on the album and show me the new names first." | Previews the new names across every loaded session, tells you if two would share a name, then renames. |
| "Make a preset called Stems 24 that bounces one Solo stem per audio track as 24-bit WAV into a Stems subfolder." | Saves a Batch preset with the rule "all audio tracks" and those values. It shows up in the Presets sheet. |
| "Apply my Stems preset to every loaded session, tell me what each one missed, then show me the plan." | Applies the preset to all sessions, matching tracks, buses and markers by name, reports what each session missed, and shows the plan. |
| "Queue everything, show me the plan, then start bouncing, wait for it to finish and give me the Bounce Summary." | Queues the bounces, shows the plan, starts bouncing, waits, and reports the Bounce Summary with each failure's reason. |
| "Find the stems I bounced for this session, tell me if any are missing, and zip the ones that are there." | Finds each bounce's files where they landed, tells you which were moved or deleted, and works on the ones it found. An agent running on this computer can open the files; a remote one only sees their paths. |
| "Make 24-bit 48 kHz WAV my default and put the date in my Mix names." | Changes Bounce Defaults for sessions you add from now on, and the Mix pattern in Naming Rules. |
Everything the agent adds shows up in the window as it happens, so you can check it before pressing Bounce yourself, or let the agent press it. Bounces and presets the agent adds without a name of its own follow your Naming Rules, the same as from the window. Marker ranges come from your IN/OUT (or START/END) pairs and from memory locations that hold a range.
If something goes wrong
When a command fails, the agent gets a short code and a sentence that says what to do next, and it usually sorts it out by itself (reading the session again, or waiting for bouncing to finish). The codes you might see it mention:
<!-- agent-guide:errors --> <!-- Generated from fast-bounce-client-dev/src/main/agent/guide.js by scripts/sync-agent-guide.mjs. Edits here are overwritten: edit guide.js, then run the sync. -->| The agent says | What it means | What to do |
|---|---|---|
PLAN_REQUIRED | Agent control is part of the paid plans, and this account is on the free plan. | Agent control is part of the Monthly, Annual and Perpetual plans. |
NOT_SIGNED_IN | Nobody is signed in to Fast Bounce on this computer. | Sign in to Fast Bounce, then ask again. |
APP_NOT_READY | The Fast Bounce window has not finished opening. | Give the window a moment to open, then ask again. |
PRO_TOOLS_NOT_RUNNING | The command needs Pro Tools, and it is not running or not connected. | Open Pro Tools and a session. |
SESSION_NOT_OPEN | The command needs this session open in Pro Tools, and another one (or none) is. | Open the session in Pro Tools, or ask the agent to open it. |
NOT_FOUND | No session, bounce or preset has that id or name. | The name or id was wrong. The agent lists what is there and tries again. |
INVALID_INPUT | An argument is missing, wrong, or names something the session does not have (a track, folder, marker or bus). | A track, folder, marker or bus name did not match the session. The agent reads the session again. |
RUN_IN_PROGRESS | Fast Bounce is bouncing, and bounces cannot be changed while it is. | Wait until bouncing finishes, or pause it first. |
TIMEOUT | The command did not finish in time. Loading big sessions and opening one in Pro Tools can take minutes. | It took longer than expected. Ask again; it has often finished meanwhile. |
INTERNAL | Something went wrong inside Fast Bounce. | Try once more. If it keeps failing, Settings › Support sends us the logs. |
When the tool cannot reach Fast Bounce at all:
- The tool does not list Fast Bounce, or the connection is refused. Open Fast Bounce, check that Allow agents to control Fast Bounce is on, then reconnect the tool (in Claude Code,
/mcp). - Every call answers 401. The token the tool has no longer matches, usually after Regenerate token. Press Set up again next to the tool, or paste the new token into a tool set up by hand.
- Claude Desktop shows no Fast Bounce tools. Quit and reopen it; it reads its tools when it starts.
- Codex asks before every tool. Turn on Let Codex use Fast Bounce without asking under its row.
- Bouncing does not start. Pro Tools must be running with the session open. Ask the agent for the status, or look at the connection dot in the Fast Bounce window.
In Claude Code, /mcp__fastbounce__troubleshoot walks through these checks with you.
Keep in mind
- Keep Fast Bounce open while it bounces. The bounces live in the Fast Bounce window. Closing it ends them.
- A bounce in progress is never cancelled. As in the window, pause and stop take effect after the bounce Pro Tools is working on.
- An agent can find your bounced files, now or later. Fast Bounce remembers what each bounce wrote, even if you rename the bounce or change its folder afterwards. It checks that folder and tells the agent which files are still there. A file you moved or deleted comes back as missing, and only that folder is checked. An agent on this computer can then open the files; a remote one only sees their paths.
- The agent asks first before deleting bounces or presets, or ejecting a session, and shows you the plan before it starts bouncing, unless you tell it to go ahead.
- The token is private. Anything on your computer that has it can control Fast Bounce. Agents on this computer connect locally; nothing on the network can reach that connection.
- Signing out stops agents until you sign in again.