Skip to content
All articles

News · 10 minute read

What Braus Can Do in Pro Tools Today, Job by Job

A Pro Tools mix window with tracks routed into colored folders, while an engineer works on a second screen. AI-generated illustration.

Every session has a stretch of work nobody bills for. Routing forty tracks into their folders. Putting the same EQ on every vocal. Setting automation modes before the first pass, rendering a clip through AudioSuite, running Strip Silence on a dozen tom tracks. None of it is hard. All of it takes the hour you wanted for the mix.

Braus is Forte's AI agent for Mac apps, and Pro Tools is where it goes deepest today. If you have been looking for an AI assistant for Pro Tools that does the work instead of describing it, this is how Braus works: you describe the job in plain words, the way you would brief an assistant, and a worker does it in your session. It routes tracks to their folders and buses, places plug-ins on inserts and points sends, renders AudioSuite on a selection, strips silence and sets up the session around the mix. After each change it reads the session back, and it tells you when it could not confirm something.

This article is the list. It is not a roadmap and not a demo reel: it covers what Braus does in Pro Tools 2026.4 and later, today, grouped the way you work, with what it deliberately leaves alone. If a job is not on this page, Braus does not do it in Pro Tools yet, and it is better to read that here than to find out in a session.

Everything Braus does in Pro Tools, at a glance

AreaWhat a worker doesOn your screen
Session and tracksReads the session, imports audio as new tracks, creates, renames, mutes, solos and record-arms tracks, selects tracks and ranges, saves, bounces the mixReading, track changes, saving and bouncing leave Pro Tools where it is
Routing and foldersRoutes outputs to outputs, buses and routing folders, moves tracks into folders, sets inputsBehind your work, checked on a real session
Inserts and sendsPlaces a plug-in in an empty insert slot, points sends A to J, reads every stripChecked in Pro Tools; Pro Tools may come forward for a step
AudioSuiteRenders a plug-in on the selection, always to new filesChecked in Pro Tools; Pro Tools may come forward for a step
EditingRuns Strip Silence with your values, sets the grid from 1 bar to 1/64Strip Silence brings Pro Tools to the front for that step
Mix setupSets automation modes and pan, reads groups, recalls Track Presets and window configurationsChecked in Pro Tools; Pro Tools may come forward for a step

The rest of this article goes through each row, with requests you can copy.

How you ask

Braus takes one request at a time, in plain words. It is not a macro recorder and it does not automate whole workflows: you name the job, a worker does it and reports back. Two requests show the shape that works.

"Create four mono audio tracks named Kick, Snare, OH L and OH R, then record-arm them." The four tracks appear, named and armed.

"Route Lead Vox, Double and Harmony to the Vox Bus." Each track's output now points to the bus, and Braus reads each one back to confirm it.

If you are starting from zero, the Braus launch post covers setup in four steps.

Session and tracks

The foundation is the session itself. A worker reads tracks, clips, the current selection and the session state, such as sample rate and bit depth. It creates, renames, mutes, solos and record-arms tracks, selects tracks and timeline ranges, saves the session and bounces the mix. It also imports audio files as new tracks and checks that they arrived.

Reading the session, creating, renaming and muting tracks, saving and bouncing need no macOS permission at all, and they leave Pro Tools where it is while you keep working on something else. "Which tracks are muted or record-armed?" gets you an answer instead of a scroll through the session. "Import the stems in Desktop/Stems as new tracks, then save" is a complete request.

Routing and folders: the job checked most closely

Routing decides whether your stems work later, and it is the Pro Tools job Braus has been checked on most closely behind your work. A worker routes the main output of one or more tracks to an output, a bus or a routing folder, by its name. It lists the outputs and buses in the session and reads where each track is routed. It moves tracks into a folder, out to the top level, or before or after another track, sets track inputs, and brings a track that is out of view into view before working on it.

Routing runs on a display of its own: Pro Tools does not come to the front, and your mouse and keyboard stay yours. In a real session, a worker routed nine tracks into their folders, including three that were out of view, which it scrolled to first. Each new output is read back after the change, and if you stop the worker halfway it leaves no routing menu open. For the bus structure that routing feeds, the guide to mix template bus routing in Pro Tools covers how to set it up once.

Inserts, sends and AudioSuite

A worker puts a plug-in in an empty insert slot on mono, stereo or multi-mono tracks; EQ3 7-Band and Dyn3 are the plug-ins it has been checked with. If the slot is already in use, it refuses instead of replacing your plug-in. It points a send slot, A to J, to a bus, an output or a track. It also reads each track's strip, including automation mode, input, inserts and sends, which makes "What is on the drum tracks?" a useful question before a change. A typical request: "Put EQ3 7-Band on the first insert of every vocal track."

For AudioSuite, a worker renders a plug-in on the current selection. It can set the selection first, so one request can cover the range and the render. It always renders to new files and never chooses to overwrite, so the original audio stays untouched.

Editing and mix setup

Strip Silence. A worker runs Strip Silence with the threshold, minimum duration and pad you give it, on the tracks or range you name. This is the one job that brings Pro Tools to the front, for that step only. For how to pick those three values, the guide to Strip Silence in Pro Tools walks through the workflow.

Mix setup. A worker sets the automation mode per track (off, read, touch, latch, touch/latch or write), sets pan, including mono or left and right for stereo tracks, and sets the grid value from 1 bar to 1/64. It reads the list of groups, recalls a Track Preset, and lists and recalls window configurations. "Rename Audio 1 to 4 Kick, Snare, Bass and Vox, set the vocals to Touch and the grid to 1/16, then save" covers the half hour before a mix in one request. The modes themselves are explained in Pro Tools automation explained.

Ask Braus while you work in Pro Tools

Workers take jobs from the Braus app. With the Super Worker you can also talk to Braus from inside Pro Tools: hold Option and Command, say what you need and let go. Ask it to highlight every vocal track and boxes appear around them on screen. Ask how to add a new track and it walks you through the steps out loud, drawing each one. Mark a plug-in or a panel with Control and ask what it does. The Super Worker needs a Mac with Apple silicon, and the Super Worker announcement covers the gesture in full.

How Braus checks its work

After each change, Braus reads the session back to check the result, and it tells you when it could not confirm a change. If a series of track changes fails halfway, Braus puts the tracks back: it removes the tracks it created and restores the previous names, mute, solo and record-arm states. It asks before it deletes anything or does what can't be undone.

You can stop a worker at any time from the Braus app. Stopping does not undo what it already did; it just stops, so check the session before you continue.

What it leaves alone on purpose

It never overwrites audio with AudioSuite. It never replaces a plug-in in a slot that is already in use. It does one job at a time, the one you asked for. Those limits are deliberate, and they are the reason you can hand it a session you care about.

What happens on your screen

Reading the session, track changes, saving, bouncing and routing happen behind your work: your mouse and keyboard stay yours and Pro Tools stays where it is. The other window jobs, such as inserts, sends, AudioSuite, automation modes, inputs, grid and pan, have been checked in Pro Tools itself and are being checked one by one behind your work. Until each one is, Pro Tools may come forward for the step that needs it, only for that step. Strip Silence always brings Pro Tools to the front for its step.

One worker uses the background display at a time. Others wait their turn, and a waiting worker's row reads "Waiting for the computer." Keep your Mac's display awake while a worker is busy. The background guide covers the details.

What you need

Braus needs macOS 15 or later, with Pro Tools 2026.4 or later open on the same Mac; it has been measured on Pro Tools 2026.4.1 and 2026.11. You also need a Forte account, which is free to create, and a model of your own: free models through OpenRouter or a Google AI Studio key, your ChatGPT or Claude plan, Gemini, or a local model with Ollama. The free models guide shows the no-cost route.

Reading and track jobs need no macOS permission. Window jobs need Accessibility, and working behind your own work needs Screen Recording as well. The permissions page lists exactly what your version of Braus asks for. If you already work in Claude Code or Codex, you can also drive Braus from there over MCP; the MCP setup guide shows how.

The full reference, kept current, lives in the Braus docs for Pro Tools.

Braus, fMusic and fPost

Braus is a different kind of tool from fMusic and fPost. Those apply a full prep or export flow to a session in one pass; Braus takes one request at a time, in your words. Many engineers will use both. Forte has been an Avid Technology Partner since June 2025, and fMusic and fPost also run inside Pro Tools as Pro Tools Extensions.

Beyond Pro Tools

In other Mac apps, a worker works the way a person does, on its own virtual desktop. Dedicated support for apps such as DaVinci Resolve is still in testing and not solid yet, so Pro Tools is the app to judge Braus on today. Braus also has an open source edition, documented at braus.ai.

FAQ

Which Pro Tools versions does Braus work with?

Pro Tools 2026.4 or later, open on the same Mac, with Braus on macOS 15 or later. It has been measured on Pro Tools 2026.4.1 and 2026.11.

Can Braus route tracks to folders and buses?

Yes. A worker routes the main output of one or more tracks to an output, a bus or a routing folder by name, moves tracks into folders, and reads each new output back. Routing runs behind your work, so Pro Tools does not come to the front.

Does Braus overwrite my audio when it renders AudioSuite?

No. It renders the plug-in on your selection and always to new files. It never chooses to overwrite, so the original audio stays untouched.

Can I keep working while Braus works in Pro Tools?

For reading the session, track changes, saving, bouncing and routing, yes: your mouse and keyboard stay yours and Pro Tools stays where it is. Other window jobs may bring Pro Tools forward for the step that needs it, and Strip Silence always does.

Is Braus free?

Yes, Braus is free to use. You bring the model, and free models through OpenRouter or a Google AI Studio key work, so running it can cost nothing.

Braus does the repetitive jobs of a Pro Tools session one request at a time, checks each change and tells you what it could not confirm. See the full page at forte-ai.com/braus/pro-tools.

Share this article

Get Forte for macOS

fMusic, fPost, fMusic for Logic Pro, and AAF Checker: native, on-device Mac apps. Braus is free to start and works in Pro Tools.

Download for macOS

Keep reading