Feature request for product/service Cloud Agent (GitHub, Slack, Linear,…) Describe the request Problem: When delegating Linear issues to @Cursor, repo routing works via repo/ labels, but worker pool must be selected manually every time — even when the repo implies the pool (e.g. repo/redzone-ios-co…

Hey June! The case you’re describing should mostly just work today under one specific combination: if each repo maps to only one pool, and your team has “Require Self-Hosted Pool” turned on for all cloud agents. In that setup the repo label alone is enough to land a ticket on the right machines, yo…

To answer your questions: No, Require Self-Hosted Pool is turned off. We only need one repo routed to a particular pool; most repos can run on the default Cursor-managed cloud. So no, it’s not a case where each repo is served by exactly one pool, but there is one repo that is served by exactly one p…

Auto-route worker pool from repo label/key (Linear / Cloud Agents)

Ideas Feature Requests

Troy_Gibb (Troy Gibb) July 19, 2026, 2:15pm 8

We have a similar use case that is not being served by Cursor’s self-hosted routing rules but for monorepos. Posted here: Self-Hosted Routing for Monorepos

Topic		Replies	Views
Self-Hosted Routing for Monorepos Help cloud-agents , large-codebases	3	94	July 22, 2026
Linear-triggered multi-repo agents — route via environment membership Feature Requests cloud-agents , linear , automations	12	246	July 30, 2026
Linear default repo selection (similar to slack) Feature Requests cloud-agents , linear , slack	1	35	July 21, 2026
Use Multirepo Workspace when Triggered from Linear Help cloud-agents , linear	5	176	July 17, 2026
Cloud agents - corporate network access Help teams-enterprise , cloud-agents	2	147	July 8, 2026

Auto-route worker pool from repo label/key (Linear / Cloud Agents)

Related topics