Skip to main content
Browser automation is a workspace-gated preview for authenticated social tasks that need a platform’s website. daoco still prefers native platform APIs and uses the browser only for an authenticated UI gap or an explicit UI fallback.

​
Supported platforms

  • LinkedIn
  • Instagram
  • Facebook
  • X
  • Threads
  • TikTok
  • YouTube
  • Bluesky
The same Browser automation preview toggle controls browser auth and browser-backed tasks for all supported platforms.

​
Supported work

Browser-backed reads can inspect profiles or pages, collect posts and comments, review UI-visible analytics, and run limited extraction steps. Browser-backed writes are limited to posting, commenting, and replying with the exact approved text. Available work still depends on the selected platform, account type, authenticated session, and the page state at the time of the run.

​
Complete browser auth

1

Enable the preview

A workspace owner or admin enables Browser automation under Settings → Preview features.
2

Start a browser-backed task

Ask in brand chat. If the selected social connection needs browser auth, daoco shows a browser auth card.
3

Sign in securely

Open the secure browser window and complete the platform’s login, account selection, MFA, or CAPTCHA yourself.
4

Return to daoco

Confirm the completed login when prompted. daoco verifies the session and resumes the original request.
You can review or clear a saved browser session from the connected social account in Connections without disconnecting its OAuth or API connection. Clearing it means the next browser-backed task will ask you to authenticate again.

​
Review browser evidence

Specialist run cards can show the browser steps daoco completed, links it visited, screenshots it retained, and whether a result was complete, partial, blocked, or failed. Expand the run card to review this evidence before relying on a browser-backed result or approving another action.
An uncertain browser write is not retried automatically. Review the destination before trying again so you do not create a duplicate post, comment, or reply.

​
Safety boundaries

  • daoco resolves the social connection, platform, account ownership, and approved website origins on the server.
  • Browser navigation is restricted to approved origins for the selected platform.
  • Credentials, cookies, tokens, authorization headers, recovery codes, and MFA values are excluded from evidence.
  • Login challenges stay in the secure browser window for you to complete.
  • Live browser sessions are bounded to the operation; the saved browser profile can be cleared from Connections.
For platform publishing and analytics caveats, see Platform support and limitations.