Raticode

Appearance

New Raticode 0.5.3 is out

Build the maze.
Let the agents run it.

Raticode turns the coding work you keep re-prompting into workflows. Wire shell commands, scripts, HTTP calls and AI agents together with real branches, loops and reviews. Design them with Rem, run them on your machine, and wake up to finished work.

Download Raticode Read the docs

macOS · Windows · Linux · CLIOpen sourceNo account requiredMobile coming soon

Bring the agents you already pay for

  • Claude Code
  • Codex
  • Cursor
  • GitHub Copilot
  • OpenCode
  • Antigravity
  • Grok
  • OpenAI API
  • Anthropic API
The problem

You became the glue code in your own AI workflow.

01 · Groundhog prompts

You type the same instructions every day.

Run the tests. Fix what broke. Summarize the diff. Open the PR. Your agent is brilliant, but your process lives in your clipboard.

02 · Context bloat

One endless chat carries everything.

Every step drags the whole conversation along. Answers drift, tool calls pile up, and the bill grows with the scrollback.

03 · Black-box runs

When it goes sideways, you start over.

There is no step to inspect, no failure to route around, no way to rerun just the part that went wrong.

Raticode turns that loop into a machine you can see. Each step becomes a node with its own prompt, model and limits. Routes decide what happens next. Your agents do the work; you review the result.

How it works

From a sentence to a repeatable machine.

  1. 01

    Describe it

    Tell Rem what you want done. Rem drafts the workflow in Rattish, a small language you can read in one sitting, and checks it before you run anything.

  2. 02

    See it

    Every workflow is a graph. Wire routes, joins, branches, loops and review cycles on the canvas. The graph and its source stay in sync.

  3. 03

    Run it anywhere

    Run from the studio, on a cron schedule, when files change, from a local webhook, or headless with the Raticode CLI on any machine. Every run keeps a snapshot you can inspect.

One workflow, two views

Readable source. Visible graph.

Workflows are plain text you can diff, review and commit. The studio draws the same file as a live graph. Hover a node to see where it lives in the source.

.raticode/fix-failing-tests/workflow.rattish✓ check passed
1rattish: 123workflow:4  name: Fix failing tests5  max-runs: 2467node run-tests:8  type: bash-command9  start: true10  allow-fail: true11  command: npm test12  to:13    - fix when failed14    - open-pr otherwise1516node fix:17  type: agent18  provider: claude-code19  prompt: |20    Run npm test, find the root cause of each failure and fix it.21    Keep the diff small.22  to: review2324node review:25  type: agent26  provider: codex27  prompt: Review the diff. Approve only if it fixes the cause.28  output-schema: {"properties": {"approved": {"type": "boolean"}}, "required": ["approved"], "type": "object"}29  to:30    - run-tests when node.review.output.approved31    - fix otherwise3233node open-pr:34  type: bash-command35  command: gh pr create --fill36  needs: run-tests37  finish: pass
when failedotherwiseapprovedotherwise$run-testsbash · npm testrun-tests — Succeeded✦fixagent · Claude Codefix — Succeeded✦reviewagent · Codexreview — Succeeded$open-prbash · gh pr createopen-pr — Succeeded

Try it. Hover or tab to a node. Two agents, two providers, one review loop, capped at 24 runs.

Inside the studio

Everything your agents need. Nothing they don't.

A complete coding workspace built around one idea: small, focused agent steps beat one enormous conversation.

Rem

Switch models. Keep the thread.

Rem is the coding agent that lives in Raticode. Move a conversation from Claude Code to Codex mid-task. The history, project scope and resources stay with the thread.

Control flow

Branches, joins and cycles

Route on failure, on typed output, or otherwise. Wait for several steps with needs. Cap loops with max-runs.

Fan-out

One step, many runs

Loop an agent over a count, the rows of a spreadsheet or every file in a folder, with a concurrency limit you choose.

Automation

Runs while you sleep

Cron schedules, file changes and local webhooks start workflows while Raticode or its background scheduler runs.

Workspace

A real place to code

Files, editor, terminal, Git history, worktrees and a built-in browser sit next to your agent.

Swarms · Experimental

A team of agents

Split a job into tasks, give each agent its own workspace, then review what came back.

Second Brain · Experimental

Knowledge that sticks

Point Rem at a notes folder. It searches what you know and saves reports back as notes.

Headless

The same engine, no UI

Ship workflows to a server and run them with the standalone Raticode CLI on Linux, macOS or Windows.

Local by design

Your machine.
Your keys.
Your rules.

Raticode is a desktop app and an open-source CLI, not a hosted service. Each agent step gets its own prompt and the inputs you wire into it, and you choose how much earlier context it keeps.

  • No account. No login.

    Install it and start. There is nothing to sign up for.

  • No Raticode cloud

    Workflows, threads and run history live on your machine. There is no Raticode server in the middle.

  • Secrets stay out of source

    Workflows refer to secrets by name, so keys never land in the files you commit.

  • Your providers, your terms

    Agents run through the subscriptions and API keys you already have, under your own accounts.

Download

Start building tonight.

Raticode 0.5.3 · released November 11, 2026 · release notes

Coming soon

Raticode Mobile

Talk to Rem, follow tasks and threads, read files and Git history, and run workflows from your Android phone while your computer does the work. It's in testing and not published yet.

Watch releases on GitHub

Looking for an older build? Browse all releases →

Let the agents
run the maze.

Rem is waiting. Your first workflow is one sentence away.

Download Raticode Read the docs