Coordinate sub-agents to monitor PRs and fix prod bugs
A Cursor Projects coordinator agent delegates to sub-agents, watches new PRs and production bugs, spins up agents to fix issues, and surfaces questions to the user.
A developer sends tasks via Telegram/OpenClaw into Linear, where Cyrus routes each to the right repo and model and opens PRs for review.
A developer sends tasks via Telegram/OpenClaw into Linear, where Cyrus routes each to the right repo and model and opens PRs for review.
The developer sends tasks through Telegram/OpenClaw into a single Linear account that acts as the control plane across several projects. In Cyrus, they set up labels and routing so it knows which git repo to build worktrees from. Labels also select the model, such as codex or claude variants. Cyrus then opens PRs for review.
The setup lets the developer work more hands-off, with PRs arriving across multiple repos for review. No numbers are given. For hands-on work they use Orca instead, a desktop UI with Linear and GitHub integrations.
Set up a flow where I send a task by [Telegram or another chat app] and you create a Linear ticket for it in [team name]. Route each ticket to the right repo from [list of repos] and the right model, and have the coding agent open a pull request for review. Stop when one test task has gone from message to open PR, and never merge anything without my approval.
A Cursor Projects coordinator agent delegates to sub-agents, watches new PRs and production bugs, spins up agents to fix issues, and surfaces questions to the user.
Ran a Cursor agent continuously for 24 hours to build a project management tool; the app fully works but is not production ready.
The author had ChatGPT take the Session Buddy extension source from Chrome, port it to Safari and install it, taking about 20 minutes.