SCRIPTMASTERLABS — GHOSTKEY SESSION BRIDGE v0.3 Purpose ------- Delegate narrow browser actions into a Chrome/Edge browser that YOU authenticated yourself. GhostKey does not receive your cookies, passwords, Google credentials, CAPTCHA answers, MFA codes, or password-field contents. GhostKey v0.3 supports two modes: 1. One-off session pairing — paste a short-lived session ID + bridge token for a single job. 2. Trusted browser identity — enroll this browser once with a device-local P-256 signing key so later short-lived sessions can be claimed without re-pasting a bridge token. Install page ------------ https://ghostkey-mcp.onrender.com/session-bridge/INSTALL.html Desktop setup (Chrome / Edge) ----------------------------- 1. Download GhostKey-Session-Bridge.zip from: https://ghostkey-mcp.onrender.com/session-bridge/GhostKey-Session-Bridge.zip 2. Extract the ZIP to a folder. 3. Open chrome://extensions or edge://extensions. 4. Turn on Developer mode. 5. Choose "Load unpacked" and select the extracted GhostKey-Session-Bridge folder. Trusted browser enrollment — recommended for your own Windows browser -------------------------------------------------------------------- 1. From GhostKey MCP call ghostkey_device_pairing_create. 2. In the extension popup, enter the returned pairing ID and one-time pairing code under Trusted device. 3. The extension generates a P-256 signing key. The private key is created non-exportable and stored in browser-local IndexedDB. Only the public key is sent to GhostKey. 4. After enrollment, call ghostkey_device_pairing_status with the same pairing ID + code before the 10-minute pairing capability expires. 5. That status returns the enrolled 256-bit device routing capability. Keep it private; do not publish it in pages, manifests, logs, screenshots, or listings. 6. For later jobs, call ghostkey_session_create with trusted_device_id plus ONLY the HTTPS origins needed for that job. 7. No bootstrap bridge token is returned for a trusted-device-targeted session. The enrolled browser proves its P-256 key, receives a short-lived device access capability, and claims the short-lived browser session itself. 8. If all job origins were already approved in this extension, the session can reconnect automatically. If a job introduces a new origin, the extension waits for YOU to approve that origin once. 9. Site authentication, MFA, CAPTCHA, consent, identity verification, and password entry remain manual. 10. Use ghostkey_session_revoke to revoke an individual action session. Use “Forget trusted browser” in the extension to revoke the durable browser identity and delete its local device key. One-off session setup --------------------- 1. In GhostKey MCP, call ghostkey_session_create without trusted_device_id and with ONLY the HTTPS origins needed for the task. 2. Copy the returned sessionId and bridgeToken into the extension popup and click “Validate session”. 3. Review the listed origins and click “Grant approved origins”. 4. Complete login, MFA, CAPTCHA, consent, or other identity steps manually in the browser. 5. After the extension reports Connected, the agent can use ghostkey_session_action for inspect/navigate/click/input/select/read/wait inside the allowlisted origins. 6. Revoke with ghostkey_session_revoke when finished. Security boundaries ------------------- - Every action session remains short-lived: 60 seconds minimum, 60 minutes maximum. - Origin allowlists are enforced independently by the server and extension. - New browser host permissions always require user approval. - A trusted browser may retain previously approved host permissions so later jobs for those same origins can reconnect without another Chrome prompt. This does NOT create a permanent action session and does not authorize any new origin. - Password, hidden, and common MFA fields cannot be read or filled by delegated actions. - Cookies and browser local/session storage are never exported. - CAPTCHA/Turnstile/KYC/MFA are not automated or bypassed. - Off-allowlist direct navigation, link destinations, and form destinations are denied where detectable before execution. - One-off agent and browser bridge tokens are separate random capability tokens. - Trusted-device targeted sessions do not expose a bootstrap bridge token. The trusted browser must authenticate its non-exportable P-256 key before claiming a fresh bridge capability. - The trusted-device routing ID contains 256 bits of randomness and must be treated as a private routing capability, not a public identifier. - Trusted-device persistent storage contains only the public key and bounded device metadata; browser credentials are not stored there. - Device challenge/access capabilities are short-lived. A GhostKey service restart invalidates in-memory device access grants and active action sessions, but the enrolled browser can re-authenticate its persistent public-key identity after restart. - The server reports bridge_connected only while the browser heartbeat is fresh. - If GhostKey persistent trusted-device storage is not configured or reachable, trusted-device enrollment fails closed. One-off sessions continue to work. MCP tools --------- ghostkey_status ghostkey_catalog ghostkey_policy ghostkey_device_pairing_create ghostkey_device_pairing_status ghostkey_session_create ghostkey_session_status ghostkey_session_action ghostkey_session_revoke Browser actions --------------- inspect Safe inventory of visible interactive controls and selectors. navigate Navigate to a URL only when its origin was explicitly allowed. click Click a selected control while denying known off-allowlist link/form destinations. input Enter text in a non-sensitive input, textarea, or editable element. select Choose an option from a select element by value or visible text. read Read selected non-sensitive content or a limited safe attribute set. wait Bounded wait for a navigation or UI update. Example origin set for Circle / PartnerPage ------------------------------------------- https://partners.circle.com https://directory.partnerpage.io https://login.partnerpage.io Google sign-in, CAPTCHA, and identity verification remain manual. Do not add accounts.google.com merely to automate login; GhostKey is not designed to automate or bypass authentication controls. Truth First. Proof Always. Pay Only for Accepted Delivery.