[Feature]: Explicit routing options

[T4cC0re]

Preflight

• I searched existing issues and docs before opening this.
• This proposal is grounded in a real Roomote use case, not a broad generated feature list.

Problem

(I only tested Discord)
When using the /run command you can specify a Task, but which project this task is getting routed to, comes in a follow-question in a thread. For Discord this seems limited to 5 environments. It is impossible to route to another project than the list generated by roomote and presented wothin Discord

Current workaround

Go into the web-view and create the task there - with the drawback of not having it within Discord anymore

Proposed behavior

Expand the /run command to include a way to route to a dedicated project; or: have roomote assign specific channels to specific Projects. This would also benefit the “manual in the Web-View” aspect, as those tasks could be automatically posted there aswell.

Affected surfaces

Other

Self-hosting implications

Alternatives considered

I tried posting a verbatim message with routing instructions in Project XYZ do this without it reliably working

Documentation impact

No response

[roomote-community]

I've analyzed this issue and here's my proposed implementation plan:

1. Update apps/api/src/handlers/discord/routing-confirmation.ts so buildOptions() retains every environment returned by getAvailableEnvironments() instead of truncating the list to three. Keep the router's suggested environment first and the remaining environments alphabetized.
2. Paginate the existing Discord button picker within Discord's five-action-row limit. Keep environment selections readable, reserve a compact control row for previous/next navigation, All repositories, and Never mind, and use stable global option indexes so any environment can be selected from any page.
3. Extend the routing callback parsing/handling in routing-confirmation.ts to support page navigation without consuming the pending route. Preserve the existing requester authorization, Redis TTL/pointers, atomic claim behavior for terminal selections, auto-confirm of the router suggestion, natural-language rerouting, and expired-card handling.
4. Add regression coverage in apps/api/src/handlers/discord/__tests__/routing-confirmation.test.ts for more environments than fit on one page, page boundaries, selecting an environment from a later page, cancel/all-repositories controls, unauthorized clicks, and preserving pending state while navigating. Update callback integration coverage in apps/api/src/handlers/discord/__tests__/callback-actions.test.ts or index.test.ts if the callback shape changes.
5. Update apps/docs/providers/communications/discord.mdx to explain that users can page through all available environments or reply naturally when Roomote asks where to run a task.

The current repository command is /new request:<request> rather than /run; both /new and mention/DM intake use this shared routing confirmation. Fixing the picker there solves the reported inability to explicitly choose an omitted environment across Discord entry points without introducing channel-to-environment precedence rules as part of this issue.

Please tag @roomote if you'd like me to implement this, or reply with feedback on the plan.

[T4cC0re]

Not sure if this is possible, but if the /new command can have more than one parameter, adding the environment, or repository URL as a second parameter would be a nice, declarative way of doing that too.

[mrubens]

Hi @T4cC0re, we just added a "routing rules" section in /settings/environments that might help with part of this? #1238

I'll look into the Discord behavior as well.