A near agentic workflow to help you ship better.

Describe what you want to build or fix. Cadre brings together a researcher, planner, designer, implementer and reviewer to work through it. Follow their progress, answer questions and review the pull request.

Download for Mac

For macOS 13 or later. On an Intel Mac? Download for Intel. Windows and Linux are on the way.

Add passkey sign-in auth-service Working 4m 34s
Add passkey sign-in to the auth service, and keep password login as a fallback.
ChiefSonnet 5.5 · medium

A new sign-in method that touches the session store. Research first, then a plan and a design before anything is built.

Handed off to Researcher Map every path into the session store…
ResearcherSonnet 5.5 · medium
Took 52s ›

Sign-in goes through two routes, both ending in createSession().

PrincipalOpus 5.5 · high
Needs you
Should passkeys sync across devices?
1Yes, store them per account 2No, keep each one on its device
ImplementerGPT-5.6 Terra · medium
Asked Principal Should a failed passkey fall back to the password form? Yes, after one retry.
Took 1m 46s ›

42 tests pass. Password login is untouched.

ReviewerSonnet 5.5 · high

Round 1: the sign-in challenge never expires, so an old one could be replayed.

Sent back to Implementer Expire each challenge after 5 minutes…
ImplementerGPT-5.6 Terra · medium
Took 38s ›

Challenges now expire after 5 minutes. 44 tests pass.

ReviewerSonnet 5.5 · high

Round 2: approved. A new test covers the expired challenge.

ChiefSonnet 5.5 · medium
Took 4m 34s ›

Passkey sign-in is ready, synced per account, with password login kept as the fallback. Review caught a replayable challenge; it now expires after 5 minutes. The pull request is yours to review.

Add passkey sign-inauth-service#142 · feat/passkey-sign-in → main Open ↗
Working · 4m 34s
This run$2.73
56.9k tokens · 4m 34s · 91% from cache
  • Implementer$1.02
  • Principal$0.61
  • Reviewer$0.52
  • Researcher$0.29
  • Chief$0.18
  • Planner$0.11
Local checkout feat/passkey-sign-in
Message the room. Type @ to reach a role…
+ Sonnet 5.5 ⌄ Medium ⌄ to Chief ⌄ ↑
  1. It asks when the call is yours

    The Principal stops to ask whether passkeys should sync. Answer it, or turn on Auto and let the agents decide.

  2. Agents check with each other

    Instead of guessing, the Implementer asks the Principal how a failed passkey should fall back.

  3. A separate reviewer reads every change

    Round one finds a sign-in challenge that never expires and sends the work back with the fix it wants.

  4. You see what it costs

    Cost, tokens and time for the whole run and for each agent, as the work happens.

  5. You get the pull request

    Reviewed, tested and assigned to you. Nothing merges until you merge it.

Works with the coding agent you already use

How your task gets done

The Chief reads your request and routes it to the agents it needs. A small fix can go straight to coding and review. A new feature may need research and a design first. Agents can ask each other questions or send work back for changes.

›You
Chief
Researcher
Conductor
Planner
Principal
Analyst
Implementer
Reviewer
⇡Pull request
Hands off Asks a colleague Sends it back

Yours to steer

Every action has a shortcut and a place in the command palette. Press ⌘K anywhere on this page, or try it here.

Session
New run…⌘N
Resume workspace⇧⌘R
Settings⌘,
Role
Message reviewer…⌘M
Go to principal, waiting for me⌘J
Open chief⌘1
Attach files…⌘U
Pipeline
Answer principal's question⇧⌘Y
Hand off to…⌥⌘H
Run
Show the agents⌥⌘J
Open Pull requests⌥⇧⌘P
Panel
Show the Changes tab⌥⌘4
Show the Terminal tab⌥⌘1

Download Cadre for Mac

Open a repository, choose your coding agent and start a task.

Download for Mac

On an Intel Mac? Download for Intel

You'll need Claude Code, Codex or Cursor's agent installed and signed in, and the GitHub CLI for pull requests.

Before you get started

What do I need to use Cadre?

You'll need a Mac with Apple silicon and Claude Code, Codex or Cursor's agent installed and signed in. Cadre uses the agent you choose with your existing plan or API key. Install the GitHub CLI and sign in to let agents open pull requests.

How is this different from using my coding agent directly?

Cadre's built-in specialist roles have separate responsibilities for research, planning, design, implementation and review. Each has its own conversation and instructions. They share their findings and ask each other questions, and a separate reviewer checks the code before you review the pull request.

Which coding agents does it work with?

Claude Code, Codex and Cursor's agent. Cursor support is newer and may have rough edges.

Does my code leave my Mac?

Yes, if your coding agent sends code and prompts to its provider. Cadre runs agents in your local checkout, using the coding agent you choose. Your provider's data policies still apply.

Can I step in while a run is working?

Yes. Message the Chief agent, or type @ to address another agent. You can also pause the run, answer questions or open an agent's terminal to work with it directly.

Will it merge anything on its own?

No. Completed changes become a pull request assigned to you. You decide whether to merge it.

When are Windows and Linux coming?

Both are in development. The current release is for Macs with Apple silicon.