A worker for every job.
In the apps you already use.
Give a worker a job in plain words. It works inside your app in the background, and checks each step.
Open DaVinci, create session 'test_carla', import the video from downloads 'carla_video.mp4', edit it making it black and white fast, zip it to downloads and send it to Loris on Slack.
18:00Opened DaVinci Resolve · chose File from the menu bar · 24 more
- Checked open apps
- Opened DaVinci Resolve
- Tried to press New Project in content…
- Chose File from the menu bar
- Chose File > New Project… from the menu bar
- Typed “test_carla” into control|newproject1
- Pressed Create
- Pressed Open
- Pressed Change
- Pressed carla_video.mp4
- Chose File > New Timeline… from the menu bar
- Typed “carla_edit” into control|timeline1
- Pressed Create
- Pressed Color in bottom bar
- Viewed the window
- Typed “0” into control|5000
- Pressed Return
- Typed “200” into control|10000
- Pressed Quick Export
- Typed “test_carla_bw_2x.mov” into control|carlaeditmov
- Pressed Save
- Closed DaVinci Resolve
- Opened Finder
- Tried to select Compress “test_carla_bw… from test_carla_bw_2x’s menu
- Pressed test_carla_bw_2x.zip
- Dragged test_carla_bw_2x.zip to Arrow Down Circle
- Checked Slack’s open windows
- Opened Slack
- Pressed Carica dal computer
- Pressed test_carla_bw_2x.zip
- Tried to press Open in the dialog
- Viewed the window
- Tried to press Invia messaggio Loris -…
- Pressed v
- Viewed the window
I’ll set up the DaVinci project, import the clip, apply a black and white grade and faster playback, then export, zip, and send it to Loris. I’ll check the available controls as I go and verify each output before sharing it.
DaVinci took focus on your display while its export panel opened, so Braus has paused the background controls. Please switch back to your own window; I’ll continue from the export panel once the seat is available.
Created and saved the DaVinci project test_carla, imported carla_video.mp4, made it black and white, and set it to 2× speed. The edited video is in test_carla_bw_2x.zip (/Users/mac/Downloads/test_carla_bw_2x.zip), and the ZIP appears in Loris’s Slack conversation.
Using chrome, can you search X for the top trending posts about computer use agents? Once you have them, rank them from most to least popular and draft a post for me, then I will schedule it.
18:59Opened com.google.Chrome · pressed Return
- Opened com.google.Chrome
- Tried to type “computer use agents” into Q Search
- Pressed Return
[…]
3. @Lummox_eth — "Build Your Own AI Employees on GPT-6 Astra: The A-Z Agent Playbook" (Sep 16)
157K views, 1.4K likes, 278 reposts, 96 replies
Long-form article framing agents as staff rather than tools.
4. @ataiiam (Atai Barkai) — "Introducing OpenMuse" (Sep 22)
155K views, 1K likes, 110 reposts, 55 replies
Open-source, self-hostable assistant that works with any agent harness.
Also in the top results, but I could not read their engagement counts — the metric rows sit below tall media and never rendered as text in the accessibility tree across several scroll positions:
- @ataiiam — "Introducing OpenDots" (Oct 1): self-hostable always-on coworkers; computer use across browser, terminal, files
- @N01ennn — "Sam Altman just broke down how to actually use DOTS agents" (Oct 4): "give it responsibilities, not tasks"
- @Lummox_eth — "GitHub is becoming dangerous for AI agents" (Oct 1): 10 open-source repos for autonomous systems
- @BuildwithOmkarr — "Introducing OpenMausBot" (Sep 23): open-source team of agents with real desktop access
The clear theme: the center of gravity moved from "agent that answers" to "agent that stays running" — always-on, own cloud computer, own browser, plugged into your existing apps. And the loudest open-source replies (OpenDots, OpenMuse, OpenMausBot) are all self-hostable answers to OpenAI's closed launch.
Draft post
Everyone's reading the dots launch as a model story. It isn't.
The shift is from agents that answer to agents that never switch off — own cloud computer, own browser, plugged into the apps you already pay for.
Which is why the most interesting replies weren't takes. They were repos. OpenDots, OpenMuse, OpenMausBot — all shipped within two weeks, all self-hostable, all betting the runtime matters more than the model.
The best line I saw on it, from a breakdown of Altman's own guidance: give it responsibilities, not tasks.
That's the whole gap. Tasks are what you delegate to software. Responsibilities are what you delegate to people.
A shorter, punchier alternative:
"Give it responsibilities, not tasks."
That's the line from this week's agent discourse that actually matters.
Tasks are what you delegate to software. Responsibilities are what you delegate to people. Every always-on agent shipping right now — dots, OpenDots, OpenMuse — is a bet that the second one is now possible.
The model was never the bottleneck. The runtime was.
Both are under 280 characters per paragraph block but run long as a whole — tell me if you want it cut to a single-tweet length, and I can tighten it. I haven't posted or scheduled anything; the Chrome session is still open on the search results if you want me to pull more posts or check a specific account.
Upload the final mix and the stems to the client’s folder, then send them the link.
17:42Opened Finder · opened Google Chrome
- Opened Finder
- Checked the Delivery folder
- Opened Google Chrome
- Viewed the window
The final mix and all 12 stems are in Delivery, and the client’s folder is open in Chrome.
The folder already holds a mix from Tuesday. Should I replace it, or upload this one beside it as v2?
Turn my notes from Monday’s call into a checklist for the release.
16:05Opened Notes · typed “release call” into Search
- Opened Notes
- Typed “release call” into Search
- Viewed the window
Here is the checklist from Monday’s call:
- Approve the final artwork by Thursday.
- Send the mastered tracks to distribution.
- Book the listening session with the label.
- Write the credits for the liner notes.
Export the album masters as 24-bit WAV files into the Masters folder, named by track number.
14:20Opened the album session · exported 10 tracks
- Opened the album session
- Exported 10 tracks
- Checked the Masters folder
All ten masters are in Masters as 24-bit WAV files, from 01 to 10. Nothing clipped on export.
Clean up the dialogue in scene 12: take out the hum and even out the levels.
19:10Opened the scene 12 session · removed the hum from 14 clips · 1 more
- Opened the scene 12 session
- Removed the hum from 14 clips
- Matched the clip levels
Scene 12 is clean: the hum is gone from all 14 clips and the lines sit at one level. I saved it as a new version next to the original.
This model doesn’t offer Effort levels.
How it works
Brief a worker like a colleague.
Any app
Works in any app.
Even the ones without an API. A worker reads each window as text on your Mac, finds the controls it needs and uses them.
How Braus reads a windowIn the background
Your cursor stays yours.
Workers use your apps in the background while you keep working. Your mouse and keyboard stay yours, and you can stop a worker at any time from the Braus app.
How the background worksMemory
It learns your apps.
Every job teaches Braus more about an app: its windows, its controls and what they do. That knowledge stays on your Mac, and every worker starts the next job with it.
How memory worksIn parallel
Several workers at once.
Give each worker its own job in its own app. They work at the same time and report back one by one, while you stay on yours.
See the plansModels and agents
Braus Flash and Braus Pro.
Braus comes with its own models, on every plan (Braus Flash on Free). Braus Flash is fast and made for everyday jobs. Braus Pro is the most capable and uses your plan faster. Under each is a leading third-party model, tested on real Mac work and reviewed every month. Prefer your own? Connect your ChatGPT or Claude plan, your API keys, or a local model with Ollama, or drive Braus from your agent over MCP: Claude Code or Codex.
Set up MCP
Logic Pro
DaVinci ResolveAudio and video first
Pick your app to see what a worker does there. What works depends on the app and the task.
Put a worker on the job
Audio and video, from the first import to the last delivery.
Sessions that arrive ready to mix. Brief a worker for the jobs around your prep: import stems, name and arm tracks. It works alongside fMusic and fPost and reads the session back before it says done.
Stems out, named and checked. Tell a worker which stems the delivery needs. It exports them from Logic Pro, names every file your way and lists what it checked.
Your live set, built before soundcheck. Hand over the stems and the running order. A worker builds the Ableton Live set track by track and scene by scene, and leaves the sound to you.
Selects on a timeline before you sit down. Point a worker at the day’s footage. It imports it into bins, lines up your selects on a new sequence in Premiere Pro, and leaves the cut to you.
Every version rendered and named. You keep working. List the versions once: lengths, formats, names. A worker queues them in DaVinci Resolve, waits for your go, renders each one and checks the list before it reports back.
Masters out the door, one per destination. Tell a worker what each destination needs. It shares the project from Final Cut Pro, names the files and tells you when each one is written.
- Import the 14 stems in Desktop/Song_04 as new tracks, named after the files.
- Imported 14 files as 14 new tracks. Names match the files. The session is 48 kHz, 24-bit.
- Mute the two reference tracks and record-arm Lead Vox.
- Ref Mix and Ref Master are muted, Lead Vox is armed. I read the session back: nothing else changed.
- Export Drums, Bass, Keys, Vox and FX from Song_07. 48 kHz, 24-bit, named like Song07_Drums.
- Exporting in the background. Keep working.
- 5 stems in Bounces/Song_07, all 48 kHz, 24-bit, all 3:42 long.
- Add an instrumental too.
- Done: Song07_Instrumental, 3:42, in the same folder.
- Build a set from Tour/Stems: a track per stem, a scene per song, in folder order.
- Found 9 songs and 54 stems. Building the set now.
- Ready: 6 tracks, 9 scenes, 54 clips, each song at its own tempo. Save it as Tour_Set_v1?
- Yes, save it.
- Saved. Live is back on your screen.
- Import the Day 03 card into a bin per scene, then put every clip labeled Select on a new sequence.
- 212 clips imported into 7 bins. 18 are labeled Select.
- Day03_Selects is ready: 18 clips in scene order, 11:40 long.
- Great. I’ll take it from here.
- Render the 30s, 15s and 6s timelines as ProRes 422 HQ and H.264, named Spot_30_v3 and so on.
- 6 jobs in the Render Queue, names set. Start the render?
- Go.
- 6 of 6 rendered to Exports/Spot_v3. Each file matches its timeline: 0:30, 0:15, 0:06.
- Share Trailer_v5 as a 4K master file and as 1080p for the web.
- 2 shares started, named Trailer_v5_4K and Trailer_v5_1080p. I’ll report when both files are written.
- Both are in Exports/Trailer, 2:14 each. Close the library?
- No, leave it open.
Open 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.
Set up Braus in four steps.
Sign in with Forte, pick a model, allow the permissions, and give your first worker a job.
- 01
Sign in with Forte
Download Braus for macOS 15 or later and sign in. Forte users already have access. New users can create a free account here or in the app.
- 02
Pick a model
Start with Braus Flash, or Braus Pro on a paid plan, or connect Claude or ChatGPT.
- 03
Allow the permissions
Allow Mac permissions when Braus asks on first launch, so a worker can read and use your apps.
- Accessibility
- Screen Recording
- 04
Give a worker a job
Open your app and tell the worker what you need, in plain words. It reports back when the job is done.
Pricing
Start free.
Braus Flash and one worker at a time, free forever. Pay for workers in parallel, usage and teams, never per action.
Braus plans for individuals
Free
One worker at a time, on your Mac.
€0/ month
Free forever
- One worker at a time, for as long as you like
- Memory on this Mac
- Your ChatGPT or Claude plan, or your API keys
- Free models through your own OpenRouter account, and Gemini
- Local models with Ollama
- Braus Flash, a small monthly allowance
- Connectors with usage data turned on
- Run reports
Pro
For one professional running workers in parallel.
€20/ month
billed yearly, or €25 billed monthly
Everything in Free, plus
- Workers in parallel, no limit
- Memory synced across 2 Macs
- Pre-mapped apps
- Braus Flash and Braus Pro, monthly usage included
- All connectors unlocked
Pro Max
For the heaviest days.
€60/ month
billed yearly, or €75 billed monthly
Everything in Pro, plus
- 5× the usage of Pro
Braus plans for studios and teams
Team Pro
For studios and teams that share the same apps.
€25/ seat / month + VAT
billed yearly, or €30 billed monthly
Everything in Pro, plus
- Shared team memory, anonymized
- Team usage, pooled
- Priority support
Team Pro Max
For teams that run workers all day.
€60/ seat / month + VAT
billed yearly, or €75 billed monthly
Everything in Pro Max, plus
- 5× the usage of Team Pro
- Team usage, pooled
- Shared team memory, anonymized
- Priority support
Enterprise
For organizations with their own software and rules.
Custom
A quote for your organization
Everything in Team Pro Max, plus
- Your software mapped, so workers can use it too
- Pay as you go, with volume discounts
- Training on your workflows
- Local setup: model and hardware
- SSO and audit log
- Support SLA and a dedicated contact
From the blog
Frequently asked questions
What is Braus?
Braus gives you workers for the apps on your Mac. Give a worker a job in plain words. It works inside your app, in the background, while you keep working.
What is a worker?
A Braus worker has a name, a role and a job. Brief it in plain words. It works in your app in the background, checks each step and reports back. Run several at once, each in its own app, and stop any of them whenever you want.
How much does it cost?
You can start free, with Braus Flash and free models, and one worker at a time, for as long as you like. Paid plans add scale: workers in parallel, more usage and teams. You never pay per action.
Which model do I need?
None to start: Braus comes with its own models, Braus Flash and Braus Pro, on every plan (Braus Flash on Free). You can still connect Claude or ChatGPT in the Braus app, or drive Braus from your agent over MCP: Claude Code or Codex.
Do I need a Forte account?
Yes, sign in to Braus with your Forte account. Existing Forte users already have access. If you’re new to Forte, create a free account on this website or inside the Braus app.
Which apps does Braus work in?
Desktop apps on your Mac, even ones without an API. Our focus is Pro Tools, Logic Pro and Ableton Live for audio, and Premiere Pro, DaVinci Resolve and Final Cut Pro for video. What works depends on the app and the task.
What can Braus do in Pro Tools?
Braus reads your Pro Tools session, creates and renames tracks, and changes mute, solo, and record-arm states. It also selects tracks and timeline ranges, imports audio files as new tracks, and opens, saves, and closes sessions. Braus works in the Mix and Edit windows.
Can I keep working while Braus works?
Yes, Braus works in Pro Tools in the background while you keep using your Mac. Your mouse and keyboard stay yours, and Pro Tools does not jump to the front.
What leaves my Mac?
Braus turns app windows into text on your Mac, then sends that text and your request to the model the worker uses. Screen images stay on your Mac. App knowledge and conversations are stored on your Mac. Braus models run only on providers with zero data retention: they don’t keep what you send, so it can’t be used to train models. If you connect your own subscription or API key, that provider’s terms apply.
Which Macs does Braus run on?
Braus requires macOS 15 or later. It cannot be installed on older macOS versions yet. These requirements apply to Braus and differ from those of other Forte apps.
Does Braus check changes and recover from errors?
Braus reads the Pro Tools session after each change and tells you when it could not check the result. If a series of track changes fails halfway, Braus puts the tracks back. It removes tracks it created and restores the previous names, mute, solo, and record-arm states.
Can I stop Braus, and does stopping undo changes?
You can stop Braus at any time from the Braus app. Stopping Braus does not undo changes it has already made in Pro Tools.
Is Braus open source?
Its open source edition is: the app, the engine and the background driver are on GitHub under Apache 2.0. The Braus app you download from Forte works with a Forte sign-in.
Braus, or fMusic and fPost?
Both. fMusic and fPost each do one Pro Tools job, the same way every time: mix prep and stems, or AAF turnovers. Braus workers take the jobs around them, in Pro Tools and your other apps. They share one Forte account, each with its own plan.