Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hydro13/tandem-browser
Use Tandem Browser's MCP server (local and remote agents) or HTTP API (local and remote agents) to inspect, browse, and interact with the user's shared browser safely. Prefer targeted tabs and sessions, use snapshot refs before raw DOM or JS, verify action completion explicitly, and leave durable handoffs instead of retrying blindly.
Passed 17 of 20 test cases with the skill, and 8 of 20 without it.
and 12 more in the full report
10 fixed9 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
An agent opened tab-505 and now needs to move this tab into a newly created workspace with ID 'ws-789'. Which specific identifier property from the open tab response must be passed in the body of POST /workspaces/ws-789/tabs?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies that webContentsId must be passed in the tab move request body. | Missed | Passed |
| Uses POST /workspaces/ws-789/tabs to relocate the tab into the designated workspace. | Passed | Passed |
The instructions your model reads when the skill loads.
Tandem Browser is a live human-AI browser environment for shared work in the user's real browser context.
Important: Tandem itself must already be running. The local API and MCP server are how an agent talks to a running Tandem instance, not alternatives to Tandem itself.
Agents work with a running Tandem instance through MCP or HTTP, depending on what the client supports in practice. For some clients, MCP is the primary or only realistic integration path.
Use this skill when the task should happen in the user's real Tandem browser instead of a sandbox browser, especially for:
Tandem supports agents on the same machine (MCP or HTTP) and on remote machines over a private Tailscale network (MCP or HTTP). Both can be active at the same time.
A running Tandem instance publishes its own version-matched bootstrap surface. This works for both local and remote agents, and does not require repo access:
GET /agent — human-readable bootstrap pageGET /agent/manifest — machine-readable endpoint manifest with all route familiesGET /agent/bootstrap — authenticated bootstrap contract with runtime context,
operating rules, and the agent toolboxGET /skill — version-matched usage guideGET /agent/version — version and capability summaryThese routes are public (no auth required) and use the request Host header,
so they return correct URLs whether accessed locally or over Tailscale on the
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.