2 Commits

Include renames

Author	SHA1	Message	Date
leeguooooo	61060486f4	rebrand: agent-browser-stealth → chrome-use, de-fork, reset to v1.0.0 ... Standalone product rename across the whole repo (issue: project identity): - Binary/package/repo/skill/docs: agent-browser[-stealth] → chrome-use (single binary name `chrome-use`; old aliases agent-browser/abs dropped). - Version: 0.27.0-fork.51 → 1.0.0 (drop the upstream-fork counter). - Native-messaging host: com.agent_browser.connect → com.leeguoo.chrome_use (CLI + ab-connect extension in lockstep — this is a breaking handshake change, extension bumped 0.4.2 → 0.5.0, needs a Web Store republish). - Config dir: ~/.agent-browser → ~/.chrome-use. - README/zh: reframed from "stealth fork of agent-browser" to a standalone product with a small `originally based on vercel-labs/agent-browser` credit. - Kept AGENT_BROWSER_* env vars working (63 vars across the codebase; renaming them would break every existing script/skill for no user-facing gain). Build green, 802 unit tests pass, fmt + clippy clean. Upstream attribution to vercel-labs/agent-browser preserved.	2026-06-12 12:56:21 +09:00
Chris Tate	4cc6ca40b7	feat(skills): rename "agent-browser" skill to "core"; make CLI-served main skill actually useful (#1253) ... Before this change, the main skill served by the CLI (`agent-browser skills get agent-browser`) was a ~40-line discovery stub whose content was essentially "run `agent-browser skills get <name>` before doing anything." Agents already inside the CLI got no signal from it — the content they needed to actually use the tool lived only in the `--full` references. Split the two jobs apart: - **`skill-data/core/`** (new) — the runtime usage guide. 420-line `SKILL.md` covering the snapshot-and-ref loop, common workflows (login, extract, screenshot, multi-tab, sessions, iframes, dialogs), waiting strategies, element selection strategies, troubleshooting, and when to load a specialized skill. Supplementary `references/` and `templates/` (moved from `skills/agent-browser/`) provide the full command reference under `--full`. - **`skills/agent-browser/SKILL.md`** — still the discovery stub that `npx skills add` installs, now marked `hidden: true` so it stays out of `skills list` inside the CLI. Body is a clean pointer to `agent-browser skills get core` and the specialized skills. The `hidden: true` frontmatter flag is a new, general mechanism: skills marked hidden are omitted from `skills list` and `skills get --all` but can still be fetched by explicit name. This keeps the stub reachable for anyone who installed via `npx skills add` without polluting the CLI-side skill listing. ## Behavior ``` $ agent-browser skills list agentcore Run agent-browser on AWS Bedrock AgentCore cloud browsers... core Core agent-browser usage guide. Read this before running... dogfood Systematically explore and test a web application... electron Automate Electron desktop apps (VS Code, Slack, Discord...) slack Interact with Slack workspaces using browser automation... vercel-sandbox Run agent-browser + Chrome inside Vercel Sandbox microVMs... $ agent-browser skills get core # the actual usage guide # ~420 lines of workflows, patterns, troubleshooting $ agent-browser skills get agent-browser # still works if called explicitly # the thin stub, now pointing at `core` ``` External `npx skills add vercel-labs/agent-browser` behavior is unchanged: it finds and installs the thin `agent-browser` stub, which tells the agent to run `agent-browser skills get core` for real content. Version drift protection is preserved — the stub is the only thing that gets copied; the real content is always runtime-fetched. ## Updated - `cli/src/skills.rs` — `SkillInfo.hidden: bool`, parsed from frontmatter; `run_list` and `run_get --all` filter it. 3 new unit tests for the frontmatter parser. - `cli/src/output.rs` — top-level `--help` and `skills` subcommand help reference `skills get core` / `skills get core --full`. - `AGENTS.md` — "update these files for user-facing features" now points at `skill-data/core/` instead of the stub, with a note that the stub is not the right place for feature content. - `README.md`, `docs/src/app/skills/page.mdx` — describe the new split and `skills get core --full` as the recommended entry point. - `evals/cases/{command-usage,skill-selection}.ts` — expect `skills get core` in agent output instead of `skills get agent-browser`. Eval lib still reads `skills/agent-browser/SKILL.md` (simulating what an agent sees after `npx skills add`). All 11 skills unit tests pass. `cargo clippy -- -D warnings` and `cargo fmt --check` clean. Verified end-to-end: `skills list` shows `core` + specialized (no stub), `skills get core` returns the new content, `skills get agent-browser` still returns the stub on explicit request.	2026-04-16 14:36:59 -05:00