Skip to content

Open-source AI teammates in Slack, Teams, Discord, Telegram and Mattermost. Self-host it, with any agent harness and any model.

Document who may turn auto-route on and who names the triage agent

agent-runner35349a49b455697
diff --git a/console/packages/plugins/src/switch-skill/SKILL.md b/console/packages/plugins/src/switch-skill/SKILL.md
index 37f118ae4..543699da7 100644
--- a/console/packages/plugins/src/switch-skill/SKILL.md
+++ b/console/packages/plugins/src/switch-skill/SKILL.md
@@ -158,7 +158,9 @@ does, and there is no polling tool to call.
rather than to the agent that spoke there last, and answering a routed
message does not make the person's next untagged message a follow-up to you:
it is decided again. `!auto-route off` turns it off, and `!auto-route` on its
- own says which it is and whether it can act.
+ own says which it is and whether it can act. Anyone who can post in the
+ room may turn it on or off, from the room or from its toggle in Switch
+ Console or on the gateway's room page (both need write access to the room).
Which decision service a room uses is its workspace's choice, made by a
workspace admin in Switch Console → Admin → Decision routing: the server's
@@ -167,9 +169,10 @@ does, and there is no polling tool to call.
decision service and changes nothing, and the room works as it does without
it. When the decision service fails, the message goes to nobody and Switch
posts "Auto-route is unavailable right now; tag an agent to reach it." in
- the room, at most once an hour. A room can name a triage agent for those
- messages with `!auto-route fallback @agent` (`!auto-route fallback off`
- clears it; it can't be the room's assigned agent). If you are that agent,
+ the room, at most once an hour. The room's owner or a workspace admin can
+ name a triage agent for those messages with `!auto-route fallback @agent`
+ (`!auto-route fallback off` clears it; it can't be the room's assigned
+ agent); anyone else who tries is told who can. If you are that agent,
such a message reaches you marked as a fallback: auto-route was unavailable,
so it came to you as the room's triage agent. Answer it if it is yours, or
say briefly which agent to tag.
diff --git a/console/packages/plugins/src/switch-skill/switch-skill.test.ts b/console/packages/plugins/src/switch-skill/switch-skill.test.ts
index 3a3847dfa..e77958abb 100644
--- a/console/packages/plugins/src/switch-skill/switch-skill.test.ts
+++ b/console/packages/plugins/src/switch-skill/switch-skill.test.ts
@@ -28,4 +28,12 @@ describe('switch skill', () => {
expect(text).toContain('`!auto-route fallback off`');
expect(text).toContain("came to you as the room's triage agent");
});
+
+ it('says who may turn auto-route on or off, and who may name the triage agent', () => {
+ const text = SWITCH_SKILL_CONTEXT.replace(/\s+/g, ' ');
+ expect(text).toContain('Anyone who can post in the room may turn it on or off');
+ expect(text).toContain(
+ "The room's owner or a workspace admin can name a triage agent for those messages"
+ );
+ });
});
diff --git a/docs/old/decision-routing.md b/docs/old/decision-routing.md
index da78edd25..074af707f 100644
--- a/docs/old/decision-routing.md
+++ b/docs/old/decision-routing.md
@@ -107,12 +107,30 @@ only: `GET`, `PUT` and `DELETE /gateway/decision-settings`, and
## In a room
`!auto-route on` and the auto-route toggle on the room page (Console and the
-gateway, `PUT /gateway/rooms/{id}/auto-route`, for the room's owner and
-workspace admins) set the same switch. Turning it on is refused, with the
-reason and who can fix it, where it cannot act: the flag is off, or the
-workspace resolves to no backend. A room's detail reports
+gateway, `PUT /gateway/rooms/{id}/auto-route`) set the same switch. Turning it
+on is refused, with the reason and who can fix it, where it cannot act: the
+flag is off, or the workspace resolves to no backend. A room's detail reports
`auto_route: {on, available, reason, fallback_agent, fallback_agent_name}`.
+### Who can change it
+
+- **Turning auto-route on or off** takes write access to the room, the same as
+ `!follow-ups` and `!assign-agent`: its owner, a workspace admin, or anyone
+ on a room everyone may write to. In chat, anyone who can post in the room
+ may send `!auto-route on|off`. In Console and on the gateway's room page the
+ toggle follows the room's `can_write`, and is shown disabled, with the
+ reason, to someone who can see the room but not write to it. The API
+ answers 403 without write access.
+- **Naming or clearing the triage agent** takes the room's owner or a
+ workspace admin (the room's `can_manage`), because it chooses an agent that
+ gets messages nobody addressed to it. `!auto-route fallback @agent|off` from
+ anyone else is refused with a reply saying who can; the picker in Console
+ and on the gateway is read-only for them ("Only the room's owner or a
+ workspace admin can change this"); and a `PUT` carrying `fallback_agent`
+ answers 403. Anyone may see which agent it is.
+- **Choosing the workspace's decision backend** stays with workspace admins
+ (above).
+
### When there is no backend
Nothing changes from a room without auto-route: tags, aliases, roles, direct