Browser automation and web navigation plugin for Claude, Cursor, and OpenCode IDEs. Provides Chrome daemon control, cookie/intercept inspection, PDF/screenshot generation, and site profile injection for web navigation memory.
Tandem is a browser automation plugin with 8 tools. Most tools have descriptions (6/8), but naming is inconsistent (tandem-* prefix mixes with bare names like 'fingerprint'), and schemas are incomplete or inferred. Tools 6-8 (hook/adapter tools) lack visible input schemas in source, only hookInput objects are documented. Parameter descriptions exist but are sparse. No output schemas documented. Error handling guidance is absent. The server appears to be a collection of scripts rather than a cohesive MCP server with formal tool registration.
OpenCode plugin for tandem:map profile injection. Hooks tool.execute.after to inject profiles on browser_navigate and cleans up session markers on session.deleted events.
Structural drift detection by route. Captures or checks the skeleton (roles/controls/headings) of a page to detect structural changes in site profiles. Emits {status, added[], removed[]} on comparison.
PostToolUse hook for tandem:map (Claude Code). Injects site profiles into model context when navigating to a host with a saved profile. Marks injections per (session, host) to avoid re-injection.
Cursor adapter hook for tandem:map profile auto-injection (postToolUse on browser_navigate). Resolves adapter data dir and formats Cursor's output envelope.
Wrapper to invoke the Chrome daemon by name from slash commands without depending on ${CLAUDE_PLUGIN_ROOT}. Controls the shared Chrome instance (start/stop/restart/status).
Extract cookies from tandem's Chrome via Chrome DevTools Protocol. Supports filtering by domain, multiple output formats (list, json, curl, headers, netscape), and optional plaintext value revelation.
Tools 6-8 (hook/adapter tools) have no visible input schemas in source code. Only hookInput object structure is documented in descriptions, not as formal JSON Schema.
Inconsistent tool naming: 'tandem-browser', 'tandem-cookies', 'tandem-intercept', 'tandem-pdf' use hyphenated prefixes, but 'fingerprint', 'hook-inject-profile', 'inject-profile', 'TandemMapInject' do not. LLMs struggle with inconsistent naming conventions when selecting tools.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields without knowing what each tool returns.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
HTTP sniffer for tandem's Chrome via CDP. Captures request+response with full bodies from the active tab. Supports start (with duration/tab selection), show (with filtering by URL/method/status/MIME), clear, and count operations.
Generate PDF or full-page screenshot of the active tab via CDP. Attempts Page.printToPDF first (headless Chrome only); falls back to full-page screenshot on headful Chrome.
No error handling guidance. Tools lack descriptions of failure modes, recovery steps, or actionable error messages. E.g., tandem-browser 'start' command does not document what happens if Chrome is already running or if the daemon fails to start.
Tool 'fingerprint' has ambiguous naming. Does not start with action verb (get_, create_, check_). 'fingerprint' alone is a noun; LLMs may confuse it with a data structure rather than an action. Should be 'check_fingerprint' or 'capture_fingerprint'.