agentleFS
EtanHeyEtanHey/golems/skills/golem-powers/agent-browser/SKILL.md

agent-browser

Skill0 starsChanged 15 days agoApache-2.0View on GitHub

Agent web testing: attach to shared Chrome Beta over CDP. Never launch worker browsers or drive Helium.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use time-skill, dep-refs and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Recepay6358Skill

    time-skill

    Display the current time in Pakistan Standard Time (PKT, UTC+5). Use when the user asks for the current time, Pakistan time, or PKT.

    Also in 6 projects that use this

  • betacatslingSkill

    dep-refs

    Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.

    Also in 5 projects that use this

  • betacatslingSkill

    feature-boundary-planner

    Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.

    Also in 5 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • Recepay6358Skill

    weather-svg-creator

    Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.

    Also in 6 projects that use this

  • +3 more from nicepkg

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 173 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always pass the same name to release: the default name is the calling shell's PID, which changes between commands.

    line 20
  2. Distinctive:

    Use the same name through cleanup, even if attach or tab creation fails:

    line 28
  3. Distinctive:

    Do not change or repin hooks-live for this installation.

    line 71

“Common” is measured: kept by at least 6 in 10 of the 173 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent browser

Choose the first option that works:

  1. An API or CLI when it gives the data: DeepSource → deepsource-issues; GitHub → gh.
  2. Pages needing no sign-in: a headless browser (or T3's browser tools when the task is browser work), leaving no window on Etan's screen.
  3. The M1's agent browser when the sign-in exists there. Use the M1 T3 environment or a delegate; see /agent-routing for cross-machine delegation.
  4. M4 Chrome Beta only when the M4 signed-in session is needed.

On the chosen Mac, run agent-browser start --lease <unique-task-name> before every CDP attach. If it fails, do not connect. The lease lasts 30 minutes; renew the same name with start --lease <name> --ttl 1h for longer work. Always pass the same name to release: the default name is the calling shell's PID, which changes between commands. Never touch another task's lease. status prints live leases; reap drops expired ones. The last release, or reaping all expired leases, stops the verified browser with SIGTERM. There is no background reaper (Etan, 2026-11-01): you close it. When your task ends, page.close() your tab and release your lease; if you are the last one, the browser quits. If you find a stale browser, run agent-browser reap. Never leave it running for other workers without their own live leases.

Use the same name through cleanup, even if attach or tab creation fails:

import { execFileSync } from 'node:child_process';
import { randomUUID } from 'node:crypto';
const lease = `task-${randomUUID()}`;
let leased = false, page;
try {
  execFileSync('agent-browser', ['start', '--lease', lease]);
  leased = true;
  const browser = await chromium.connectOverCDP('http://127.0.0.1:9333');
  page = await browser.contexts()[0].newPage();
  // Test using your own tab.
} finally {
  try {
    if (page) await page.close();
  } finally {
    if (leased) execFileSync('agent-browser', ['release', lease]);
  }
}

Open and close only your own tabs. Never call browser.close(), Playwright launch or launchPersistentContext on this shared signed-in browser. Chrome Beta starts with no window; newPage() opens your tab. Etan signs in by hand; never automate sign-in or clone/export the cookies. Serialize computer-use checks and use only Google Chrome Beta, never Helium.

The shared profile is ~/Library/Application Support/golems-agent-browser (0700), with .leases.json (0600), outside repos. CDP lets local processes read signed-in cookies: bind 127.0.0.1 only, never expose or forward 9333. The launcher refuses foreign listeners/profiles and corrupt lease files. stop refuses while live leases remain; release your own lease instead.

From any golems checkout, install once the reviewed source is in the installed hooks-live pin (Git resolves the shared repository location, including worktrees):

golems_git_dir="$(git rev-parse --path-format=absolute --git-common-dir)"
golems_repo="$(dirname "$golems_git_dir")"
ln -sfn "$golems_repo/.worktrees/hooks-live/scripts/agent-browser/agent-browser" "$HOME/.local/bin/agent-browser"

Do not change or repin hooks-live for this installation; its owner runs the normal reviewed-pin update. Until then, run the reviewed script by its full path.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.