Brand chat

Brand chat is the conversational workspace for most daoco work. Ask naturally, attach files or assets, or use slash commands when you want to start a specific workflow.

​

What brand chat can do

• Write and revise on-brand copy.
• Generate, edit, and resize visuals.
• Create draft social posts and prepare publish approvals.
• Run research, SEO, campaign, clipping, and analytics tasks.
• Open workflow panels for richer review and editing.
• Refresh brand context after you approve the proposed changes.
• Work with connected integrations when the workspace has them enabled.
• Copy structured text blocks, such as hooks or campaign copy, directly from assistant responses when daoco renders them as copy cards.
• Pause, resume, stop, retry, or queue follow-up instructions while longer work is running.
• Follow a live, turn-by-turn execution ledger and stop an individual delegated branch when the control is available.
• Review large connected-tool tables in a dataset panel instead of reading raw provider output in the transcript.

​

How chat routes your request

daoco uses one main chat thread for most work. When you send a message, daoco decides the best specialist for the job:

1. Slash commands. A command such as /post or /research starts with that specialist. See Assistants and slash commands.
2. Follow-up in the same workflow. A continued post, clip job, campaign, or brand refresh stays with the active workflow instead of restarting.
3. Natural language. For everything else, daoco interprets the request and may run one specialist or a short sequence, such as research before writing.

Complex requests can run as specialist runs inside the same thread. The execution panel lists the planned steps, current work, completed work, and anything waiting for you. The final result stays in chat and, when needed, in a panel on the right.

​

Control active runs

Long-running work can involve research, publishing checks, campaign planning, or specialist tasks. When a run is active, the composer can show controls for the current state: Some pauses are waiting for a required action, such as an approval, reconnect, or browser auth. Complete the card shown in chat instead of using Resume for those pauses.

​

Send follow-ups while work is running

You can send another instruction before the current run finishes. The follow-up appears immediately as a queued message in the transcript. When the active run is safe to steer, a plain-text follow-up can guide its next step without waiting for a second turn. If the run is compacting, paused for approval, using an active specialist, or otherwise cannot be steered, daoco keeps the message queued. Compatible plain-text messages can be combined into one follow-up turn; messages with attachments stay separate. Use Cancel to remove a queued follow-up. Use Interrupt when available to stop the current run so the queued message can run next. If you paused the run yourself, queued follow-ups wait until you resume.

​

Work safely

daoco asks for confirmation before sensitive actions such as publishing, scheduling, applying brand updates, or making provider changes through connected integration tools. The approval card identifies the requested operation, target connection, and relevant scope. Review those details with any previews, diffs, attachments, and dates before approving. Approving an ordinary provider write runs exactly that action and also lets daoco keep making updates on the same provider for the rest of the thread without asking again, so one approval covers the whole job. Destructive changes, such as deleting something in a connected app, are always approved one at a time. The shield toggle in the composer turns on Bypass approvals for the current thread: gated actions, including publishing, run without asking until you turn it off. Turning it on while a connected-app write approval is already waiting answers that approval too, so the paused run resumes on its own; other kinds of waiting approvals keep their card and still need your answer. Deletes still ask, actions that always require confirmation (like a paid final render) still ask, and a connection that is turned off or read-only still refuses. The toggle is per thread, requires the workspace owner or admin role, and stays on across refreshes. Turning it off also withdraws the provider access the thread was granted while it ran open, so the thread goes back to asking. A workspace admin can turn the feature off entirely under Settings → Team → Approvals, which hides the toggle and puts already-bypassed threads back to asking. Brand owners and admins set approval preferences per brand. Ask before acting is the default. Work autonomously allows ordinary connected-app updates without asking, while Full autonomy can also publish and send. Per-connection exceptions can make access stricter or allow ordinary updates on one connection.

​

Browser auth for social tasks

Browser automation can use a secure browser session for supported UI tasks on LinkedIn, Instagram, Facebook, X, Threads, TikTok, YouTube, and Bluesky. When required, daoco shows a browser auth card in chat. Open the secure browser, sign in to the selected platform, then confirm on the card so daoco can resume the request. You can clear the browser session from Connections without disconnecting the platform’s OAuth or API connection. See Browser automation.

​

Chat activity signals

When a background run finishes in another thread, the sidebar can highlight that thread until you open it. This is useful for long research, scheduling, brand refresh, and generation work that may complete after you switch surfaces. While a turn is running, the transcript shows a single live status and elapsed time. The execution panel breaks the request into plain-language steps such as Understanding the request, Researching, or Writing the copy. A required approval changes the relevant step to Waiting for you. Finished turns keep their duration and can be reopened in the ledger. The composer context meter shows current context pressure and, once usage has been billed, how many basic tokens the thread has charged so far. Hover it for in, out, and total thread usage. See Understand token usage. Stopped runs show a stopped state instead of a generic failure. Use Retry run when you want daoco to try again with the latest request. If a connected-tool step fails, daoco separates connection setup problems, expired authorization, provider refusals, and temporary transport errors when it can. A retry keeps the original connection and approval scope. Reconnect only when the recovery card says the provider authorization needs attention.

​

Use chat with product surfaces

See Workflow panels for the right-side review surfaces and Assistants and slash commands when you want explicit routing.