An agentic browser harness: an AI side panel & orb in your own logged-in Chrome, Edge, Arc, Brave or even Firefox run by the agent/subscription you already use (Claude Code, Codex, Antigravity). Free, open source, no API key. Also an MCP server.
TypeScript agentic-browseragentic-browsingagy-cliaiai-agentai-browser-extensionai-toolsbrave-extensionbrowser-agentbrowser-automationbrowser-extensionbrowser-usebrowserskillchrome-extensionclaude-codecodexfirefox-addonmcp-servernanobrowserweb-automation
chore(yarn): ignore Yarn 4 project state, keep the vendored release
Shahriar3beca061b43a
diff --git a/.gitignore b/.gitignoreindex a6fffd2..1e2abe1 100644--- a/.gitignore+++ b/.gitignore@@ -1,6 +1,16 @@-# Dependencies+# Dependencies. Both yarn.lock files (root and mcp/) are committed — mcp/yarn.lock is also+# what keeps `yarn --cwd mcp` a separate project rather than part of the root install.node_modules/+# Yarn 4 keeps per-project state in .yarn/, and there are two projects here. install-state.gz+# is a local cache; the package cache is global (enableGlobalCache), so nothing else lands+# here except .yarn/releases/, which holds the pinned Yarn binary that .yarnrc.yml's yarnPath+# resolves to — that one has to stay committed, or a fresh clone has no working Yarn.+**/.yarn/*+!**/.yarn/releases+!**/.yarn/patches+.pnp.*+# Build output — WXT writes to `dist/` (see outDir in wxt.config.ts); tsup writes to mcp/dist/.# The bare `dist/` pattern matches at any depth, so it covers both.dist/@@ -16,7 +26,9 @@ stats-*.jsonweb-ext.config.tsweb-ext.config.ts.timestamp-*-# `npm run mcp:link` artifacts: mcp/bin holds symlinks into mcp/lib/node_modules+# Stray `npm link` artifacts. `yarn mcp:link` links into the real npm prefix and writes+# nothing here, but the `npm --prefix mcp link` it used to run treated mcp/ as the *global*+# prefix and left self-referential symlinks (mcp/bin -> mcp/lib/node_modules) behind.mcp/bin/mcp/lib/