Threads, groups, and collaboration

Bots and threads

A bot is a durable agent identity. A thread is one conversation with that bot and has its own transcript, model, provider session, approvals, costs, and running state. Optional folders organize related threads without duplicating the bot's memory or skills.

Use separate threads when you want fresh context or independent work without duplicating the bot. Messages sent to a busy thread are queued, and supported providers can be steered while they work. Other threads can continue independently. See Bots, folders, and threads for limits and shared-resource behavior.

Groups

Groups bring several bots into one conversation. Each participant keeps its own provider state. Group timeouts prevent a participant from blocking the whole group indefinitely. Existing channels and their thread histories remain intact; the new label does not change turn-taking or delegation.

Delegation

Bots can hand work to other bots. Delegated runs carry explicit status back into the parent conversation, including completion, failure, and cancellation.

Rewind and branches

Editing an earlier message creates a new conversation path. Dash Bot avoids resuming stale provider sessions after a rewind, so the next turn follows the visible branch rather than hidden abandoned state.

Memory and working folders

Bot memory is visible and editable. A bot may also have a dedicated working folder; groups can use a shared working folder. Cloud workspaces use a stable default so generated files remain discoverable across threads. A sidebar folder is only organization, not a working directory or a permission boundary.