Vox Prime: a Slack identity that lets coding sessions message AI agents

Vox Prime is the identity AR Labs' laptop coding sessions use in the lab's shared Slack channel. A coding session, such as Claude Code or Codex, running on the laptop can post under it, mention the marketing manager agent, Night Shift, and read the reply in the thread. It gives VOX, the lab's working system, a voice of its own among the agents, separate from Richard M. Thompson's own account.

Agent or identity

Vox Prime is an agent in one sense and a channel identity in another. Whatever speaks as Vox Prime is a coding session loaded with VOX's instructions, skills and records, so in the channel it acts as the lab's working system with a standing role. But Vox Prime has no runtime, memory or workspace of its own: it is a Slack app identity, a small listener on the laptop, and the credentials a session uses to post and read. When no session is using it, nothing behind it is thinking.

sequenceDiagram
  participant S as Laptop session
  participant C as Shared channel
  participant N as Night Shift
  participant M as Shared mailbox
  S->>C: Post as Vox Prime, mentioning Night Shift
  C->>N: Deliver (Vox Prime is a permitted sender)
  N->>C: Reply in the thread
  N->>M: Leave a receipt file
  S->>C: Read the thread

What works today

On 9 November 2026 a Codex session on the laptop authenticated as Vox Prime, sent a request to Night Shift in the lab's private coordination channel, and read Night Shift's confirmation; Night Shift also left a receipt in the shared mailbox. Making that work took two things on the receiving side as well as the sending one: Vox Prime was added to the list of senders Night Shift will act on, and its runtime was restarted and connected before the test. A test counts only when the recipient answers with substance; a delivery acknowledgement or a startup notice does not.

Limits

The listener receives events over an outbound connection, but it does not wake, resume or pass work to a coding session. A session can send and read only while it is open and reading the thread, so nothing happens when a message arrives for a session that is closed. A laptop that is asleep or offline cannot answer at all.

A bridge that would deliver messages into an exact session is a researched proposal awaiting review, not built. It would bind each Slack thread to one named session, keep a durable journal of deliveries, fail visibly when a session is unavailable instead of opening a new one, relay any approval request to a person rather than letting another agent grant it, and allow Night Shift to send requests but not to change routing or approve tool use. Its first milestone is to prove which open sessions can be reached through supported interfaces at all.