Skip to content

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

feat(connectors): make agents write like room participants (#210)

Louis Amaudruz80913c1f2f69
diff --git a/connectors/claude-code-plugin/.claude-plugin/plugin.json b/connectors/claude-code-plugin/.claude-plugin/plugin.json
index 35934da5f..c73a591cd 100644
--- a/connectors/claude-code-plugin/.claude-plugin/plugin.json
+++ b/connectors/claude-code-plugin/.claude-plugin/plugin.json
@@ -1,5 +1,5 @@
{
"name": "switch-connector",
- "version": "0.8.1",
+ "version": "0.9.0",
"description": "Connect Claude Code to a Switch platform instance as a participating agent"
}
diff --git a/connectors/claude-code-plugin/skills/switch/SKILL.md b/connectors/claude-code-plugin/skills/switch/SKILL.md
index faf829417..2e8c1c380 100644
--- a/connectors/claude-code-plugin/skills/switch/SKILL.md
+++ b/connectors/claude-code-plugin/skills/switch/SKILL.md
@@ -15,6 +15,41 @@ travel that same connection — you never talk to the Switch server directly.
now; it stays true until the session ends. The later sections are reference —
consult them when the work calls for them, and otherwise get on with it.
+## How to write in a room
+
+A room is a chat channel, not a report. People read it in Slack, Mattermost or
+the console, often on a phone, in between everything else. Write for that, not
+for a terminal transcript. **Default to a few sentences.**
+
+- **Answer first.** Then only the detail that changes what someone does next.
+ No preamble, no restating the question, no recap of the steps you took, no
+ closing offer of further help.
+- **Plain words.** Say what happened in the room's terms. Leave out the
+ vocabulary of your own run — file paths, tool names, step-by-step narration —
+ unless someone needs it to act.
+- **One message, one point.** Do not spread a single thought across a burst of
+ posts, and do not bundle five topics into one wall of text.
+- **Shorter, not thinner.** Say everything that has to be said — the caveat,
+ the number, the thing that will bite them — and nothing else. Cutting content
+ to be brief is worse than being long.
+
+## Say something before you go quiet
+
+Silence in a chat room reads as absence. If answering will take more than a
+moment — you are about to read a codebase, run a build, wait on another agent,
+or work through several steps — post a one-line heads-up first, do the work,
+then post the result.
+
+- "On it — checking the deploy logs." That is the whole acknowledgement; do not
+ pad it with a plan.
+- Acknowledge once. A long job earns an interim update when the picture changes
+ or your estimate slips, not a commentary on every step.
+- For tracked work the task protocol already does this: `accept_task` tells the
+ room you have it, `update_task` records progress, `finalise_task` reports the
+ outcome — no parallel narration in messages.
+- The heads-up is not the answer. Always come back with the result, in the same
+ thread.
+
## Entering a room
1. **`list_rooms`** — the rooms you are assigned to. Skip it if you were given
diff --git a/connectors/codex-plugin/.codex-plugin/plugin.json b/connectors/codex-plugin/.codex-plugin/plugin.json
index 3a2658eae..e4c19f7cd 100644
--- a/connectors/codex-plugin/.codex-plugin/plugin.json
+++ b/connectors/codex-plugin/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "switch-connector-codex",
- "version": "0.2.3",
+ "version": "0.3.0",
"description": "Connect Codex to a Switch platform instance as a participating agent",
"skills": "./skills/",
"mcpServers": "./.mcp.json"
diff --git a/connectors/codex-plugin/skills/switch/SKILL.md b/connectors/codex-plugin/skills/switch/SKILL.md
index e8b943a60..bfe547304 100644
--- a/connectors/codex-plugin/skills/switch/SKILL.md
+++ b/connectors/codex-plugin/skills/switch/SKILL.md
@@ -18,6 +18,41 @@ guessing.
now; it stays true until the session ends. The later sections are reference —
consult them when the work calls for them, and otherwise get on with it.
+## How to write in a room
+
+A room is a chat channel, not a report. People read it in Slack, Mattermost or
+the console, often on a phone, in between everything else. Write for that, not
+for a terminal transcript. **Default to a few sentences.**
+
+- **Answer first.** Then only the detail that changes what someone does next.
+ No preamble, no restating the question, no recap of the steps you took, no
+ closing offer of further help.
+- **Plain words.** Say what happened in the room's terms. Leave out the
+ vocabulary of your own run — file paths, tool names, step-by-step narration —
+ unless someone needs it to act.
+- **One message, one point.** Do not spread a single thought across a burst of
+ posts, and do not bundle five topics into one wall of text.
+- **Shorter, not thinner.** Say everything that has to be said — the caveat,
+ the number, the thing that will bite them — and nothing else. Cutting content
+ to be brief is worse than being long.
+
+## Say something before you go quiet
+
+Silence in a chat room reads as absence. If answering will take more than a
+moment — you are about to read a codebase, run a build, wait on another agent,
+or work through several steps — post a one-line heads-up first, do the work,
+then post the result.
+
+- "On it — checking the deploy logs." That is the whole acknowledgement; do not
+ pad it with a plan.
+- Acknowledge once. A long job earns an interim update when the picture changes
+ or your estimate slips, not a commentary on every step.
+- For tracked work the task protocol already does this: `accept_task` tells the
+ room you have it, `update_task` records progress, `finalise_task` reports the
+ outcome — no parallel narration in messages.
+- The heads-up is not the answer. Always come back with the result, in the same
+ thread.
+
## Entering a room
1. **`list_rooms`** — the rooms you are assigned to. Skip it if you were given