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

Tom + comrade

Comrade, not foreman.

Work where you like. Tomrade keeps track.

Other tools want the work done inside them, or only ever hand it out. Tomrade goes both ways. Set it up once, keep working in the Claude Code or Codex you've already tuned, in your own terminal, and the status finds its way back to the board.

• Any agent that speaks MCP: Claude Code, Codex, Cursor, Gemini CLI, OpenCode and the rest.
• Git keeps score. Name TOM-42 in a branch or a commit, and the ticket follows it to Doing, Verifying and Done.
• One command brings a session back: /tomrade:sync in Claude Code, $tomrade-sync in Codex.
• Never required. Work with no ticket stays yours, and nothing asks you to file one first.

Both directions work: press Start to hand a ticket out, or work on your own and sync it back. Connect a repository once, and Tomrade opens a pull request with the MCP config and agent notes, so every agent that works in it finds Tomrade.

Terminal

Alt-Tab cardio: cancelled.

The terminal, right next to the board.

Run Claude Code, Codex or a plain shell in Tomrade's own Terminal window, one click from the backlog. Split it however you like, let each pane connect to its ticket, and see at a glance which agent is working and which one is waiting on you.

• Split it your way: ⌘D to the right, ⇧⌘D down. Save a layout you like and open every new window with it.
• Sessions connect on their own. Start a ticket and it opens in a pane; when an agent in a plain terminal claims a ticket, that pane becomes its session.
• See who needs you. Each pane's bar and the sidebar say Running, Needs you or Idle, and Continue nudges a session on without leaving the window.
• Nothing gets lost. Quit Tomrade and your agents keep working; restart herdr and the layout comes back, every agent resuming its conversation.

Sessions

Six agents, one place to ask you things.

One conversation, every ticket in its place.

A single agent conversation can carry a whole afternoon: three tickets, a question, a fix. Tomrade marks where each ticket begins, shows the same session in the assistant panel and in its Terminal window cell, and keeps the ones waiting on you at the top.

Drawn in Matcha, one of the built-in themes.

• Chapters, not a scroll. When an agent claims a ticket, a line marks where that ticket's work starts, and its commands and test runs fold into one: Ran 18 commands · 79 tests passed.
• One pane, two windows. A session in a Terminal window cell also opens in the assistant panel. Type, allow or answer on either side; the other side shows it, and says where it came from.
• Who needs you comes first. The session bar filters by waiting, running and ended, and says what a session waits for in plain words: “wants to run git push”. Allow it right there, or from the menu bar.
• Look back by ticket. An ended session leads with its outcome, its conversation filters by ticket, and each pane keeps a timeline, including what you did by hand between sessions.

Files & notes

A notebook that lives next to your board.

Each project carries a folder of files: Markdown, HTML, images, anything. Write in an editor that previews as you type, link notes to each other, and attach them to tickets as deliverables.

1# 2026-10-102Shipped the sunrise on the login screen. #tomrade3Notes for [[Promo site]]:4- Say it's not just for code5- Move the cat after the plugins6- Let people bring their own pet

• [[Wiki links]] and backlinks. Rename a note and the links follow.
• #tags and full-text search across every file.
• Today's note: one click to a dated page in your journal.
• Read, Edit or Split, with the preview scrolling in step.
• Every save is versioned. Sync to a GitHub repo of your choice.
• Attach files to tickets, and let agents search your notes.

The assistant

Ask it about anything in Tomrade.

It isn't only a backlog planner. The assistant works on everything Tomrade holds: tickets and workstreams, files and notes, diagrams, even Tomrade's own settings. And when there's nothing to do, it's happy to just talk.

Every change it makes is attributed and lands in History, where ⌘Z takes it back: tickets, files and settings alike. API keys, MCP servers and command lines stay yours to change.

Inbox

The backlog has a bouncer now.

Feedback waits at the door, not in your backlog.

Issues and reports land in the project's inbox first. The assistant proposes what each one is (a new ticket, a bug you already have, or a duplicate) and drafts the reply. One click confirms it.

• Accept it as a ticket, merge it into one, or close it as won't do or a duplicate. The assistant proposes; you decide.
• A repeat is counted on its ticket, so you can see what people keep running into.
• Whoever wrote hears back where they wrote: a reply on the issue, and the issue closed once its ticket ships.

GitHub issues come built in. Sources are plugins too: bring in your support mail or a feedback form.

Built-in plugins

Draw it in one sentence.

Archify comes built in. Ask the assistant, Claude Code or Codex for an architecture, workflow, sequence, data-flow or lifecycle diagram, and it lands in the conversation as a live page you can pan, zoom, trace and present. Save it to Files with its source, and ask for changes later.

WorkflowArchitectureSequenceLifecycle

YouDraw how a ticket gets from one sentence to a merged PR.

Open it live

Rendered by the Archify that ships with Tomrade. Each one is about Tomrade itself.

• Five kinds: architecture, workflow, sequence, data flow and lifecycle.
• One self-contained HTML page: pan, zoom, trace a path, present it full screen.
• Checked on every render: no overlapping boxes, crossed wires or clipped labels.
• It keeps its JSON source, so a follow-up edits the diagram instead of starting over.

Archify is an open-source project (MIT) by tt-a1i. Tomrade fetches a pinned copy from GitHub the first time you ask for a diagram.

Principles

Built so agents can move fast without stepping on you.

~/Tomrade/projects/my-app/.tomrade/
├── project.json
├── state/
│   └── items.jsonl
├── log/
│   └── macbook.jsonl
└── README.md