TOMRADE

喵喵,喵喵 MEOW MEOW

For solo makers and small teams who build with coding agents, and for keeping everyday life in order too

From idea to merged PR, with the agents you already use.

Your agents write the code. Tomrade remembers what to build, how far it got and what changed, so every session picks up where the last one stopped, and any run can be undone in one click.

🐟 Find it useful? Treat the cat to a snack →

How it works

Talk, split, build, merge.

One loop from an idea to a merged pull request. Each step below is filmed in the app as it is.

  1. 01Talk

    Say what you want in plain words, at your desk or from your phone. It becomes a ticket on the board, ready to start.

  2. 02Split

    Say “tidy up” and the assistant merges duplicates and splits the big ones into tickets sized for one pull request. You pick; one click takes it back.

  3. 03Build

    Press Start on a ticket, or name it to Claude Code, Codex or another agent in your own terminal. It claims it, works on its own branch and reports back.

  4. 04Merge

    Leave the rest to an auto run: it works down the dependency graph overnight, merges each pull request whose checks pass if you let it, and writes you a report by morning. Failed checks and review comments go back to the agent.

Watch it

One day, start to finish.

An idea in the afternoon, agents with questions, a run through the night and a report by morning, filmed in the app as it is, nothing staged.

A day with Tomrade · 1:27

  • Who's waiting on you

    Answer every agent from one sidebar.

  • Files, notes and diagrams

    Linked notes, and an architecture diagram drawn from your code.

  • An inbox that sorts itself

    Issues come in, get triaged, and ship.

  • Take over half-done work

    Point it at a repo; it finds the branches you forgot.

  • Everything is a plugin

    A pet, a timer, models, themes, and the plugin it writes for you.

Every film is the real app on a demo repository, with agents running on Claude Code. Captions are in English and Chinese.

Why Tomrade

What your agents don't keep for you.

  1. Every session starts from zero.

    A backlog that lasts

    Ideas, tickets, decisions and what's already done stay in one place across sessions and agents, so the next run starts where the last one stopped.

  2. Another tool, another window to babysit.

    Keep the tools you have

    Claude Code, Codex or Cursor stay in the terminal you already use. Tomrade connects over MCP and git, and the board keeps up on its own.

  3. Something changed. Who did it?

    See it, undo it

    Every agent write is attributed and grouped by run. One click takes a whole run back: tickets, notes and settings alike.

Also in the box

  • Your agents

    Work where you like. Tomrade keeps track.

  • Terminal

    The terminal, right next to the board.

  • Undo, not approve

    No approval queue. Just undo.

  • The assistant

    Ask it about anything in Tomrade.

  • Built-in plugins

    Draw it in one sentence.

  • One workspace

    Not just for code.

  • IM

    Message it from your phone

  • Ways to play

    Work is serious. Tomrade doesn't have to be.

Agents

Plug in the agents you already use

  • Claude Code
  • Codex
  • Cursor
  • Gemini CLI
  • OpenCode
  • Pi
  • WorkBuddy

FAQ

Questions

Is Tomrade only for programmers?

No. The board, the assistant and Files work for any project: a household, a trip, a thesis, a journal. Coding agents join in when a project has a repository and stay out of the way when it doesn't.

I already use Orca, Cursor or another agent tool. Do I still need Tomrade?

They do different jobs, and they work together. Tools like those run your agents and help you review their code; Tomrade keeps what the agents should work on, how far each piece got and what changed. Keep running agents where you like: they connect to Tomrade over MCP and git, claim tickets, and the board follows their branches and pull requests.

How far back can undo go?

Every write Tomrade makes or lets an agent make: tickets, files and notes in Files, and settings. Revert an assistant run in one click, or roll History back to any point. A permanent delete is the one thing you can't take back. It doesn't reach outside Tomrade: commits, branches and pull requests in your repository stay with git, where you revert them the usual way.

Do I need GitHub?

No. A local git repository is enough: name a ticket in a branch or a commit and the ticket follows it. Opening and merging pull requests from Tomrade uses GitHub today, and Files can sync to a GitHub repository if you want; neither is required.

Is Tomrade ready for everyday use?

It's a preview. Until 1.0, Tomrade is in development and testing: features change between versions, and you will hit rough edges. Your projects are plain folders on your own machine, so back up the ones that matter.

Is Tomrade open source?

Yes. Tomrade is licensed under the Apache License 2.0, an OSI-approved open-source license, for the app, every package and the plugin SDK alike. You can use, change and redistribute it, commercially too. The source is on GitHub.

How Tomrade fits with Orca, Cursor and other agent tools →

Ship more. Approve less.

Free to use and open source under Apache 2.0. Your projects stay in your own folders.

🐟 Find it useful? Treat the cat to a snack →