Skillget

troupe

agent
Security Audit
Fail
Health Pass
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 10 GitHub stars
Code Fail
  • fs module — File system access in package.json
  • exec() — Shell command execution in src/agents.ts
  • process.env — Environment variable access in src/command-context.ts
Permissions Pass
  • Permissions — No dangerous permissions requested

No AI report is available for this listing yet.

SUMMARY

Run a team of coding agents you can actually watch: one approved plan, each role in its own tmux window and git worktree, on Claude Code or Codex.

README.md

troupe — One command. Your agents, in order.

Put Claude Code and Codex on the same team.
See every agent. Step in anytime.

English — current language 阅读简体中文版

Watch the demo Quick start User guide

MIT license Claude Code and Codex Runs in tmux

Demo

A task from plan to review and cleanup, in 68 seconds.

Open the English demo: the troupe panel shows the team and highlights an agent waiting for you
▶ English demo · 1:08 · 中文版 · 1080p downloads

Why troupe

  • See the team, and step in. Every agent is a real Claude Code or Codex session. One panel shows who is working and who needs you. Jump into any agent's terminal to read along or answer it.
  • Agree on the work before it starts. Review the plan, change the split, and approve it. Each role gets its own git worktree and branch; planned file overlaps need an explicit order.
  • Build and review with different agents. Mix Claude Code and Codex, models and effort per role. The default workflow reviews each branch, asks before opening the pull request, and waits for your merge confirmation before cleanup.

The live troupe panel: agent roles, work stages, activity and a flow of the team

Quick start

You need macOS, Linux or WSL2, tmux, Node.js 20+, git, and Claude Code and/or Codex, installed and signed in.

Install:

npm install -g troupe-cli
troupe setup

To run your own build instead, see Contributing.

troupe setup installs the workflow skill for the agents it finds.

Then open Claude Code or Codex inside tmux, in the repository you want to change, and ask:

Run a troupe mission: add a search box that filters the list as you type,
and a dark theme that follows the system setting.

The agent writes the plan and opens the panel beside it. Read the plan, press a to approve or c to request changes, and the team starts after approval.

You can also run troupe up -m <mission> in your target repository to start the orchestrator and panel together.

From one task to a finished change

  1. Plan together. The orchestrator reads your code and proposes the work, roles and completion criteria. You can ask for changes before approving.
  2. Watch the team work. Independent roles run in parallel; dependent roles wait their turn. Each has a terminal and worktree of its own. The panel shows when someone needs you.
  3. Review each branch. A reviewer checks the work as it lands. Findings go back to the same agent for a fix round before the orchestrator merges into the mission branch.
  4. Approve the handoff. You approve opening the pull request, merge it yourself, and confirm. The workflow then closes its terminals and removes its temporary worktrees.
See the plan approval, agent terminals and final handoff

Change the plan, or approve it.

Reviewing and approving a plan

Claude Code, Codex and a reviewer, each in a real terminal.

Agent terminals working side by side

You approve the pull request and confirm the merge before cleanup.

Pull request approval, merge confirmation and cleanup

Make it yours

The workflow lives in a skill: when to review, when to merge and which questions to ask you. Change or replace it to fit how you work. The CLI checks plan approval, role dependencies, declared file overlaps and agent permissions.

Multiple missions can run in the same repository or across repositories. Each gets its own mission branch and worktree; your original checkout stays on its branch.

  • User guide — plan format, commands, panel controls, adapters and known limits.
  • Roadmap — product direction and what's next.
  • Contributing — development setup, checks and adding an agent.
  • Issues — bugs, questions and feature requests.

Acknowledgements

Prover

troupe started as an internal tool at Prover and is open-sourced with their support. See NOTICE.


MIT licensed. Built with TypeScript, tmux and git, with no runtime npm dependencies.

Reviews (0)

No results found