Check and Clear Saved Browser Sign-ins from the CLI

Use the CLI to check whether an agent has saved browser sign-ins or to clear them. The status response reports metadata, not the cookies or other sign-in data. Sign in with wallfacer auth login, then find the account ID and agent user ID. wallfacer agents list <account-id> lists the account's active agents.

Check the saved state

wallfacer agents list-browser-state <account-id> <agent-user-id>

The response's data.status is empty, saved, in_use, clearing, or unavailable. in_use means one of the agent's browsers is running with the saved sign-ins. clearing means a browser that held them is still being stopped. unavailable means the saved sign-ins could not be restored, so the browser started signed out.

data.saved_at gives the last save time when one exists. data.generation increases when sign-ins are cleared, so you can use it to distinguish a response from before a clear. Check data.reason_code for a restore or save failure, including a state that was too large to save.

Clear the sign-ins

Clearing requires the account admin or owner role:

wallfacer agents browser-state <account-id> <agent-user-id>

This deletes the agent's saved sign-ins and stops a browser currently using them. The next browser starts signed out. If the command returns status: clearing, run list-browser-state again until the status changes. Repeating the clear is safe.

Saved sign-ins normally carry into the agent's later sessions and new sandboxes. See The Agent's Browser for how saving works when the same agent has concurrent sessions, and the API Reference for response fields and status codes.