[ Meet Macaron ]

AI,in every flavor.

Work on code or clean up a draft. Macaron brings tools for creating, transforming, and checking your work into one place.

One Macaron · Different flavors

The Macaron desktop app asking “What should we work on?”, with the project running in its own computer that can't touch your Mac

A codebase

Checks · after the agent's turn

  • test✓ Passed
  • lint✓ Fixed
  • typecheck◐ Running

Claude Code or Codex changes it in a computer of its own. Checks run before you keep anything.

A draft

In today's fast-paced world, our team leverages synergy to ship.

✓ Fixed Our team works together to ship.

Formulaic phrasing gets flagged. You choose which fixes to keep.

[ Choose a task ]

What do you want to do?

Start with code or a draft. Each task has a place in Macaron.

Available on desktop and web

Describe the change you want.

Bring a repository and describe the change. Work with your coding agents, review the diff, and keep the changes that pass your checks.

Try a task like

Fix the checkout test. Then clean up the generated code.

Start coding
[ Work where it suits you ]

On your desktop or in your browser.

Start Code on your own machine or in the web app. Check and clean up prose in your browser. Deeper model rewrites are still in testing.

Now running

Fix the checkout test

Checks 2 of 3 passed

macaron/site2m ago

In your browser

Macaron app

Start agents on machines of their own, keep your keys encrypted, and read each run's receipt and diff, all in one place.

Macaron's agent list: Claude Code, Codex, OpenCode and Droid, each with a Run button

On your desktop

Macaron

The harness for the agents you already use. Claude Code, Codex and more run in computers of their own, and every turn is checked and can be undone.

Stop.
Start.
Copy.

  • Local
  • Cloud

On a machine of its own

Local or cloud

Each agent gets its own Linux machine. Stop it when you're done, start it again when you need it, or copy it to try something risky.

[ Try the Code flavor ]

Have Macaron fix the flaky checkout test in your repository and

Say it the way you'd say it to a person. Macaron works in its own machine, runs your checks, and hands back a change you can read line by line before you keep it.

3 blanks · about 30 seconds

Run-00847macaron/site

Fix the checkout test

2 checks passed

Review the diff
Undo a turn
4Agents, one harness
Checked before it counts
  • Checks before and after
  • A machine of its own
  • Every turn can be undone

Macaron runs the agents you already use on a machine of their own, checks every turn, and hands back a receipt. From the first sentence to the change you keep.

OverviewNew run

Good evening, maya

What's running, what finished, and what you can pick up next.

Machines running

2 of 3

Credit

$48.20

Active runs

1

Runs this week

9

Recent runs All runs

  • Fix the flaky checkout testmacaron/site · claude-sonnet-5-5 · complete4m ago
  • Add rate limiting to loginmacaron/api · claude-opus-5-5 · runningjust now
  • Upgrade to React 20macaron/web · claude-sonnet-5-5 · complete2h ago
  • Remove narrating commentsmacaron/site · claude-sonnet-5-5 · complete1d ago

Activity All activity

  • MMacaron finished Fix the flaky checkout test
  • mmaya ran bun test checkout
  • mmaya saved src/cart.ts
  • mmaya started Add rate limiting to login
[ Inside the Code flavor ]

From one sentence to a change you trust.

For coding work, Macaron keeps the checks, review, and receipt together.

  1. Macaron's composer: What should we work on? with the agent, model and effort pickers

    01Describe

    Say it the way you would to a teammate

  2. Macaron's checks list: test passed, lint failed with two findings, typecheck stopped, each with a Rerun button

    02Check

    Your checks run before and after the agent

  3. Macaron's computer setup: choose Local or Cloud, then name, host, user and size

    03Keep or let go

    Stop the machine, start it again, or copy it

A receipt
you can read.

Run-00847

What changed
The checkout test now waits for the cart request instead of a fixed delay. Nothing else in the repository was touched.
Checks
test passed before and after. lint passed. Not verified: the payment sandbox.
Reviewer
Still reading the diff.

macaron/site · checkout.spec.ts:41bun test checkout

An example run. Yours is built from what actually ran.

  • Checks before and after
  • Files that changed
  • What nobody verified
[ Start with Code ]

The work you'd rather hand off.

Bring your own keys and pick the model per task. Macaron keeps the rest the same: the machine, the checks, the review and the receipt.

Fix a failing test

Fix the cause, not the test.

The clearest job you can hand an agent: it's done when the test passes and nothing else breaks. Macaron is told to fix the cause, never loosen the test.

  • Your checks run before and after
  • Tests are never weakened to pass
  • A diff to read before you keep it

AI is brighter than it seems.

The way you work with it matters. Macaron brings different ways of creating, transforming, and checking your work under one roof. Start with a task. Find the flavor that fits. Keep the result you want.

More flavors are in development: Patois for deeper prose rewrites, Write, and Research. We’re building toward a workspace that carries your files, context, and history between flavors. That shared workflow is still ahead.