Routing

When more than one agent is connected, submit a task with the provider set to auto and vemlor decides which agent runs it. A fast classifier looks at the task and picks a connected agent; if it can't decide, it falls back to your first runnable agent.

Routing only runs when the provider is auto. Pin a task to a specific agent and vemlor uses that one, no questions asked.

Override rules

Workspace owners can define deterministic rules that bypass the classifier. Rules are checked in order and the first match wins, so put your most specific rules first.

Each rule matches on any combination of:

• intent: the classified kind of work (for example a bug fix or a refactor).
• repo / repo_glob: an exact repo or a glob like acme/*.
• platform: github or gitlab.
• source: where the task came from (a comment, a webhook, the app).
• len_gt / len_lt: prompt length thresholds.
• has_code_fence: whether the prompt contains a code block.

A match sets the provider (and optionally a specific model) for that task. For example: route everything in acme/legacy-* to Claude, and send short one-line asks to a fast model.

Rules are workspace-scoped and only consulted for auto tasks.