Explicitly share selected-tab debugging context with your local AI coding assistant
Users
10
0 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#196K
#164K among extensions
Version
1.1.0
updated 29 Aug 2026
Users
monthly, 10 months
Latest, 16 Oct 2026:10 usersMove the mouse over the chart for any month
Ratings count
monthly, 10 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Agent Logger
Agent Logger connects the browser tab you are debugging to MCP-compatible AI coding tools. It provides deliberate screenshots, selected element details, page errors, accessibility context, and browser actions without persistent access to other sites or tabs.
HOW IT WORKS
1. Sign in to Agent Logger and install the MCP runtime with the version-pinned @continuallabs/agent-logger@1.1.0 npm setup command for Claude Code, Gemini CLI, or Codex CLI.
2. Start your supported coding client. Its MCP process prints a short-lived pairing code in that terminal.
3. Select that runtime in the side panel and enter the terminal-visible code within two minutes.
4. Use Agent Logger on the active http(s) tab. Capture and element actions are deliberate. Error monitoring begins only when you click “Monitor tab” and ends when you stop it or that tab navigates.
5. Browser context travels over an authenticated loopback connection to your local MCP process, where your coding tool can request it.
FEATURES
• Viewport, full-page, element, and region screenshots
• Element selection with DOM, style, and accessibility context
• Opt-in console, exception, resource, and network-error monitoring for one selected active tab
• Accessibility inspection and page diagnostics
• Authenticated browser actions such as click, type, hover, and scroll
• Reviewable terminal staging that never presses Enter or submits text
SECURITY AND CONTROL
• The local bridge is limited to 127.0.0.1 and requires the Agent Logger extension Origin, exact protocol endpoint, versioned WebSocket subprotocol, explicit pairing, and session authentication.
• The MCP runtime independently verifies a signed, device-bound licence entitlement from the hosted service; changing local extension state cannot create a valid entitlement.
• Pairing codes are displayed only in the selected terminal, expire after two minutes, and are scoped to one running MCP process. Every new runtime must be paired again.
• Monitoring is not enabled by installation, sign-in, runtime discovery, or pairing. It applies only to the active http(s) tab selected by the user, and navigation revokes access.
• Project files and source code are not transmitted over the local WebSocket. Browser context can contain sensitive page data, so users should review what they capture or select. Agent Logger does not promise automatic redaction.
• Text sent to a supported terminal is staged for user review and is never submitted or executed by the staging operation.
ACCOUNT AND PAYMENT
Agent Logger account authentication and licence checks use the hosted Agent Logger service backed by Supabase. Paid access starts through Stripe Checkout, which collects and saves the card up front. Unless cancelled before the exact time shown in the dashboard, the card is charged automatically once, 48 hours later, for a final total of $25.00 USD. This grants lifetime access; it is not a subscription and does not renew. The extension never receives card details.
The extension is free to install. An active Agent Logger trial or lifetime licence is required for product features. Supported setup clients are Claude Code, Gemini CLI, and Codex CLI; generic MCP configuration is also available from the setup CLI.
Growth
Window
Users
Change
Ratings
Rating
7 days
−1
−9.1%
0
0.00
30 days
0
+0.0%
0
0.00
6 months
+2
+25.0%
0
0.00
Chrome Web Store search rankings
Where Agent Logger appears when people search the store, with the 30 day change