Sessions
How threads map to sessions, and what shows up on Dashboard.
Each Slack thread you talk to Sauna in is its own session. You can have many going at once. They all land on your Dashboard next to your web sessions.
- One thread, one session. Each thread you talk to Sauna in becomes its own session, the workspace, channel, thread, and your Slack identity together pin it down. A new message in a thread with no session triggers a new one; every later message in that thread feeds the same one.
- Abort on new message. Sending a new message to an existing session cancels whatever turn was in flight before the new one dispatches.
- Title. The first 100 chars of your first message become the session title, shown on Dashboard and in Slack's assistant sidebar.
- Shared threads split by user. In a shared thread (root without
@Sauna, reply with@Sauna), each person who mentions Sauna gets their own session. Your coworker's answers don't land in your session. - Dashboard shows them all. Slack-triggered sessions appear on Dashboard with a Slack tag. Filter by Slack to narrow the board.
- Web and Slack stay separate. A session you started on the web stays on the web; a Slack thread stays in Slack. Continuation is thread-based, not a unified conversation across surfaces.
- No in-thread reset command. To start a fresh session, open a new DM chat or a new channel thread. Slack has no
/new. - Schedules don't deliver to Slack. Scheduled tasks can send to iMessage and email, not to Slack.
