Our Technology
Most tools stop at the API.
Braus works in the app itself.
A worker reads each window as text and uses its controls, on a display of its own. It learns each app as it goes, and runs on free models or the model you connect.
How Braus works
From the window to the work.
Perception
It reads the window as text.
A worker turns each window into a Scene: labels, values, controls and panels with their state, from text recognition and what the app exposes to accessibility. It works in apps without an API, and screen images stay on your Mac.
How Braus reads a windowBackground
It works on a display of its own.
Each worker moves its app’s window to a virtual display, off your screen, and sends input only to that window. Several workers run at once, each in its own app. Your cursor and focus stay yours. The window returns when the work is done.
How the background worksMemory
It learns your apps.
As a worker observes and acts, Braus records the controls it found and the effects it checked, in one file per app on your Mac. Every worker starts its next job with that knowledge, and you can inspect it in the Brain.
How memory worksModels and MCP
Free models, or your own agent.
Braus comes with free models and Forte’s own plans, so a worker is ready from its first job. You can still connect Claude or ChatGPT, and Claude Code or Codex can run as workers or drive Braus over MCP, through a local bridge on your Mac.
Set up MCPOn your Mac
Your files stay where they are.
Braus works with your files on your Mac. App knowledge, conversations and their history are stored there, in the Braus folder, and window images never leave it. The model a worker uses receives text: the window as text, and your request.
Permissions and data
Pro Tools
Logic Pro
DaVinci ResolveOpen source at the core
Read the code that works in your sessions. Two editions: the app from Forte, and the open source edition on GitHub.
Forte sign-in
The Braus app
The app you download here. It works with your Forte account, runs your workers and keeps what they learn on your Mac.
Apache 2.0
The open source edition
The app, the engine and the background driver, on GitHub. Read the code, build it yourself, or build on it.
Inside fMusic and fPost
The specialists: one job each, done the same way every time.
It runs the DAW like an operator.
Forte is a native automation layer for Pro Tools and Logic. It does the operator work end to end: importing, routing, naming, organizing and printing, the same moves a trained assistant would make, just without the clicking and typing.
It works where APIs do not reach.
Most of an audio job lives outside the integrations vendors expose. Forte’s unit of work is the action itself, not the API call, so it covers the whole turnover, including the steps no plugin or SDK can touch. Pro Tools, Logic, and AAF from any NLE.
On-device, by architecture.
Everything runs on your Mac, or on-prem inside your facility. No uploads, no cloud round trips, no connection required. Unreleased mixes, NDA material and client audio never leave the machine, because there is nothing to send them to.
It understands the audio, not the file name.
On-device recognition classifies dialogue, music and effects from the signal itself, with models we built for audio post. A clip named audio_final_v3_NEW still lands on the right track, because Forte listens to what is inside it.
Every AAF, read in seconds.
AAF is handled differently by every vendor. Forte reads files from Pro Tools, Media Composer, DaVinci Resolve and Premiere, reconciles the quirks each one introduces, and shows you exactly what is inside before anything touches your session.