Skip to content
Documentation menu

Roadmap

trusty-mpm roadmap

trusty-mpm runs your coding sessions and keeps them going. The next two releases make that dependable. The release after them, 2.0.0, adds a supervisor that looks after all of your projects for you.

What 2.0.0 brings

A supervisor you create with one request. Ask for a supervisor and trusty-mpm sets one up: a small project of its own, kept as a local git repository, watching the projects you choose. You can add or remove a project later. It runs on the latest Opus model.

Instructions made for supervising. A normal trusty-mpm session is a project manager that hands coding work to specialist agents. A supervisor has a different job: it watches sessions, acts directly, and reports what it saw and what it checked. It gets its own instructions and its own writing style, so it carries none of the project-manager rules it never uses.

Chat channels for your projects, starting with Slack. A project can be given a channel. When the supervisor needs your decision, it sends you the question there, and your reply goes straight back to it. You no longer have to be at the terminal to unblock it.

Careful about who can talk to it. Messages follow a routing table that refuses anything not explicitly allowed. At first the only allowed sender and recipient is the owner. An incoming message can answer a question the supervisor asked, and nothing else: it cannot start work or run commands. If two answers arrive, the first one counts.

One supervisor for everything. A single supervisor serves every project, so the same question never reaches you twice.

How we get there

1.7.1 finishes the reliability work already under way. 1.7.2 is bug fixes only. 2.0.0 follows.

Now

1.7.1

1.7.1 is a reliability release focused on session and account safety. tm now always acts on the exact tmux session it means, so it never touches another session with a similar name; worktree removal only happens once your work has actually landed; and --user/account pinning no longer falls back silently to your global account. It also fixes the supervisor's background launch behavior, so the LaunchAgent no longer runs tmux at background priority and your tmux.alternate_screen setting reaches Claude Code on every launch path.

6 of 50 items done · follow on GitHub

Next

1.7.2

trusty-mpm 1.7.2 — bug fixes after 1.7.1. The release line is 1.7.1 (in flight) → 1.7.2 (bug fixes) → 2.0.0 (supervisor and channels platform).

0 of 59 items done · follow on GitHub

2.0.0

trusty-mpm 2.0.0 adds a supervisor: one session that watches all of your projects, handles what it can, and asks you about the rest. You create it with a single request, and it comes with its own instructions and writing style, made for watching and reporting instead of for running coding work. Each project can be given its own chat channel, starting with Slack, so the supervisor can send you a question and take your answer there. Incoming messages go through a routing table that refuses anything not explicitly allowed, and a message can only answer a question the supervisor actually asked. One supervisor serves every project, so the same question never reaches you twice.

0 of 8 items done · follow on GitHub

Later

cross-harness

Work so trusty-mpm can drive coding harnesses other than Claude Code — Codex and Cursor — each independently usable behind one orchestration layer, without breaking any harness already deployed.

0 of 7 items done · follow on GitHub