Skip to main content
Some work needs a website, not an API: reading analytics a platform only shows in its app, checking how a profile looks, editing a document in a web tool, or replying to a comment. Daoco does that work in a browser profile, a signed-in browser session the brand keeps. It still prefers a platform’s API when one exists and uses the browser only for what the API cannot do or when you ask for it. Browser automation is on for every workspace.

What Daoco can do in a browser

  • Read. Open profiles and pages, collect posts and comments, read analytics the site shows, and pull details from a page.
  • Change things on a site you added. Edit a design or a document, fill a form, choose options, attach files from the brand’s library, save. The profile’s Access setting decides whether it asks first.
  • Act on a social account, one approved action at a time. Post, comment, reply, like, repost, follow, or send a message, each with its own approval. An approved post or message can carry images or video from the brand’s library.
Ask for it in brand chat, for example “read the latest numbers in our analytics dashboard” or “check our LinkedIn profile”. Daoco stays on the site’s own address. If the saved sign-in has lapsed, it tells you to sign in again from the Browser tab. It never asks you for a password or a code. What a task can do also depends on the platform, the account type, and the page at the time it runs. Supported social platforms: LinkedIn, Instagram, Facebook, X, Threads, TikTok, YouTube, and Bluesky. For any other site, add it as a site profile.

Cost

Browser use costs premium tokens: 1 when a task’s browser starts, then 1 more for every 10 minutes Daoco works in it. Time the browser sits idle and time you have control are free. The model’s own work still uses basic tokens. If the workspace has no premium tokens left, Daoco does not open the browser and says so. The Browser tab in the workflow panel shows how many premium tokens the browser has used. See Understand token usage.

Browser workflows

Three slash commands run common browser work on your connected social accounts. They use only accounts that have a browser sign-in, they only read, and you can watch them in the live view. Type / in brand chat to start one. If the browser cannot read the account or post, for example because it hits a sign-in screen, the answer says what to fix instead of guessing from public sources.

Sign in when a task asks

1

Start a browser task

Ask in brand chat. If the account or site needs a sign-in, Daoco shows a sign-in card.
2

Sign in yourself

Open the secure browser window and complete the login, account selection, MFA, or CAPTCHA yourself.
3

Return to Daoco

Confirm when prompted. Daoco saves the session and carries on with your request.
You can also sign in ahead of time from Connections > Browser. See Browser profiles.

Approvals

What Daoco may do without asking is set per profile with Off, Read only, Ask, or Allow, on top of the brand’s approval preference. The full rules, including what always asks and what is never done, are in Choose what Daoco may do. When a browser task needs approval, the thread shows an approval card and the task waits. Workspace owners and admins approve. What runs after you approve is exactly what the card showed. One approval covers one action. If Daoco rewords the text, that is a new action with a new card. A task approved for edits that reaches a Publish or Delete button stops before touching it and asks for that button by name. Changes you allow ahead of time are listed under the profile on the Browser tab, with Revoke. Removing the profile removes them too.

Approve by typing

You can type “approve” (or “yes”, “go ahead”, “lgtm”, and similar) in the thread instead of using the card, as long as exactly one approval is waiting. With more than one waiting, none is answered and Daoco asks you to use the cards. Typing anything else while an approval is waiting closes it without running, and the thread carries on from your message. Approving continues the same browser task. Daoco does not start over.

Watch the browser live

When Daoco starts a browser task in a saved browser profile, the workflow panel on the right gets a Browser tab that shows the browser as Daoco works. You only watch by default: the tab shows the latest screenshot of the page and the address it is on, and updates after each step Daoco takes. The live, clickable browser opens only for the person who takes control. Quick lookups that do not need your saved session, such as reading a single public post, have no live view. The live view is in the dashboard only, not in the team assistant’s channels.

Take control and hand back

Click Take control to use the browser yourself, for example to dismiss a prompt Daoco is stuck on or to sign in again. Daoco stops acting in that browser while you hold it:
  • If Daoco is between steps, the browser is yours straight away.
  • If Daoco is in the middle of a step, it finishes that one step first. The panel says “Daoco is finishing its current step. You get control next.” Cancel withdraws the request.
  • Daoco ends its turn with a short note on what it completed, and waits.
Click Hand back when you are done. If Daoco has stopped to wait for you, this sends a message in the chat asking it to look at the page again and continue. It carries on in the same browser, still signed in. What carries over. When your control ends (you hand back, the time runs out, or the run is stopped), Daoco closes the browser you used, so the live link you had stops working, and opens a fresh one from the same saved sign-in when it continues. This takes a few extra seconds. Daoco is not told what you did; it looks at the page again. Anything saved to the account or the sign-in carries over, such as signing in or dismissing a prompt. The page you navigated to and anything you left unsaved on it do not. The 10-minute hold. You can hold the browser for up to 10 minutes, or less if the session is already old, because a browser session lasts 30 minutes. Two minutes before your time runs out, the panel says when control ends and offers Keep control, which gives you another 10 minutes as long as the browser has that long left. If the time runs out, control goes back to Daoco and the panel shows Continue, which resumes the work the same way Hand back does. Stop. Stopping the run from the chat ends any hold and closes the live view. One person at a time. Everyone else on the thread sees who has control and keeps watching the latest screenshot. Only the person holding it can hand it back. While an approved action runs, such as a post with its exact text, a publish, or a delete, Take control is off, so nothing you do can change what was approved. It comes back when the action finishes. A task that only reads or edits can be taken over at any time. What you do while you hold the browser is your own action. It needs no approval and is not checked against the profile’s settings. The live view closes when the task finishes, fails, or the browser has been idle for about five minutes. The tab then shows Session ended with the last screenshot Daoco kept. If the browser closes while you hold it, the panel says so, and Daoco opens a new one when you ask it to continue. Anyone with access to the brand can open the thread, watch, and take control while the session is live.

Replays

When replays are turned on for your workspace, Daoco keeps a video of each browser session it drove. A few minutes after the session ends, Session ended shows a Replay button, with one video per browser tab. While Daoco is still copying the video, the tab says Preparing replay…. Under the video, Console and network lists what went wrong on the pages: console errors and warnings, requests that failed, and the pages visited. Addresses are kept without their query strings, and no request contents, headers, or cookies are kept.
  • A replay shows whatever the browser showed, including the signed-in account. Anyone with access to the brand can watch it from the thread.
  • Replays are deleted after 30 days, and when the brand is deleted.
  • Replays are off unless they have been enabled for your workspace. Sessions from before then have no replay, and a session whose video is very long or could not be recorded shows the last screenshot only.

Review browser evidence

A specialist’s view shows the browser steps Daoco completed, links it visited, screenshots it kept, and whether a result was complete, partial, blocked, or failed. Click the specialist’s row in chat to open its view and check this before you rely on a browser result or approve another action.
An uncertain browser write is not retried automatically. Check the destination before trying again so you do not create a duplicate post, comment, or reply.

Safety boundaries

  • Daoco resolves the social account or site profile, who owns it, and which addresses it may open on the server.
  • Navigation stays on the platform’s own addresses, or the one address of a site profile.
  • Every click, key press, field, option, and file is checked against what was approved before Daoco touches it. Daoco acts only on an element it can identify exactly; if a page shows two matching buttons, it stops and looks again instead of picking one.
  • When a site asks “Are you sure?”, accepting counts as pressing the button the question describes, so “Delete this post?” needs the delete approval.
  • Files Daoco attaches come only from the brand’s library.
  • Passwords, cookies, tokens, authorization headers, recovery codes, and MFA values are left out of evidence.
  • Login challenges stay in the secure browser window for you to complete.
  • A browser session lasts at most 30 minutes. A saved profile can be removed from Connections > Browser, which deletes the saved session.
For platform publishing and analytics caveats, see Platform support and limitations.