Slack AI Lab

A Slack bot answers questions in Pigfox's own workspace, and this page is a live read-only mirror of what it said. When someone there mentions the bot, it makes one model call and replies in the thread. The exchange is recorded, and it appears below.

What you are looking at

The conversation below happened in Slack, in Pigfox LLC's own workspace, when a member of it mentioned the bot there. This page is a read-only mirror of that record. Opening it causes no model call, sends nothing anywhere, and changes nothing — there is no box to type in, because there is nothing here to type into.

Questions are shown without who asked them. The workspace is private and this page is public, so the row behind each exchange has no name, no user id and no channel in it — not hidden at render time, but absent from the table. What crosses the line is the question, because the question is about this site; who asked it does not.

The bot is a real one. It runs in this server process, connects to Slack over Socket Mode, and calls claude-haiku-4-5-20251001 once per mention with a system prompt written on the server. Its replies land in the Slack thread first; this page is downstream of that.

You are seeing the most recent 20 exchanges, and nothing older than 7 days — a recent record rather than an archive. Older rows are deleted on a timer.

Where the work happens

The bot is a goroutine in this process, not a second service. Socket Mode dials out over a websocket Slack holds open, so it needs no inbound route, no public URL and no shared secret — which is why this demo added a dependency and no endpoint. When the connection drops the client reconnects with backoff; when it cannot, the status line below says so.

The exchange reaches this page over a server-sent event stream: on connect the server replays the recent record from its table, then forwards each new exchange as the bot records it. At most 32 mirrors stream at once.

The same bot, standalone and runnable against your own workspace in a few minutes: https://github.com/pigfox/slack-ai-lab.

The record

Connecting to the record…

    Reading it

    Each entry carries the question as it was asked, the bot's reply as it was posted, and what the call reported it cost — the input and output token counts are the API's own figures, not an estimate.

    An exchange that arrives while you are watching is marked as new. Everything else was replayed from the record when you connected.

    If the bot is not connected, the status line says so and the record below is still shown. An empty transcript and an offline bot are different things, and the page distinguishes them rather than leaving you to guess.