One, two, many, lots. We’re at two.

The zero-one-infinity rule says a design should allow none of a thing, one of it, or any number, and never stop at an arbitrary count. In Pratchett’s Discworld, trolls count “one, two, many, lots”. We’re at two.

Zero was nothing. One was shmobster, our agent, on Slack, and one surface needs no abstraction: the agent and the place it talks are the same thing. Two is Slack and Signal. The second surface is the one that makes you separate what the agent does from where it talks. Many is what that separation allows. It isn’t what we run.

One thing, done well

The separation is the Unix idea: a part does one thing and does it well, and the others talk to it. On Signal that’s literal. signal-cli can be held by one process at a time, so one process has to own the account, and everything else becomes its client.

That process is voitta-gateway, now public under the AGPL. It is one API in front of Signal, Slack and the phone network: REST commands, an event stream that replays from any event id, and a media socket per call. It runs as a service or embedded in a single agent, and its API is specified in OpenAPI and AsyncAPI. The rule it is built around is one owner per identity: one process holds the account, and every agent behind it is a consumer with its own token. Group ids stay in the gateway’s config; an agent knows a group only by a label. The agents on it today include shmobster and a lead-finding agent.

The gateway is one part of Voitta’s open operating system, the parts that let AI work with a business’s own records, in four jobs: reach the records, connect the tools, fence the actions, coordinate the agents. It is the newest part in the last one. shmobster does the work in the channel; yolt classifies the commands it wants to run.

One sender, several agents

On Slack each bot is its own user. On Signal everyone sees one account. So the gateway signs each agent’s messages with its label, routes an incoming message by what it quotes, whom it names, or a default, and answers a bare /help itself with the agents on the account. /help <agent> reaches that agent, which answers without the model: what it is, how to reach it, and whether it asks before changing anything.

The rest of Signal is different enough from Slack to force a choice at every turn:

  • Identity. A Signal user is an account id with a profile name they chose themselves. Anyone can call themselves anything, so the agent never shows a profile name. People are the name the operator gave them, or a stable handle like “Signal user 3f9a2c”. Trust is by account id.
  • Mentions. Signal puts each @mention on a U+FFFC placeholder plus an id. Before #401, “talk to @X” reached the model as “talk to @someone”. Now the agent can write @name back and it becomes a real mention, built the same way, never inside code or a URL.
  • Approvals without buttons. A trusted user types approve <id>. In a group, a bare approve reached no agent, because a group message has to name or quote one, so the cards now say so.
  • Markup. Our release announcement arrived on Signal as raw Slack markup, :sparkles: and all. Now one Markdown source is rendered per surface: Signal gets bold and monospace, and a link becomes its text with the URL after it.
  • Limits. Signal’s limit is 2000 UTF-8 bytes, but style offsets count UTF-16 units, so the renderer keeps two counters that must never meet. Past the limit, signal-cli doesn’t fail. It cuts the message and attaches the rest. Replies are split by bytes. An approval card is never split; if it can’t fit, it’s withdrawn.
  • Edits. Another agent sends a stub and then edits in the full text. Ours answered the stub: “your message got cut off”. Edits are separate events, and we don’t read them yet (#404, open).

Closed groups only

shmobster is built for private channels. A Signal group is only as private as its settings: a group link lets anyone holding it walk in, and “any member can add members” lets the group grow without its admins. So shmobster serves only closed groups. That’s a fixed rule, not a setting, and not open to argument in a PR. In an open group, or one it can’t check, the agent says why and how to close it, at most once an hour, and withholds every other post: replies, command output, cards, alerts, announcements.

One wrinkle from the README: an invite link that requires admin approval also counts as open, because signal-cli can’t tell the two apart.

Inside a closed group, membership is the permission, as it is in a private Slack channel. We first planned a per-sender allowlist for other agents and dropped it. In the live test, the agent mentioned another agent with a real mention, and that agent’s reply reached it as an ordinary member. Two agents that can reach each other can also talk forever, so after three answers in a row to agents, ours waits for a person to speak. That’s prevention; we haven’t seen a loop.

What review caught

Each of these changes went through an adversarial review before merge. Three catches worth naming:

  • The gateway’s check of whether a group is closed first ran inside signal-cli’s reader, with a 15-second timeout, and stalled all Signal traffic while it waited. It now runs in the background.
  • shmobster first kept its own list of Signal groups, joined to the gateway’s by a label string, and a rename silently dropped a group’s policy. Now the gateway owns presence and shmobster owns behaviour. The first cut of that made an entry holding only routing keys an empty policy, with no repo limits at all. Routing keys no longer count as policy.
  • The first replies on Signal read “Ada: Ada: …”. The gateway signs every message with the agent’s label, the agent’s history came back signed, and the model, a fast learner, signed its own replies too. The first fix ran before the agent’s marker was stripped, so it missed normal replies (#394).

And

The approval gate’s enforcement changes next week. That gets its own post.

shmobster also got its first outside pull request. Someone running it on Linux found that the health check could never restart a frozen agent: GNU stat -f means “file system”, not “format”, so the mtime came back as several lines of text and the check died on every run. They sent a one-line fix with a reproduction and a table of results on both kinds of stat. Thank you.

Do you have this problem?

If several of your agents need to share one messaging account, talk to us.