Skip to content

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

E2E README: list the agent-identity scenario

Petr Bauch5931fac5c010
diff --git a/console/tooling-e2e/README.md b/console/tooling-e2e/README.md
index 4273b7949..cb544ad3e 100644
--- a/console/tooling-e2e/README.md
+++ b/console/tooling-e2e/README.md
@@ -137,6 +137,7 @@ passed or not. A teardown that leaves something behind fails the scenario.
| `unaddressed-history` | Five unaddressed messages arrive in the recipient's room history in the order sent, and none of them as a notification. | — |
| `operations-front-door` | The operations registry over HTTP: it lists the operations, `list_rooms` returns the room, `read_context` returns a message posted in it. | — |
| `mattermost-roundtrip` | A room on the Mattermost bridge: an addressed post from the human reaches the agent, and the agent's reply appears as its bot. | Mattermost |
+| `agent-identity` | Renaming an agent from the gateway and with `!rename-agent` renames its Mattermost bot in place, and mentions follow the new name; `!delete-agent`, confirmed, deletes it. | Mattermost |
If `mattermost-roundtrip` passes and a provider-lane scenario fails, the fault
is in the agent session, not in Switch, the bridge or the harness.