Quickstart
Go from opening d5s to a first useful result, then preserve the context that should matter later.
The fastest way to understand d5s is to complete one real task in a chat. You do not need to configure a project, agent, or automation first.
1. Start from the workspace home
Open your workspace and start a new chat. Describe the result you want, the relevant background, and any constraints. A useful opening request names the deliverable and the decision it should support, for example:
Review the attached customer notes, group the recurring objections, and create a short brief with the five issues we should address first. Show your evidence for each group.
If the work already belongs to a listed project, choose that project before sending. Otherwise, start directly: d5s creates an unlisted project behind the chat so files, memory, and artifacts still have a durable owner.
2. Add the right context
Attach files that are specific to this conversation. Put instructions or reference material that should affect future work in the project instead. This distinction prevents a one-off attachment from silently becoming standing context.
The composer also lets you choose the model, reasoning level, available tools, and approval mode. Keep the default Ask for approval mode when you want connector actions configured to Ask to pause. Choose Allow all only when you are comfortable letting those actions continue for the whole session without individual prompts. Explicit Deny rules and connector or network boundaries still apply.
3. Review the result
Follow progress in the conversation. A run can show tool calls, generated files, sub-agent work, research progress, and connector approval requests. In Ask mode, approve a requested connector action once (valid for 15 minutes and consumed by one call) or for the session (valid for up to 24 hours) only when the requested action is appropriate. Switching the conversation to Allow all does not create one of these durable tool approvals; it applies only while that session remains in Allow all mode.
Continue in the same chat while the goal is changing. If a second message arrives while work is active, d5s records it as another turn and either joins it to the current work cycle or queues it for the session; the UI shows the applicable state.
4. Keep what should last
Use Save as project when the chat has accumulated context you want to find and reuse. This promotes the existing project; it does not copy the chat or move its files into a new container.
Then choose a work mode: keep the conversation as a chat, staff an agent for an ongoing responsibility, create an automation for a defined job and trigger, or create a dashboard when the maintained output matters more than the transcript.