Route Linear tickets into the right repo and PR

They used OpenClaw and Linear as a control layer to send tasks to Cyrus, which picked the repo, chose a model, and opened pull requests.

Done with OpenClaw· Intermediate· Sep 2026

What they did
A developer funneled work through Telegram and OpenClaw into one Linear account that served as the hub for several projects. In Cyrus, they configured labels and routing rules so each ticket pointed to the correct git repo for worktree creation. Those labels also decided which model to use, including codex and claude variants, and Cyrus then created pull requests for review.
How it went
The setup made their workflow more hands-off, with pull requests showing up across multiple repos ready for review. For more direct editing, they switched to Orca, a desktop interface tied into Linear and GitHub.
Tips
Make the routing rules explicit for each repo and model so the agent does not guess. If you want a test run, stop after one ticket becomes a PR and review it before taking any further action.

Try it yourself with OpenClaw

I want to send coding tasks from [Telegram or another chat app] into a Linear project for [team or workspace]. When a new ticket arrives, use my routing rules to pick the right repo from [repo list] and the right model from [model options]. Create a worktree, implement the change, and open a pull request for review. After the first test ticket reaches an open PR, pause and ask me to approve before you do anything that would merge, submit, delete, or send it onward. If a ticket is ambiguous, stop and ask which repo or model to use.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on news.ycombinator.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.