hitianqi / troupe
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.
- Stars
- 139 stars
- Forks
- 25 forks
- Language
- TypeScript
- License
- MIT
- Created
- Oct 24, 2026
- Last push
- Nov 13, 2026
- Updated
- Nov 19, 2026
Why these Tags: an agent read the README and quoted it
- Multi-agent orchestration from the description:
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.
- Coding agent manager from the readme:
One panel shows who is working and who needs you. Jump into any agent's terminal to read along or answer it.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 17, 2026: +105 stars in 7 days.
Star History
15 days recorded, Nov 5, 2026 – Nov 19, 2026 (UTC). Net change +139 stars.
The star count of each day is the latest count minus the net stars of the later days.
Add this Star History to a README
The images follow the light or dark theme of the page that shows them, and update every hour.
Add ?theme=light or ?theme=dark
to the chart address to keep one theme.
Star History chart
[](https://awesomerepos.com/hitianqi/troupe) Badge
[](https://awesomerepos.com/hitianqi/troupe) Timeline
It gained stars on each of the 15 days recorded since Nov 5, 2026.
Its largest 7 days were Nov 11, 2026 to Nov 17, 2026: 101 stars.
- Created on the Repository Host
- Release troupe-video-v2: Troupe demo film v2
- Release v0.6.0
- +13 stars in one day
- Release v0.7.0
- Latest push
- Largest star day recorded: +31 stars, 1 day after release v0.7.0
- Reached 100 stars, 22 days after it was created
- +19 stars in one day
- Entered the Repository Index: +105 stars in 7 days
The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.
Forks and pushes
From 3 Observations, Nov 18, 2026 – Nov 20, 2026. Forks +1. AwesomeRepos saw a new push on 0 of 2 days.
- Nov 19, 2026: no new push
- Nov 20, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 19, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 1 task for the maintainers of hitianqi/troupe.
Improve the Health Facts of the GitHub repository hitianqi/troupe. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/hitianqi/troupe. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task. 1. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-19). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. Ask me for the contact; do not invent one. Rules for this work: - Each file must be true for this project. Do not copy text that does not apply to it. - Do not choose a licence, a contact, or a release version for me. Ask me. - Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch. - Keep each change small, and run the checks of this repository before you finish. - At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question). AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts
Maintenance
3 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-13, 6 days ago. Source
-
Yes: Commits in the last 13 weeks
259 commits on the default branch in the last 13 weeks (GitHub, 2026-11-19). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 5 of the last 52 weeks (GitHub, 2026-11-19). Source
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 0
- 50
- 156
- 33
- 8
- 12
Releases
3 of 3 checks-
Yes: A release in the last 365 days
Newest release v0.7.0 on 2026-11-13, 6 days ago. 3 releases in the last 365 days. Source
-
Yes: The newest release tag is a semantic version
The newest release tag is v0.7.0. Source
-
Yes: A changelog file at the root
CHANGELOG.md at the root (GitHub, 2026-11-19). Source
Security practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-19). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
2 of 3 checksObservations
Latest Observation, Nov 20, 2026: 139 stars, 25 forks, last push Nov 13, 2026, not archived. One of 3 Observations since Nov 18, 2026.