Browser

The Browser page is your control panel for everything operator + web. Three tabs:

• Sessions — cookies + login state for sites operators access on your behalf
• Local Browser — Guilde Connect tunnel that exposes your real Chrome to operators (with consent, per tab)
• Recordings — captured runs of operators driving a browser, for audit and replay

Sessions — log-in state without the password

Some operators need to log in to sites that don't have an API. The CRM your sales team still uses, the ops dashboard your team built five years ago, your supplier portal. Sessions let an operator borrow your logged-in state without handing over the password.

A session is a snapshot of cookies + storage for a single domain, captured from your real browser and uploaded to the guild over an encrypted channel. When an operator with the browser tool needs to log into that domain, it replays the session — same effect as if you opened that page yourself.

Two ways to capture a session:

1. Guilde Connect extension (recommended) — install the browser extension, log into the site normally, click Sync to Guilde. The extension uploads cookies + storage for that one domain.
2. Paste manually — paste cookies as JSON from a tool like EditThisCookie into the Sessions page. Same end result, slower and more error-prone.

Each row shows: domain, active/expired state, cookie count, last sync, extension version. Revoke session removes it; operators lose access on their next request.

Local Browser — the tunnel

The Local Browser tab uses the Guilde Connect extension to expose your real Chrome as a remote browser the operator can drive. Different from Sessions:

• Sessions = static cookies replayed in a headless browser on Guilde's side
• Local Browser = your live, interactive Chrome, driven over a tunnel

Operators use the local browser when they need your real browser state — open tabs, current page context, extensions, your real identity end-to-end. The tunnel is opt-in per session, with a green "connected" indicator while it's live.

Recordings — audit + replay

Every operator-driven browser run is captured. The Recordings tab shows the gallery: who ran, on what site, when, screenshots and events. Useful for:

• Auditing what an operator actually did
• Replaying a failed run to debug
• Sharing a "look what it did" demo

Privacy & trust

• Sessions are encrypted in transit and at rest.
• Guilde's servers can't see the cookie values without the guild's encryption key.
• Your password is never sent to Guilde — only the cookies issued AFTER login.
• Operators can't exfiltrate cookies — they can only call browser tools that internally use them. Cookie values aren't surfaced to operator prompts or output.

A session in a guild is a pile of trust. Anyone who can use the guild's browser tool can take actions on the connected site as you. Don't sync sessions to guilds where the operator scope you've granted is wider than what you'd want any team member to do as you.

What's next

• Integrations — prefer API-based access when available
• Actions — the underlying browser tool methods (browserOpen, browserStep, browserClose, …)