Give your AI a world to work in.
A desktop home for your AI crew. Give agents real tasks, connect their tools, and build workflows across a living pixel-art station.
WHAT IT IS
A living simulation on your machine where every sprite is a real agent doing real work. Recruit a crew, connect real tools and real models, and build the station into a workforce shaped around you — the only limit is what you ask for.
- Placed gear is real capability. A signal dish grants web, a cabinet grants files, a workbench grants a terminal — place one and the whole crew draws on it.
- Every bay is another agent, running its own work in parallel.
- The floor is honest. An agent at a lit desk means a live run — the timer on screen is the real one.
You direct from COMMS. They think, browse, build files, and deliver — with your models, your keys, on your machine.
FEATURES
- 01
A crew shaped around you
Recruit specialists, give them personalities, and direct their work from COMMS. Each agent has its own desk and notebook.
Meet your crew → - 02
Workflows you can see
Connect agents with conveyors. Use filters, splitters, and joiners to route real jobs and combine their results.
Build a workflow → - 03
Tools that do real work
Let agents browse, work with files, run code, and use connected services. Placed gear grants capabilities to your crew.
Explore capabilities → - 04
Useful work, on repeat
Keep a successful process as a recipe, schedule a routine, or configure Night Shift for unattended work.
Set up a routine → - 05
Your models. Your machine.
Choose a model provider or use a local model. Your station, conversations, and work history live on your computer.
Choose a provider → - 06
Stay connected to your station
Send tasks through messaging channels, connect external tools, and bring other agent harnesses into your workflow.
Connect your tools →
DOCS & HELP
Get up and running
Install bdibranding, connect a model, and send your first task.
Start here → THE HANDBOOKFind your next step
Guides and reference organized around what you want to do.
Browse documentation → NEED A HAND?Get unstuck
Find an answer, troubleshoot a problem, or contact support.
Open the help center →FAQ
Is bdibranding free?
The software is free to run. Model usage costs whatever your provider charges — you bring your own API key (or OAuth account), and bdibranding shows you real cost per run. No markup, no subscription required to use your own keys. If you'd rather not manage keys at all, bdibranding Credits are an optional managed plan — never required.
Is the work actually real?
Yes — that's the whole point. Every agent run is a real model call with real tools; files get written, browsers get driven, and the ledger records real cost. The station never renders state the harness can't prove. If it looks like an agent is working, it is.
Do I have to build conveyor belts to use it?
No. Chatting with an agent from COMMS needs no belts at all. Belts are for real jobs — work with several parts, or work that should flow through several agents on its own, especially while you're away. The conveyor guide shows the whole idea in five minutes, and the LINES tool drops a finished line in one click.
Where does my data live?
On your machine. Station state, transcripts, memory, and ledgers live in your local bdibranding workspace. Requests go to your model provider only when an agent runs, and to the wider network only when you explicitly grant a network tool or connector.
What do I need to start?
A Windows or macOS machine and one model provider: an OpenRouter API key works everywhere, a ChatGPT, Grok, or Kimi sign-in needs no key at all, and Ollama runs free and fully local. That's it — full power from minute one, nothing gated behind progression.
Can it spend money without me noticing?
No. Every conveyor line has a per-job budget ($2.00 unless you raise it, $50 ceiling) and an optional per-day cap; the BUDGET panel adds hard per-run, per-agent, per-day, and global caps the sidecar enforces against the real ledger. Night Shift is limited to a number of unattended jobs per day you choose. Use Stop in COMMS to interrupt the current task.