Skip to main content
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.

​
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 — If you include a command such as /post or /research, daoco starts with that specialist first. See Assistants and slash commands.
  2. Follow-up in the same workflow — If you are continuing a post, clip job, campaign, or brand refresh, daoco keeps the active workflow going instead of restarting from scratch.
  3. Natural language — For everything else, daoco interprets your request and may run one specialist or a short sequence, such as research before writing or writing before publishing.
Complex requests can run as specialist runs inside the same thread. You will see progress cards in the transcript while work is running, then the final result in chat and, when needed, in a workflow 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. Review previews, diffs, target accounts, connection context, attachments, and dates before approving. Brand owners and admins can set approval preferences per brand for scheduled social posts and integration writes. Both policies default to Auto when connected. Switch to Always ask or Learn after 3 when you want stricter control over scheduling and integration writes.

​
Browser auth for social tasks

The Browser automation preview 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 preview.

​
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, chat can show Queued, Understanding the request, Planning the approach, or Drafting so you can tell what daoco is doing before the first result appears. It may also show compaction when a long thread is summarized or a pause when approval is required. Background memory activity appears in the timeline when daoco saves a memory candidate, an active memory, or workflow guidance. 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.

​
Use chat with product surfaces

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