Anchor Browser

@anchor list all my active browser sessions and show me which profiles they're using

Found 3 active sessions: Session abc123 (Profile: work-testing) - Running for 14 minutes, last activity 2 minutes ago on staging.example.com Session def456 (Profile: default) - Running for 3 hours, last activity 8 minutes ago on app.client-portal.io Session ghi789 (Profile: qa-automation) - Running for 47 minutes, last activity just now on localhost:3000 All sessions are healthy. The work-testing session appears idle and may be a candidate for cleanup.

This example shows session monitoring across multiple profiles. Useful for teams running parallel browser contexts (testing different accounts, environments, or user states). Requires valid API key authentication; session data reflects only your account's activity.

@anchor fetch the full content of https://docs.example.com/api/webhooks in markdown format so I can summarize the webhook setup steps

Retrieved content from https://docs.example.com/api/webhooks (rendered as markdown, 847 words): # Webhook Configuration Webhooks allow your application to receive real-time notifications... ## Setup Steps 1. Generate a signing secret in your dashboard 2. Configure your endpoint URL... 3. Verify the webhook signature... [Full markdown content continues with code examples and troubleshooting sections] Content successfully extracted. Ready for summarization or analysis.

Demonstrates content retrieval for AI processing. Anchor renders JavaScript-heavy pages, making this more reliable than raw HTTP fetches for modern web apps. Note that some sites block automated browsers; you may need to use an authenticated session or profile with cookies for restricted content.

@anchor create a new profile called 'client-demo' from my current session def456, then end that session to save the state

Profile created successfully: Profile ID: prof_xyz789 Name: client-demo Created from: Session def456 Cookies preserved: 14 domains Cache size: 23 MB Session def456 has been terminated. All cookies, local storage, and cache from that session are now saved to the 'client-demo' profile. You can launch a new session with this profile anytime to resume exactly where you left off. Next time you need this authenticated state, reference profile ID prof_xyz789.

Shows profile persistence workflow — critical for maintaining logged-in states across sessions. This is a write operation that modifies your account's stored profiles. Useful when you've manually logged into a complex app and want to reuse that authentication. Ending the session is required to finalize the profile snapshot.

When Anchor wins for multi-account test coverage

A 3-person QA team needs to verify checkout flows across six customer account types (free trial, paid monthly, enterprise SSO, etc.) every sprint. Anchor's profile management tools let you spin up a session per account, persist the cookies, and replay the same flow without re-logging in each time. The Get Webpage Content tool pulls the rendered DOM so you can diff actual vs. expected states in markdown. This works well up to about 20 profiles—beyond that, profile churn gets messy and you're better off with a dedicated test harness like Playwright. If your test matrix is under 20 accounts and you need human-readable page snapshots, Anchor cuts your regression cycle from hours to minutes.

When Anchor is overkill for support ticket triage

A 5-person support team wants to reproduce customer-reported bugs by loading the exact session state the user saw. Anchor's session persistence sounds perfect, but it requires the customer to share cookies or profile data, which is a non-starter for privacy and compliance. The List All Sessions Status tool only shows your own authenticated sessions, not arbitrary user states. You'd need the customer to manually export their profile, then import it into your Anchor account—a workflow most users won't complete. For support triage, a screen recording tool like Loom or a session replay service like LogRocket is faster and safer. Anchor fits if you're debugging internal staging environments where you control all the accounts, not production customer issues.

When Anchor handles light competitor monitoring

A 2-person growth team tracks pricing changes on four competitor SaaS sites weekly. Anchor's Get Webpage Content tool fetches the rendered HTML (including JS-loaded prices) and returns it in markdown, so you can diff week-over-week in a shared doc. The profile tools let you persist login sessions if competitors gate pricing behind sign-up walls. This scales to about 10-15 sites before the manual session management becomes a bottleneck—you're clicking through profile creation and session cleanup instead of writing scrape logic. If you're monitoring more than 15 sites or need hourly checks, a dedicated scraper like Apify is cheaper and more reliable. For a handful of high-value competitors checked weekly, Anchor gives you rendered content without writing scraper code.