SESSION WORKFLOW GUIDE

New task in Chats.
Follow-up in the Thread.

The two composers do different jobs. Choose the right one to keep the task context you need.

Create an independent session

Enter “Help me plan a product launch” below the Chats list. DSH Slack UI creates a new session and adds it to history. Send “Help me plan a workshop” in the same composer to start a separate task.

Continue the same Thread

Select the launch task. In its Thread composer, send “The screenshots are ready. Update the checklist.” That reply uses the launch session. Sending it in the Chats composer would start a new session.

Read titles, summaries, and TODOs

Titles come from DSH session metadata. Summaries use committed assistant text, excluding reasoning and unfinished stream fragments. TODO progress comes from native todo/write events shared with the full task panel. Sessions without tasks do not receive invented progress.

Reload and return to native DSH

After a reload, host persistence restores the selected session. Choose Native DSH for Settings and Plugins, then Open DSH Slack to return. Unsent root drafts survive this switch.

Understand the context boundary

A Thread keeps the context of its own session. This version does not implement cross-session channel memory, shared human channels, or mention-only execution.