Magic Coder & BridgeApp
Magic Coder doesn’t run in isolation. It’s the coding surface in a larger product — BridgeApp — and almost everything Magic Coder does flows through it.
The shape of the pairing
Section titled “The shape of the pairing”- BridgeApp is the platform. Your account, the agentic engine that runs the model, billing, your team, your tasks, your docs, your conversation history.
- Magic Coder is the agent that runs on your machine. It has permission to read your files, edit them with diffs, and execute shell commands. It uses BridgeApp’s engine and identity to do its work.
The two are tightly coupled by design. You can’t use Magic Coder without a BridgeApp account, and Magic Coder can read and manage some of your BridgeApp data — like tasks and docs — as part of its work.
What each side does
Section titled “What each side does”| Concern | Where it lives |
|---|---|
| Your account, sign-in, billing | BridgeApp |
| The model and the agentic engine | BridgeApp |
| Conversation threads (resumable across devices) | BridgeApp |
| Available models, defaults, model switching | BridgeApp |
| Reading and editing your local files | Magic Coder, on your machine |
| Running shell commands | Magic Coder, on your machine |
| Trust decisions, workspace boundaries, permission rules | Magic Coder, on your machine |
| Themes, UI preferences | Magic Coder, on your machine |
This split is why threads are portable: the conversation lives in BridgeApp, so resuming a thread from a different machine works as long as that machine has the relevant repo and a Magic Coder install.
What you need
Section titled “What you need”To use Magic Coder you need:
- A BridgeApp account. If you don’t have one, sign up at bridgeapp.ai before installing.
- The
coderbinary installed on your machine. See Install. - A repository you want to work in.
Authentication
Section titled “Authentication”Sign-in uses OIDC against BridgeApp’s auth service. The first time you run coder, it opens a browser, you sign in to BridgeApp, and the credentials are saved on your machine for future sessions. Inside the TUI, /login starts a fresh login flow and /logout clears the saved credential. Full details in Sign in.
What’s coming
Section titled “What’s coming”Today, you talk to Magic Coder by running coder in your terminal (or via the desktop and VS Code previews). In the near future, you’ll also be able to talk to Magic Coder directly inside BridgeApp itself — the same agent, reachable from the BridgeApp web app and your phone. The terminal will stay the most powerful surface; BridgeApp will be the most reachable one.