Activity page

The activity log is off by default. Off means off: the extension keeps no record of commands, and the Overview page hides its Operations and Errors counters. Each dashboard records activity for its own browser profile. Commands in other profiles and separate developer sessions do not appear here. Switch it on under Settings → Privacy → Activity log. From then on the extension keeps the last 200 commands in memory, never on disk, and the Activity page shows them newest first:

Column	Content
Time	When the command completed.
Agent	The MCP client name that issued it (for example `claude-code`, `codex`, `gemini`).
Tab	Title of the target tab.
Command	The DevTools Protocol method or bridge request, such as `Input.dispatchMouseEvent` or `tabs.create`.
Latency	Round-trip time in milliseconds, with a bar relative to the slowest command shown. Commands taking a second or more are highlighted.
Result	OK, or the error text.

Turning the log off clears it immediately. Restarting the browser also clears it because the service worker starts fresh.

The log shows protocol methods, not MCP tool names, because one tool call can fan out into several commands. For a tool-level view read the companion’s stderr, which logs each agent connecting and disconnecting, or ask the agent what it did.

Get started

Connect an agent

Concepts

Dashboard

Guides

Reference