Ember, Cursor and the Claude Code extension

Ember is a desktop IDE where the agent is Claude Code itself, on your own Claude subscription. Compared with Cursor, you keep Tab, Cmd+K and parallel agents but drop the second subscription and keep your Claude Code setup. Compared with the Claude Code extension for VS Code, you get a full editor built for running many agents: a branches board, multi-agent plan builds, a review tab and a phone app.

Ember compared with Cursor and the Claude Code extension for VS Code
EmberCursorClaude Code extension for VS Code
The agentWhat actually does the work✓ Claude Code itself, driven through the Claude Agent SDK◐ Cursor's own agent, with Claude among its models✓ Claude Code
What you pay for✓ The Claude subscription you already have. No API key.— A separate Cursor subscription✓ Your Claude subscription
Your Claude Code setupCLAUDE.md, skills, hooks, subagents, plugins, MCP, permissions✓ All of it applies, each with a real settings UI. One configuration for the terminal and the editor.— Its own rules and settings✓ Applies; mostly edited as files
Many agents at onceKnowing which branch is where and what it waits for✓ A board of every branch in every window: six states, one next step each, ranked by what it unblocks◐ Parallel agents, listed by agent◐ Several sessions, one panel each
Multi-agent plan buildsOne plan, several agents, dependencies respected✓ Bonfire: a branch and PR per to-do, stacked PRs, merge order, a usage forecast, scheduled runs— —
Review before it lands✓ Keep or Undo per hunk, file or everything; Agent Review findings under the line; Fix with Claude; Agent Blame✓ Per-change accept and reject, with review tools◐ Accept or reject each proposed edit
Next-edit Tab predictions✓ Ember Tab, on a model you choose, local or hosted✓ Cursor Tab—
Inline edit (Cmd+K)✓ In the editor and the terminal✓ Yes—
Your phone✓ An app for the agents on your own machine: answer, approve, merge, clean up, start a chat◐ Cloud agents from the web and mobile◐ Remote sessions through Claude's apps
Usage you can see✓ Live 5-hour and weekly limits in the composer, Dashboard and status bar; a usage page by day, model, project and account◐ Usage in account settings◐ The /usage command
Who sees your codeBesides you✓ 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's service and its model providers, per your privacy settings✓ Anthropic, as with Claude Code

Based on our own use of each product and their public documentation, as of November 2026. Products change; if something here is out of date, tell us and we'll fix it.

Ember and Cursor, side by side

Where Ember goes further than Cursor

We used Cursor every day before we built Ember, and we compared the two feature by feature against Cursor 3.28 in November 2026. These are the places where Ember does the same job more carefully, or does one Cursor doesn't.

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.

Ember and the Claude Code extension

What Ember adds around Claude Code

The extension puts Claude Code's chat in an editor panel. Everything below is Ember's own work: none of it comes from Claude Code or its extension, and all of it shipped in one of Ember's 240-plus merged pull requests.

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

If you're coming from Cursor

Your habits carry over: agent chat with Plan and Ask, parallel agents, Tab, Cmd+K, Keep and Undo, rules and a codebase index. Ember imports your settings, keyboard shortcuts, snippets, extensions and other editors' rule files.

What changes is underneath. The agent is Claude Code on your own subscription, your rules and skills are plain files you own, and parallel work is organized around branches and pull requests, so it fits the way your team already ships.

If you use the Claude Code extension

Nothing about your setup changes. CLAUDE.md, skills, hooks, subagents, plugins, MCP servers and permissions all apply, and your CLI sessions show up in Ember.

What you gain is the editor around the agent: next-edit predictions, inline edit, hunk-by-hunk review with Agent Review, a board of every branch in flight, Bonfire plan builds, live usage limits and a phone app.

Download Ember