Chats

Chats are the interactive work mode in d5s. A chat keeps one session while you and the agent shape the result through multiple turns.

You can start a chat from the workspace home without choosing a project. d5s creates an unlisted project for it automatically. Choose an existing project when the work should immediately inherit that project's instructions, files, memory, skills, and connector activations.

Use a chat when

• the question is exploratory or changing;
• you expect to review intermediate results;
• a tool action may need approval;
• the work should remain attached to one conversation;
• you want to prototype a prompt before making it repeatable.

During a run

The conversation streams the agent's progress rather than waiting for one opaque response. Depending on the task, you may see tool activity, sub-agents, research phases, generated artifacts, connector approval cards, and a request for access to an exact external API host.

The approval control beside the + menu has two modes. Ask for approval is the default and pauses when a connector action resolves to Ask. Allow all persists for this session and lets Ask actions continue without individual approval cards. It does not override an explicit Deny, change connector credentials, or expand the allowed host, method, path, sandbox, or network boundaries. Switch back to Ask whenever you want the next Ask action to pause again.

If an approval card is already waiting when you choose Allow all, d5s retries that action once. A failed retry leaves the card available so you can review or deny it manually.

An external API request is not access by itself. When the workspace policy allows member grants, the card shows the exact host, its ordinary-method and all-path HTTPS API scope, and the risk that the service may retain data, perform external actions, or return prompt injection. Nested CONNECT tunneling is blocked. Allow in this chat lasts only for that chat and can be revoked. Approve only a host you trust and never send credentials or other secrets.

Messages sent while work is active are durably admitted to the session. d5s may incorporate compatible new input into the current work cycle or show it as queued for a later turn. You can cancel a queued turn or stop active work without deleting the conversation.

Session uploads belong to this chat. Project files and memory belong to the reusable project context. Use Save as project when the hidden project behind a standalone chat should become a named, listed workspace resource.

Continue, branch, or repeat

Continue in the same chat when the new request depends on its history. Branch from a completed assistant response when you want to explore a different direction without changing the original thread. Start a new chat when the work should not inherit the old transcript.

Use the thumbs-up or thumbs-down icon on a completed agent response to mark it as helpful or unhelpful. Selecting an icon immediately saves your rating and keeps it selected even if you skip or close the optional details dialog. You can add reasons and a comment later, switch directions, or remove your own feedback.

The conversation shows only your own selection. It does not show teammate ratings, aggregate counts, or other people's feedback details. Feedback is not currently added to the agent's next-message context.

Manage a chat

Open Conversation actions from a manual chat in the project Recents list, the All sessions dialog, the Chats list, the History list, or the open-chat header. From there you can:

• Move to project to keep the transcript but attach future work to another project's context;
• Rename to change the conversation title; or
• Delete to permanently remove the conversation after confirming. Deletion cannot be undone.

These conversation actions apply to manual chats. Manage automation runs, dashboard runs, and agent conversations through their parent automation, dashboard, or agent instead.

Move stable patterns onward

Once the role or trigger becomes repeatable, the same project context can support a persistent agent, scheduled automation, or refreshable dashboard. Moving to another mode reuses the project; it does not turn the chat transcript itself into standing instructions unless you explicitly carry the relevant material forward.