Troubleshooting
The agent’s JavaScript call fails right after the form is submitted
Claude in Chrome reports Cannot access a chrome-extension:// URL of different extension or Detached while handling command.
Another extension, typically a password manager offering to save the password, took over the tab. The login itself still ran. The agent should call login_status to get the outcome; the MCP server’s instructions tell it to. Reload the tab if the browser tool keeps failing. A separate Chrome profile without password managers avoids the problem.
The agent ran the script twice
That is fine. The second run returns the first run’s outcome with the note “This one-time script already ran; this is the outcome of that run.” The credentials are not released again.
no_login_form
No visible password field was found within 5 seconds.
- If the result has
previous_loginwithsuccessorsubmitted, the tab is already logged in. This usually means the agent calledloginagain after its JavaScript call was cut off. Nothing to fix. - If the login form is inside an iframe, a shadow root or behind a “Log in” button, it is not supported yet. Open the form first, or see the roadmap.
- If the form is unusual, set
<PROFILE>_PASSWORD_SELECTOR(and the other selectors) for the profile. See Configuration.
failed although the credentials are right
- The heuristic may not find the right button. Set
<PROFILE>_SUBMIT_SELECTOR. - The app keeps the form on the page after logging in. Set
<PROFILE>_SUCCESS_SELECTORto an element that only exists when logged in. - The app validates the password before sending it (for example a minimum length). The
hintshows the page’s message.
rate_limited
Three logins for the profile failed within five minutes, so the profile is paused to protect the account from a lockout. Check the credentials with npx autologin-mcp list and fix them with npx autologin-mcp edit. The pause ends five minutes after the failures, or when the MCP server restarts.
origin_mismatch
The tab’s host does not match the profile’s root URL. Check the port (localhost:3000 does not match localhost:5173) and subdomains (example.com does not match app.example.com; use *.example.com). See URL matching.
The bridge script returns error … Content-Security-Policy
The app’s Content-Security-Policy blocks scripts from 127.0.0.1. Turn on chrome://inspect/#remote-debugging so autologin-mcp uses CDP mode, which is not affected by CSP.
Chrome asks to allow access to “apps and services on this device”
This is Chrome’s Local Network Access prompt. It appears once per site when a public site (for example a staging server) loads the bridge from 127.0.0.1. Allow it for your test sites.
browser_not_connected
Only with AUTOLOGIN_MODE=cdp. Remote debugging is off, or Chrome’s Allow prompt was dismissed. Enable chrome://inspect/#remote-debugging and retry, or set AUTOLOGIN_CDP_URL to a Chrome started with --remote-debugging-port.
ambiguous_profile or ambiguous_tab
Several profiles or several tabs match. The agent should call login again with profile, or with the exact url of the tab.
A harmless shell command is blocked by the hook
The guard hook blocks any Bash command that mentions the credentials folder, even ls. This is intentional. Edit the file yourself with npx autologin-mcp edit.
The agent does not call login
- Restart Claude Code after
install, and check thatclaude mcp listshowsautologinas connected. - Tell the agent once: “When the app asks for a login, use the autologin tool.”
A local .tgz build does not update
npx caches packages by spec. After rebuilding a .tgz with the same name, clear the matching entry in ~/.npm/_npx and run install again.