Your agents.
Your hardware.

Give a place to work. Brigade keeps their sessions on your machine or server, ready whenever you come back.

Choose how
you work.

Connect Claude Code or Codex, then start a session. Keep separate connections for different accounts and choose the one the task needs.

Talk it through.

ACP chat keeps the conversation, diffs and tool activity together. Reply to permission requests in place and jump back to earlier prompts with Time Machine.

Work in chat

Stay in the terminal.

Prefer the agent’s own CLI? Use a full terminal in your browser. A separate shell is also available alongside ACP when you need to inspect or run something yourself.

Use CLI sessions

Work with the result.

Install an MCP App for a task-specific interface. CAD puts a live model, editable parameters and your prompt together, with build123d source and STEP export.

Explore MCP Apps

Make it
your agent.

The connection is only the start. Give the agent your tools, choose how it responds and keep useful knowledge beyond a single conversation.

Claude connects with a subscription token. Codex supports ChatGPT device login or an API key. Connect an agent.

Bring your tools.: Add your own MCP servers and select them per session. Tokens and other secrets stay encrypted on the server; environment variables and headers reference them when needed.
Set the tone.: Use a response profile for concise answers, detailed explanations or your own instructions. Change it as the work changes, without rewriting your messages.
Keep what you learn.: Notes and archived conversations live in your private git repository, shared across your agents. Archive preserves a read-only chat snapshot; it is not a workspace backup.

Close the tab.
Not the task.

The agent runs independently of your browser connection. Come back to the conversation, see unread replies and carry on from another device.

Pick it up in Telegram.

Connect your own bot. Chats and topics become grouped sessions, with replies, images and files in Telegram and Brigade. The bot responds only to its linked owner, including guest mentions.

Connect a bot

Keep your Mac in reach.

Switch between local and remote environments in Brigade.app. Forward remote session ports to localhost and mount workspaces with FUSE-T, installed separately.

Connect a remote environment

See what came out of it.

Open files, images and interactive forms in chat, or preview a running dev server. Add ntfy connections when you want notifications outside Brigade.

Files, previews and interactive UI

Give it a home.

One Go binary serves Brigade and its web interface. Run agents as local processes or in Docker, with a custom image when your tools need one.

Linux amd64 · Docker installed

curl -fsSL https://grigory51.github.io/brigade/install.sh | sudo sh

The installer generates credentials and starts Brigade on port 8080. It grants Brigade access to the Docker socket: use a trusted host and HTTPS or a VPN. Read the installer.

First session guide Docker setup Linux binary Build from source

Decide who gets in.

Use password login or your own OIDC provider, including ZITADEL. Configure a required role and turn off local passwords if you want provider-only sign-in.

Configure authentication