BridgeApp AI & Magic Coder
If you’ve heard of Magic Coder, you might be wondering how it fits with the AI inside BridgeApp. Short version: they’re cousins, not the same thing. The copilot and agents you’ve read about live inside your workspace; Magic Coder is a separate coding agent that runs on your machine. They share your BridgeApp account, but they do different jobs.
Side by side
Section titled “Side by side”| BridgeApp AI (Copilot & agents) | Magic Coder | |
|---|---|---|
| What it is | AI teammates inside your workspace | A coding agent for your terminal/IDE |
| Where it runs | In the cloud, on BridgeApp’s backend | Locally, on your own computer |
| What it works on | Your chats, tasks, docs, databases | Your actual source code and files |
| How it runs code | In an isolated, sandboxed computer | Directly in your real repository |
| Account | Your BridgeApp account | Also your BridgeApp account (for sign-in, billing, history) |
| Reach it from | BridgeApp web, desktop, and mobile | Terminal, VS Code, or desktop preview |
When to use which
Section titled “When to use which”- Reach for the Bridge copilot or an agent when the work lives in your workspace: summarizing a discussion, turning notes into tasks, answering questions about your data, automating a recurring job.
- Reach for Magic Coder when the work is hands-on coding on your own machine: refactoring a module, fixing a failing test, exploring an unfamiliar codebase, building a feature.
The connective tissue is your BridgeApp account. Magic Coder signs in with it for identity, billing, and saved conversation history — but all of its file and command access stays local on your computer, by design.