Import a login profile
Copy supported Chrome or Safari login cookies into the browser so you and an agent can use those sessions. The source browser stays unchanged. This is a cookie import: passwords, passkeys, bookmarks, history, extensions, localStorage, IndexedDB, and device-bound credentials do not migrate.
Import from the app
- Choose Import Browser Profile from the Browser menu or the inspector's Agent Connection pane.
- Select Chrome or Safari and a source profile.
- Choose Import Cookies. The imported profile becomes active and open tabs reload.
- Open the sites you need and check their signed-in state. Some sites require a fresh sign-in even after cookies are copied.
You and agents share the active profile. Switching profiles reloads open tabs; in-page drafts and back/forward history are not transferred when tabs are recreated.
macOS permissions
Chrome imports may prompt for normal Keychain access to Chrome Safe Storage. If macOS denies access to a browser's profile folders, enable Beacon in System Settings → Privacy & Security → Full Disk Access, then quit and reopen the app.
Quit Safari before importing so it writes its latest cookies to disk. Safari's browsing-data export ZIP does not contain login cookies and cannot substitute for this import.
Discover profiles from the CLI
These commands list source profiles and saved imported profiles:
beaconctl profile.discover '{"browser":"chrome"}'
beaconctl profile.discover '{"browser":"safari"}'
beaconctl profile.list
Run beaconctl skill show for the installed profile.import, space.create, and space.useProfile arguments. Connecting a profile to an existing task requires control of that task.
Session persistence
Persistent cookies live in the profile's WebKit store. Imported session cookies are saved in the app's Keychain item and updated when cookies rotate or are deleted. Profiles survive restarting the app; use the packaged application consistently because development executables can have a different WebKit storage identity.