Skip to main content
Navigation

Pilot access. Official extensions available. Full production onboarding under verification.

Apparatus / Setup & reference

Pilot permissions and limits

Your browser is part of the connection

Pilot acts inside your paired Chrome browser, where websites may already have signed-in sessions. Browser commands and results pass through the GhostStack relay. Using a local AI model does not make that transport local.

Each caller has a scoped agent window and tab group. The caller cannot use an arbitrary tab from your personal window. The explicit adopt action is the path for moving a permitted existing tab into an agent group.

Read and act are different permissions

A domain allowlist entry has a read or act level. Start with read access. Act adds actions such as clicking and filling controls. A wildcard allows broad domain access; prefer specific domains for a first connection.

The extension session grant must be enabled. js_eval and cookies_read need additional approval unless a matching standing grant applies. Review the exact request in the extension. Standing grants can be revoked; they do not bypass the session grant or domain boundary.

Act permission can allow website changes. Do not assume every click or form submission creates a separate approval prompt.

Free account limits

LimitFree Pilot access
Tool calls30 per rolling minute
Simultaneous browser operations2
Connected browsers2
Monthly usage capNone

These limits apply across the account, not separately to each client or workspace. An operation holds a concurrency slot while it executes. No monthly cap does not remove the per-minute or concurrency limits.

Select the right browser

When several browsers are connected, use the browsers tool to inspect them. Specify the target browser or set a default. Permissions and approvals stay with the selected browser.

Stop and verify

Disable the session grant or use the extension’s disconnect controls when finished. For a running operation, request cancellation and wait for its terminal status. A timeout or lost connection does not prove a website action was rolled back. Inspect the page before retrying a write.

Pilot can dispatch input and report execution without proving that a website accepted a form. Verify the site’s confirmation or receipt before treating a submission as successful.