6 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
leeguooooo	1a4c440d9e	ci: fix long-broken CI (version-sync, dead dashboard job, fmt, clippy, flaky test) ... The fork's CI had never been green. Pre-existing failures: - version-sync: check-version-sync.js read packages/dashboard/package.json, which doesn't exist in this fork (workspace is just "."). Drop the dashboard comparison; check package.json vs cli/Cargo.toml only. - Dashboard job: `pnpm install --filter dashboard` for a non-existent package. Remove the job. - Format check: repo was never `cargo fmt`-clean. Ran cargo fmt (mechanical). - Clippy -D warnings (newly enforced on Rust 1.94 stable): manual_contains in commands.rs (.iter().any()->.contains()), question_mark in element.rs (if-let-Err -> ?), result_large_err on the tungstenite handshake callback in connect.rs (allow — the Result type is fixed by the accept_hdr_async contract). - rust-cross: lightpanda::waits_for_ready_without_logs spawns a real process + binds a socket with timing assumptions; flaky in CI. Marked #[ignore]. Also: skill docs note fork.30's relay-preferred auto-connect (plain `agent-browser open` is dialog-free once the ab-connect extension is loaded) and the extension's new "agent-browser-stealth" display name.	2026-06-10 11:49:11 +09:00
leeguooooo	8f67cff3e1	fix(skills): embed skill content in the binary for single-binary installs ... `skills get core` (the first step the agent-browser skill stub tells agents to run) failed with "Skills directory not found" on a GitHub-Release / install.sh install: only the binary is shipped, with no adjacent skills/ or skill-data/ the way an npm install bundles them, so find_package_root() returned nothing. Embed skills/ and skill-data/ into the binary via include_dir (168K) and, when no on-disk skill dirs are found, extract them once to a per-version cache dir ($CACHE/agent-browser/skills-<version>/) and serve from there. npm/dev installs still use the on-disk dirs unchanged. Verified: from an isolated dir (no skills/ nearby), `skills list` shows all 6 skills and `skills get core` serves content.	2026-06-01 17:24:34 +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
Chris Tate	7c2ff0a2a6	Move specialized skills to skill-data/ so npx skills add only finds one (#1227) ... The skills CLI metadata.internal flag was never implemented (PRs #587 and #652 were both closed). All 6 skills were showing in the installer. Move the 5 specialized skills (dogfood, electron, slack, vercel-sandbox, agentcore) from skills/ to skill-data/, which the skills CLI does not search. The bootstrap skill stays in skills/ for discovery. The Rust CLI searches both directories so agent-browser skills list/get still serves all 6.	2026-04-12 13:13:04 -05:00
Chris Tate	71343069d2	Add agent-browser skills command with evals (#1225) ... * Add `agent-browser skills` command Adds a `skills` CLI command that serves bundled skill content at runtime, always matching the installed CLI version. This solves the problem of agents relying on stale cached SKILL.md files after CLI upgrades. The `npx skills add vercel-labs/agent-browser` flow now installs a single thin discovery skill with trigger words for all use cases (browser automation, dogfooding, Electron apps, Slack, etc.) that directs agents to `agent-browser skills get <name>` for current instructions. The other five skills (dogfood, electron, slack, vercel-sandbox, agentcore) are marked `metadata.internal: true` so they are not installed by default but remain accessible via the CLI command. Subcommands: skills [list] List available skills skills get <name> [--full] Get skill content (with optional references) skills get --all Get all skill content skills path [name] Print skill directory path * Fix skills command robustness: UTF-8 safety, flag handling, path output - Make truncate_description UTF-8-safe using char_indices() instead of byte-indexed slicing that panics on multi-byte codepoints - Pass get_all as a bool parameter to run_get instead of embedding --all as a sentinel string in the names list - Canonicalize skills_dir path so `skills path` output is clean - Warn on unrecognized flags in `skills get` instead of silently ignoring them * Add evals framework and strengthen SKILL.md for better agent compliance Strengthen SKILL.md loading instructions to require `skills get` before running commands, and trim skill descriptions to prevent agents from guessing at command syntax. Add TypeScript/Bun eval framework that tests skill-loading, skill-selection, and command-usage via Claude CLI with Vercel AI Gateway. Evals pass 20/20 (100%), up from 85% baseline. * Fix formatting in skills.rs * Add Codex provider to evals framework Add multi-provider support with a shared Provider interface. Codex provider spawns `codex exec --json`, parses JSONL output, and writes ~/.codex/config.toml for AI Gateway routing. Use `--provider codex` to run evals with Codex (default model: openai/o3). First run scores 19/20 (95%) with 100% on skill-loading and skill-selection. * Use scoped temp dir for Codex config instead of overwriting ~/.codex	2026-04-12 12:55:46 -05:00