# Ember > Ember is an IDE for developers who know how to code and still want to. It is a real editor built around Claude Code: you run several agents at once, each on its own branch and pull request, and you still read every diff, write your own code and own your git. It runs on the Claude subscription you already have, on macOS, Windows and Linux. Who it is for: developers who know how to code and still want to. Ember is a full IDE, not a chat box that replaces one. Latest version: 0.135.0. Platforms: macOS (Apple Silicon), Windows (x64, Arm64), Linux (x64, arm64). Price: free to download; an optional $5 purchase inside the app supports continued development. Requires a Claude Pro or Max subscription and the Claude Code CLI. No API key. ## Pages - [Home](https://buildwithember.ai/): what Ember is, with interactive demos of the branches board, chat, Bonfire, review and the phone app - [Download](https://buildwithember.ai/download): every build of the latest release and how to install it - [Compare](https://buildwithember.ai/compare): Ember vs Cursor vs the Claude Code extension for VS Code - [FAQ](https://buildwithember.ai/faq): short answers - [Articles](https://buildwithember.ai/articles): why Ember works the way it does ## Articles - [Why we built Ember: from Cursor to Claude Code to our own editor](https://buildwithember.ai/articles/why-we-built-ember): We built Ember because we wanted Claude Code as the agent, on the subscription we already paid for, inside an editor that kept the habits we had built up elsewhere: Tab, Cmd+K, Keep and Undo, and many agents in parallel. No existing product gave us both, so we built it for ourselves and then kept going. - [One task, one branch, one pull request: how Ember organizes parallel agents](https://buildwithember.ai/articles/one-task-one-branch-one-pull-request): Ember gives every task its own branch and pull request, and puts parallel work in git worktrees, because that is the only arrangement we found where each change can be reviewed, tested by CI, reverted and merged by itself, and two agents never edit the same checkout. - [Cleanup never takes your work: a rule we wrote after losing a file](https://buildwithember.ai/articles/cleanup-never-takes-your-work): Ember's own cleanup removes a worktree only when everything in it is on its branch, and deletes a branch only when git shows its work landed. We wrote that rule after an automatic cleanup force-removed a closed worktree that still held a saved edit and an untracked file. - [Your agents, on your phone: why Ember's mobile app talks to your own computer](https://buildwithember.ai/articles/your-agents-on-your-phone): Ember's phone app connects to Ember running on your own computer, not to a cloud copy of your code. It shows what needs you, ranked, with one button each, and every tap is checked against the branch as it is at that moment. - [Your Claude subscription, not an API key: how Ember handles sign-in and permissions](https://buildwithember.ai/articles/your-subscription-not-an-api-key): Ember drives the claude CLI already signed in on your computer, so every chat runs on your Claude Pro or Max plan. Ember never asks for, reads or stores your Claude credentials, and it removes ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN from the agent's environment so a chat is never billed per token by mistake. ## Questions and answers ### Who is Ember for? Developers who know how to code and still want to. Ember is a full IDE, not a chat box that replaces one: you get a real editor with next-edit predictions and inline edit for the code you write yourself, a review tab where you keep or undo every change an agent makes, and git that stays yours. The agents do more of the typing; you stay the engineer. ### What is Ember? Ember is a desktop IDE built around Claude Code. It is a complete editor (built on VS Code's open-source base) with Claude's agent, a board of every branch your agents are working on, multi-agent plan builds, a review tab, next-edit predictions and a phone app. It runs on macOS, Windows and Linux. ### Do I need an API key to use Ember? No. Ember runs on your Claude Pro or Max subscription through the Claude Code CLI on your computer. It never asks for, reads or stores your Claude credentials, and it removes stray ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN variables from the agent's environment so a chat is never billed per token by accident. ### How is Ember different from Cursor? The agent in Ember is Claude Code itself, on your own Claude subscription, and your rules, skills, hooks and MCP servers are the plain files Claude Code already reads. Parallel work is organized around git: one task, one branch, one pull request, with a board that shows each branch's state and one next step. The habits carry over: agent chat with Plan and Ask, parallel agents, Tab, Cmd+K, and Keep or Undo per change. ### How is Ember different from the Claude Code extension for VS Code? The extension adds a Claude panel to an editor. Ember is a whole editor designed for running many Claude agents: a branches board and Dashboard, Bonfire plan builds with several agents at once, a review tab with Keep and Undo per hunk and Agent Review findings, next-edit Tab predictions, Cmd+K inline edit, a codebase index, live usage limits and a phone app. It uses the same Claude Code configuration, so the terminal, the extension and Ember all behave the same way. ### Can I control my coding agents from my phone? Yes. Ember has an installable phone app that connects to Ember on your own computer. It opens on Now: what needs you, ranked, each with one button. You can answer a question, approve a command, merge a pull request, remove a worktree, stop an agent or start a new chat. You choose how the phone reaches your computer: Tailscale, your local network, ngrok, a Cloudflare tunnel or your own URL. ### Does Ember work with my existing Claude Code setup? Yes. CLAUDE.md, skills, slash commands, hooks, subagents, plugins, MCP servers, permissions, output styles and statusLine all apply. What you set in Ember is the same file the claude CLI reads, and your CLI sessions show up in Ember. ### What is Bonfire? Bonfire builds a plan with several Claude agents at once. Each to-do in the plan says what it changes and what it waits for, so Bonfire knows which can run together. Each to-do gets its own worktree, chat, branch and pull request, a reviewer checks it, and dependent work either waits for its parent to merge or stacks on the parent's branch. ### Which platforms does Ember support? macOS on Apple Silicon (notarized), Windows on x64 and Arm64 (an installer that needs no admin rights, or a portable zip), and Linux on x64 and arm64 as .deb, .rpm or a tar.gz. ### Where does my code go when I use Ember? Your prompts and the code Claude reads go to Anthropic, or to whichever model provider you choose, exactly as they do when you use Claude Code in a terminal. Ember adds no server of its own in between and has no account to create. What Ember stores (chat history, search, memories, the codebase index and usage stats) is kept on your machine. The phone app talks to Ember on your computer; a public link passes through the tunnel provider you picked. ### Can Ember use models other than Claude? Yes. Besides your Claude subscription, Ember can use other subscriptions, any Anthropic-compatible gateway or API key, and local models on oMLX, Ollama or LM Studio for chat, Tab predictions and embeddings. Keys are kept in your operating system's keychain. ### How much does Ember cost? Ember is free to download. If it earns a place in your day, you can support its continued development for $5 from inside the app. You also need a Claude subscription (Pro or Max) and the Claude Code CLI signed in on your computer; Ember adds no usage charges of its own. ### Will an agent merge or force-push without asking me? No. Agents push their own branch and open their own pull request. A push, merge, rebase or pull request into a protected branch needs your words in the chat, hooks are never skipped, and commands that can't be undone always ask. Merges are yours unless you turn on auto-merge when green. ## How Ember compares - The agent: Ember: Claude Code itself, driven through the Claude Agent SDK. Cursor: Cursor's own agent, with Claude among its models. Claude Code extension for VS Code: Claude Code. - What you pay for: Ember: The Claude subscription you already have. No API key.. Cursor: A separate Cursor subscription. Claude Code extension for VS Code: Your Claude subscription. - Your Claude Code setup: Ember: All of it applies, each with a real settings UI. One configuration for the terminal and the editor.. Cursor: Its own rules and settings. Claude Code extension for VS Code: Applies; mostly edited as files. - Many agents at once: Ember: A board of every branch in every window: six states, one next step each, ranked by what it unblocks. Cursor: Parallel agents, listed by agent. Claude Code extension for VS Code: Several sessions, one panel each. - Multi-agent plan builds: Ember: Bonfire: a branch and PR per to-do, stacked PRs, merge order, a usage forecast, scheduled runs. Cursor: —. Claude Code extension for VS Code: —. - Review before it lands: Ember: Keep or Undo per hunk, file or everything; Agent Review findings under the line; Fix with Claude; Agent Blame. Cursor: Per-change accept and reject, with review tools. Claude Code extension for VS Code: Accept or reject each proposed edit. - Next-edit Tab predictions: Ember: Ember Tab, on a model you choose, local or hosted. Cursor: Cursor Tab. Claude Code extension for VS Code: —. - Inline edit (Cmd+K): Ember: In the editor and the terminal. Cursor: Yes. Claude Code extension for VS Code: —. - Your phone: Ember: An app for the agents on your own machine: answer, approve, merge, clean up, start a chat. Cursor: Cloud agents from the web and mobile. Claude Code extension for VS Code: Remote sessions through Claude's apps. - Usage you can see: Ember: Live 5-hour and weekly limits in the composer, Dashboard and status bar; a usage page by day, model, project and account. Cursor: Usage in account settings. Claude Code extension for VS Code: The /usage command. - Who sees your code: Ember: Anthropic, or the model provider you choose, as with Claude Code. Ember has no server of its own; its chat history, index and usage stats are stored on your machine.. Cursor: Cursor's service and its model providers, per your privacy settings. Claude Code extension for VS Code: Anthropic, as with Claude Code. ## Where Ember goes further than Cursor (compared against Cursor 3.28, November 2026) - Rewind brings back what commands changed, too. Cursor's checkpoints restore the files a chat's edit tools touched. Ember also snapshots the folder at each turn, so files changed by a command, a script or a code generator come back as well, and the conversation rewinds in place with your message back in the box. - Review everything a chat changed, not only what's pending. Once you've kept part of a chat's work, most tools give you nowhere to see the whole of it. Ember's review tab has an Everything view: one net diff per file from before the chat's first edit to now, with other people's lines marked, built from Ember's own turn snapshots instead of a git range. - A commit settles only the changes it actually carries. When you commit, Ember marks an agent's edit as kept only if the commit holds that edit byte for byte, after any commit, merge or reset, and it checks again at startup. A change the commit didn't include stays pending for you to review. - Automatic cleanup never force-removes your work. Ember's own cleanup keeps any worktree with uncommitted, untracked or detached work and tells you why. A branch is deleted only when git shows its work landed. Removing a worktree that still holds work is something only you do, after Ember names what goes. - Old chats clean themselves up, if you want. Chats in other editors live until you delete them one by one. Ember can delete chats older than a number of days on a schedule, across every worktree folder, and pinned chats are never deleted. - Agent Review checks the change against what you asked. Check for bugs looks for bugs and also compares the change with what you typed. Something you asked for that is missing shows as "Asked for, not done". A finding you set aside isn't raised again while its code is unchanged, and a separate pass looks only for security problems. - Tab predictions on a model you choose, with related files. Ember Tab runs on your own model, locally if you like, and sees excerpts of the files this one imports and the files you just edited. It never sends keys or certificates. - Embeddings from the endpoint you pick. The codebase index uses the embeddings endpoint you choose, a local one included, and keeps every repository and worktree current. ## What Ember adds around Claude Code, beyond the Claude Code extension ### Seeing many agents at once - A Dashboard sorted by whose move it is, aware of every tab and of work started from the CLI - The branches board: six states, one next step per branch, a Tree view and the merge order for stacked PRs - Workspace tabs for several repositories and worktrees, each with a state dot and a PR chip that follows GitHub within seconds - A chat list grouped by repository, worktree and branch, with search by ticket key, PR number or branch ### Building and shipping - Bonfire: one plan built by several agents, a branch and pull request per to-do, stacked dependencies, a usage forecast and scheduled runs - A Where menu on every new chat, and a chat that moves into a worktree carries on in that worktree's tab - Open PR with your pre-PR check, Bring changes here as a squash merge, and Babysit to fix checks and review comments until green - Issues from GitHub and Jira in one table, each with its branch, chat and PR, and opt-in tracker sync - Compare: one prompt on two to four models, each on its own branch, side by side ### Reviewing - A review tab with Keep or Undo per hunk, per file or all of it, and an Everything view of a chat's whole change - Agent Review findings under the lines they're about, Fix with Claude, a security pass, and dismissals that stick - Agent Blame: which chat wrote each line, with a way back to that chat - Rewind to any message with your files put back, including what commands changed ### The editor - Ember Tab next-edit predictions and Cmd+K inline edit, in the editor and the terminal - A codebase index with hybrid search and a codebase_search tool for Claude - Forge: staging by file, hunk or line, drafted commit messages, history with the branch graph - A browser Claude can drive, with visual checks against a baseline, and canvases that keep their state ### Staying in control - Safe commands run by themselves; commands that can't be undone always ask, and the safety checks fail closed - Protected branches: a push, merge or rebase into one needs your words in the chat - A settings UI for permission rules, hooks, skills, commands, agents, plugins and MCP servers, written to the files the CLI reads - The context ring lists everything Ember adds to a chat, by name and size ### Limits, accounts and long chats - Live 5-hour and weekly limits in the composer, the Dashboard and the status bar - A usage page by day, hour, model, project and account, including what a change to your setup saved - More than one Claude account: choose per folder, window or chat, and what happens when one runs low - A long chat offers to hand over to a fresh one, with a note it writes itself ### Away from the desk - A phone app and an iPad layout for the agents on your own machine: answer, approve, merge, clean up, start a chat - Notifications written by Claude Haiku from the chat's own facts, on your subscription - Voice: Ember says by name which chat needs you, and you answer into that chat