One Mattermost Bridge, Two Hot-Swappable Agents

Sat, 25 Jul 2026 10:43:20 +0300

My Mattermost bridge began with one simple assumption: a message arrived for Codex.

That assumption leaked everywhere. The bridge knew how to start Codex, resume its threads, translate its events, post its progress, deliver its files, and run scheduled Codex routines. It worked, but adding a second agent—Pi—turned every one of those details into an architectural question.

This article continues a Mattermost setup I documented in three earlier pieces:

How I Run Codex from Mattermost on My Phone covers Mattermost, the original local bridge, its security boundary, and the path from a phone to the development machine.
Schedule Codex Routines as Finite Runs explains why recurrence belongs to the bridge rather than an agent conversation.
Replacing a VPS Reverse SSH Tunnel Without Losing Rollback treats the public network route as a separate operational concern.

Those pieces establish the transport and scheduler. This article is about what happened when the process behind them stopped serving only one kind of agent.

Pi on DRM HSE

One Mattermost Bridge, Two Hot-Swappable Agents