Macaron vs Claude Code
Claude Code is Anthropic's agent, on nearly every surface you work in. Macaron isn't a rival so much as a place to run it: on a machine of its own, with your checks around every turn.
Updated October 1, 2026 · Other products described as of October 1, 2026
Short answer. If you want one agent everywhere, from your IDE to your phone to Slack, use Claude Code directly. If you want to run Claude Code where it can't touch your Mac, see each turn as a diff with a git-backed undo, and have your own checks run before and after, run it inside Macaron.
At a glance
- What it is
- Claude CodeAnthropic's coding agent
- MacaronA workspace that runs Claude Code, Codex or its own agent
- Where you use it
- Claude CodeTerminal, desktop app, VS Code, JetBrains, web, iOS and Android, Slack, GitHub Actions
- MacaronA desktop app, the macaron CLI, and a web app at macaron.sh/app
- Where code runs
- Claude CodeYour machine, or Anthropic's cloud for web sessions and routines
- MacaronA folder on your Mac, or a Computer: an isolated Linux machine per agent, in Docker on your Mac or in the cloud
- Approving changes
- Claude CodeAsks before it edits files or runs commands
- MacaronClaude Code's own prompts, plus the Computer's isolation and connectors you switch on
- Undo
- Claude Code/rewind restores edits made by its file tools; not changes made by shell commands
- MacaronEach turn is a git checkpoint, so shell changes are covered too
- Checking the work
- Claude CodeRuns your tests when asked; hooks can run scripts around actions
- MacaronYour test, lint and typecheck scripts, before and after; AI end-to-end tests with macaron e2e; an optional second-model reviewer
- Pull requests
- Claude CodeOpens them; GitHub Code Review and GitLab CI
- MacaronLists and creates pull requests through the GitHub CLI
- Paying for it
- Claude CodeA Claude Pro or Max plan, or API tokens
- MacaronYour Claude plan or key, plus Macaron's own plan
| Claude Code | Macaron | |
|---|---|---|
| What it is | Anthropic's coding agent | A workspace that runs Claude Code, Codex or its own agent |
| Where you use it | Terminal, desktop app, VS Code, JetBrains, web, iOS and Android, Slack, GitHub Actions | A desktop app, the macaron CLI, and a web app at macaron.sh/app |
| Where code runs | Your machine, or Anthropic's cloud for web sessions and routines | A folder on your Mac, or a Computer: an isolated Linux machine per agent, in Docker on your Mac or in the cloud |
| Approving changes | Asks before it edits files or runs commands | Claude Code's own prompts, plus the Computer's isolation and connectors you switch on |
| Undo | /rewind restores edits made by its file tools; not changes made by shell commands | Each turn is a git checkpoint, so shell changes are covered too |
| Checking the work | Runs your tests when asked; hooks can run scripts around actions | Your test, lint and typecheck scripts, before and after; AI end-to-end tests with macaron e2e; an optional second-model reviewer |
| Pull requests | Opens them; GitHub Code Review and GitLab CI | Lists and creates pull requests through the GitHub CLI |
| Paying for it | A Claude Pro or Max plan, or API tokens | Your Claude plan or key, plus Macaron's own plan |
How each works day to day
With Claude Code you start a session where you are, in a terminal or IDE, on the web or from your phone, and it reads your code, edits and runs commands, asking first. CLAUDE.md, skills, hooks and MCP servers shape how it works, and routines run it on a schedule in the cloud.
In Macaron you start the same Claude Code inside a project, either in a folder on your Mac or on a Computer. Your CLAUDE.md and plugins still apply. What Macaron adds is around the agent: a card per turn with the files changed and an undo, Review for the diff, your checks before and after, a preview of the app it's serving on port 3000, 5173 or 8080, and a board of all your threads.
Where code runs and what it can touch
Run locally, Claude Code works on your machine with your user's access, and its permission prompts are the guard. Web sessions and routines run in Anthropic's cloud. Anthropic also describes self-hosted environments inside your own network for enterprise.
Inside a Macaron Computer, Claude Code runs on a Linux machine that can't see your Mac's files, SSH keys or browser sessions. A sandbox copy lets it work on a copy of a Mac folder, and Apply to Mac brings the result back only if it applies cleanly.
Undo, compared
Claude Code's checkpoints capture the state before each prompt, and /rewind can restore code, conversation or both. Its docs are clear about the limits: files changed by shell commands such as rm or mv aren't tracked, most subagent edits aren't restored, and checkpoints aren't a replacement for version control.
Macaron's undo works at the git level, per turn, so it covers whatever the agent changed in the working tree, however it changed it. Files outside the repository aren't covered.
Models and pricing
Claude plans as published on claude.com/product/claude-code on October 1, 2026.
- Pro
- Price$17 a month billed annually, or $20 monthly
- Claude CodeIncluded
- Max 5x
- Price$100 a month
- Claude CodeIncluded
- Max 20x
- Price$200 a month
- Claude CodeIncluded
- API
- PricePer token
- Claude CodePay as you go
| Claude plan | Price | Claude Code |
|---|---|---|
| Pro | $17 a month billed annually, or $20 monthly | Included |
| Max 5x | $100 a month | Included |
| Max 20x | $200 a month | Included |
| API | Per token | Pay as you go |
Inside Macaron, Claude Code uses the same plan or key; Macaron doesn't resell tokens. You can also point it at Bedrock or Vertex. Macaron's own plan covers the app and cloud machine hours.
Who should pick which
- You want to start a fix from your phone, or from a Slack thread: Claude Code directly.
- You want Claude Code to work on a repository you don't fully trust, without access to your Mac: Claude Code inside a Macaron Computer.
- You switch between Claude Code and Codex on the same project: Macaron runs both.
- Your team reviews in GitHub and wants automatic review on every pull request: Claude Code's GitHub Code Review.
What Macaron doesn't do
No Slack integration, no mobile app, no hosted SLA, no multiplayer, and no visual browser testing of its own beyond the AI end-to-end tests. It doesn't replace Claude Code's IDE extensions, mobile apps or cloud routines.
Questions
Does Macaron use Claude?+
Yes. It runs Claude Code itself, and Macaron's own agent can run on Anthropic models through your key, Bedrock or Vertex.
Do I need a separate Claude subscription?+
You need some way to pay Anthropic: a Claude plan or an API key. Macaron uses yours and adds no markup on tokens.
Will my CLAUDE.md, skills and plugins still work?+
Yes. Macaron starts the real Claude Code CLI in your project, so its own configuration applies. Macaron's settings can manage Claude Code plugins for a project.
Is Macaron's undo the same as /rewind?+
No. /rewind restores edits from Claude Code's file tools. Macaron's undo restores the repository to a git checkpoint taken at the start of the turn, which also covers changes made by shell commands.
Can Claude Code open pull requests in Macaron?+
Yes. Claude Code can run git and gh itself, and Macaron can list and create pull requests through the GitHub CLI.
Why not just run Claude Code in Docker myself?+
You can. Macaron does that setup for you, plus sandbox copies, Apply to Mac, port previews, connectors and the checks around each turn.
Sources and dates
- claude.com/product/claude-codeclaude.com, read October 1, 2026
- Claude Code docs: overviewcode.claude.com, read October 1, 2026
- Claude Code docs: checkpointingcode.claude.com, read October 1, 2026
Facts about other products come only from these pages, on the dates shown; prices are as published that day. Macaron's own details are as shipped on October 1, 2026. Products change, so check their sites for the latest.