Hosted & teams · Private beta
Routing rules
Every string has a reason.
Make the decision visible.
The rules view shows the condition and destination logic together. A shared rule model keeps the dashboard, API, and agent interface talking about the same routing decisions.
A PR remembers its workspace.
A matching pepe/<workspace>/<branch> branch establishes ownership. After the PR is pinned, later comments and reviews follow that workspace even if the branch is renamed. Forks cannot establish ownership just by copying a prefix.
Login takes the return trip.
Google OAuth callbacks follow the short-lived transaction created by the workspace that started the login. The destination is its exact registered callback; the transaction expires and can be used only once.
No match means no broadcast.
An event without an owner stays unclaimed. Assign the correct PR ownership and replay it when you are ready. That keeps an ambiguous event away from everyone else’s development environment.