Conversations

A conversation in Rundock is a thread between you and one or more agents. Every conversation lives in its workspace, persists across restarts, and carries enough context for the team to pick up where you left off. The org chart shows who’s on your team. Workspaces hold the files. Conversations are where the work happens.

​

Lifecycle

A conversation has one of two statuses:

• Active. The conversation sits in your main sidebar list, sorted by most recent activity. Active is the default for any new conversation.
• Archived. You’ve put the conversation aside. It moves into a collapsible “Archived” section at the bottom of the sidebar.

Archive behaves like Gmail’s archive, not a hard “complete” or “delete”. An archived conversation is set aside but findable; sending a new message in an archived conversation automatically reactivates it. To archive a conversation, click the ✓ button that appears on hover in the sidebar, or click the Active badge in the chat header. To unarchive without sending a message, click the Archived badge in the chat header. Deleting a conversation is a separate, deliberate action. The bin icon only appears in the sidebar on already-archived conversations: the lifecycle is Active to Archived to Delete, mirroring how email and most productivity tools handle long-lived threads.

​

Multi-agent conversations

Most conversations start with one agent. From there, the orchestrator (the top of your org chart) routes work to specialists when a request falls outside its own scope. The conversation keeps a single thread but tracks who said what. When one agent hands work to another, it says so in the thread, in its own words: what it is passing on, and to whom. When a specialist finishes its work, control returns to whoever delegated it, the orchestrator or a lead specialist, with the specialist’s output in context. You do not have to keep starting new conversations to switch agents.

​

What the sidebar tells you

The conversation sidebar surfaces a lot of state at a glance:

• Filter pills (All, Unread) sit above the list. Tap a pill to narrow the list to what needs attention right now. The Unread pill is always shown, and says “You’re all caught up” when nothing is unread. Pinned conversations are always grouped at the top, so there is no separate Pinned pill.
• Lists group conversations by project or area of focus, and each one is a pill beside All and Unread. See Lists.
• A dot on each row signals status: a pulsing dot while an agent is working, a still dot for unread messages, and none otherwise.
• Recency labels on the right of each row show when each conversation was last active: HH:MM for today, “Yesterday”, day name for 2 to 6 days ago, or DD/MM/YYYY for older. Working conversations show the pulsing dot.
• Pinning keeps important conversations at the top of the list and marks them with a pin beside the title. Pin lives in the hover button on active-session items in the sidebar.

​

Lists

Lists group conversations by project or area of focus: a launch, a client, hiring. Each list is a pill beside All and Unread, and clicking it narrows the sidebar to the conversations in that list.

• Create a list. Right-click a conversation, type a name in the New list… field at the foot of the menu, and press Enter. The list appears as a pill with that conversation already in it. A name can be up to 60 characters. Typing the name of a list you already have, in any capitalisation, creates nothing; choose that list from the menu instead.
• Add a conversation to a list. Right-click the conversation and choose the list. A tick marks every list the conversation is in. A conversation can be in several lists at once, so adding it to one leaves it in the others.
• Take a conversation out of a list. Right-click it and choose the ticked list again.
• Filter by list. Click the list’s pill. Pinned conversations still sit at the top, and All shows everything again. Archived conversations keep their lists, but stay in the Archived section whichever pill is selected.
• Delete a list. Right-click its pill and choose Delete list “Name”. The conversations stay where they are; they only leave the list. If that list was selected, the sidebar returns to All.

There is no rename. To change a list’s name, create a list with the new name, add its conversations, and delete the old one. Lists are kept per workspace. The lists themselves are in .rundock/lists.json, and the lists each conversation belongs to are stored with it in .rundock/conversations.json. Like the rest of .rundock/, they travel with the workspace folder when it syncs, and stay out of a git repository, so each person on a shared workspace keeps their own. See What syncs, what stays local.

​

Where they live on disk

A workspace’s conversation index lives at .rundock/conversations.json as a single JSON array. Full message transcripts live under .rundock/transcripts/<conversationId>.json, one file per conversation, including every agent that took part in it. Conversations are workspace-local. They do not sync across workspaces, and they are not pushed to any external server. See Workspaces for the full directory layout.

​

Where to next