glim-sh

Cuttle — Testing skill for Claude Code

Testing community

cuttle is a browser for your agent.

How to install Cuttle

This entry records only its repository, not the path inside it, so there is no exact command to give. Open glim-sh/cuttle and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Cuttle does

cuttle is a browser for your agent. Websites do not block it. It keeps your logins. When a website asks for a person, you can take control. It works with playwright-cli, agent-browser and browser-use.

Alternatives in Testing

Playwright — claude-plugins-official Browser automation, E2E testing, screenshots 29.4k ★
Playwright — Automate real browser interactions for navigation, forms, and scraping 14.6k ★
Deslop Reborn — One iteration of the IronClaw Reborn de-slop loop — take ONE Reborn crate, fan out parallel review sub-agents 12.6k ★

README

cuttle

Your agent's stock browser fails on the real web. Sites show captchas, Cloudflare walls and "verify you are human" pages. The browser forgets every login when the process ends. You cannot see what the agent sees. cuttle is a browser for your agent that fixes these three problems:

Not blocked. The browser is a patched Chromium build that looks like a normal person's browser, with one consistent identity: fingerprint, proxy, IP location, locale and timezone.
Stays signed in. Sign in once through the viewer. The login persists across agent sessions and across restarts.
You can step in. A built-in viewer shows the live browser. When a site wants a human, you solve the captcha or 2FA yourself and the agent continues.

It works with playwright-cli, agent-browser and browser-use.

Why not Claude in Chrome or ChatGPT?

They overlap a lot: all three use a real browser, keep your logins, pass bot walls, and read pages fast. The difference is control. As of 2026-08:

	cuttle	Claude in Chrome	ChatGPT
Banking, tax, government, work accounts	your call	discouraged by policy	gated, auto-pauses
Cookies, response bodies, replay from your code	yes	no	no
Identities at once	one per container (pool mode for many)	one profile, manual switch	one shared profile
Who can drive it	any CDP client	Claude only	ChatGPT only
Where it runs	your Docker, server or k8s	your desktop Chrome	OpenAI's cloud
Take over when a site pushes back	any browser or phone	at that desk	desktop web only

The row that matters most is the second one. Reading the full cookie jar, seeing request and response bodies, and calling any origin is what lets an agent work out a site's own API and then replay it from your code. Neither extension exposes that.

Not a reason to choose cuttle: persistent logins, bot walls, page-reading speed, password-manager sign-in. All three do those.

**How it works.** cu