Find your browser
Ask: “List my connected browsers and tell me which one you will use.” Choose the intended browser if more than one is paired.
← Pilot browser servicePilot.
Chrome extension / Standard
Pilot.
Your browser,
connected.
A flexible route from your AI client to the Chrome sessions you already use.
Official extensions available. Full production onboarding under verification.
01 / Install & pair
From extension to connection.
- 01
Create or sign in to your account
Use the same GhostStack account in your MCP client and extension. Open Apparatus from your account and check that Pilot access is enabled.
Create a GhostStack account ↗ - 02
Install one official variant
Open the Chrome Web Store listing, choose Add to Chrome and review the requested permissions. Use one variant for a pairing session to avoid confusing browser connections.
Install Pilot for Chrome ↗ - 03
Pair your browser
Open the extension, choose Pair browser and complete Identity sign-in. Check the account and browser name before confirming. Enable the session when you are ready to work.
- 04
Allow a test domain
Add a domain you control or are authorized to use. Start with read access. Grant act access only when you want the agent to click, type or submit, and review sensitive-action approvals.
Understand permissions & limits ↗ - 05
Connect your MCP client
Add a remote HTTP MCP server with the endpoint below and authorize it through Identity.
Connect Claude Code, Cursor or another client ↗https://apparatus.ghoststack.app/mcp/pilot
02 / First task
Start with a read. Then act.
Open an allowed page
Ask: “In your own agent window, open my allowed test page and summarize its headings.” The agent works in its own tab group; it cannot freely control your other tabs.
Try a reversible action
After granting act access, ask it to fill a test form without sending it. Inspect the result before approving a submission or any sensitive action.
Disable the extension session to stop access. Remove domain permissions or disconnect the browser when you are finished.
03 / Know your variant
Flexible input. Clear fallbacks.
Clicking
Both variants use paced, trusted browser input. Standard can fall back to a synthetic DOM click if debugger attachment fails; the tool result reports that fallback.
Form input
Standard fill assigns a field value and dispatches input/change events. For keyboard-dependent fields, use the type or press tool.
Permissions still apply
Neither variant bypasses domain permissions, sensitive-action approvals or account limits. Trusted input does not prove human authorship, guarantee invisibility or override a site’s restrictions.
04 / Troubleshooting
Check the connection in order.
My browser does not appear
Check that Chrome is running, the extension session is enabled, and the extension and MCP client use the same account. Reopen Apparatus to confirm Pilot access, then reconnect the client.
The page or action is refused
Check the exact domain and whether it has read or act access. Use the agent’s own tab group. Review pending approvals instead of repeatedly retrying a blocked action.
Input fails or a field ignores text
Check whether the result reports a synthetic-click fallback. For fields requiring keyboard events, try type or press rather than fill. Do not use either variant to evade a site’s access rules.
A request hits a limit
Pilot currently allows 30 calls per rolling minute, two concurrent operations and two connected browsers per account. Wait for the window to clear or the current operation to finish. There is no monthly usage cap.