5 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	57ef011817	docs: document humanize (human-like input) + silent operation ... - README + README.zh: new Anti-detection subsections — "Human-like input (behavioural stealth)" (curved trajectories / jitter / cadence / eased scroll-drag, adaptive per-page escalation, off|fast|human) with the trajectory contrast table, and "Silent operation" (background tabs, no foreground stealing, focus-emulated). Added AGENT_BROWSER_HUMANIZE to the tuning-knobs table. - skill core: agents told operation is silent by default and how/when to use --humanize (leave on auto; force human for known behavioural targets).	2026-06-11 21:04:35 +09:00
leeguooooo	85fd019f62	docs: lead with the hook, not a feature matrix ... The comparison read like a checklist (Runtime.enable leak, permissions footprint — proof, not pitch). Reframe the opening around the visceral wins: - headline: "Give your AI agent the browser you already live in" - pain→relief lead: no fresh Chrome, no re-login, no captcha walls; you watch it work and take the wheel on 2FA; undetectable because it IS your browser (0% bot) - three plain "why not just use X?" lines (Playwright/browser-use, Claude in Chrome, raw debug port) instead of a wall of checkmarks - the honest feature matrix moves into a collapsible "Full feature comparison". Mirrored in README.zh.md.	2026-06-11 17:40:14 +09:00
leeguooooo	9b4d924e48	docs: make the comparison table honest (CreepJS, Runtime.enable, multi-agent) ... Reader fact-checked the table — three rows overclaimed: - CreepJS: all real-Chrome tools (Claude in Chrome, web-access, us) score ~0%; it is NOT a win vs them. Reframe as "real-browser fingerprint" (✅ for all three, ❌ for Playwright/Puppeteer); note ours is the measured one. - Runtime.enable leak: mark Claude in Chrome "—" (not independently tested) rather than ✅; web-access/Playwright leak, ours is off by default (rebrowser-verified). - Multi-agent: web-access CAN run parallel sub-agents (shared browser), so not ❌. The real differentiator is per-session ISOLATED, command-scoped tab groups. Added footnotes spelling out the caveats. Same fixes in README.zh.md.	2026-06-11 17:34:07 +09:00
leeguooooo	9ad011d93c	docs: add "why not X" comparison up top + Chinese README ... - README opens with a head-to-head vs Claude in Chrome / web-access (raw CDP) / Playwright·Puppeteer·browser-use: the only tool that drives your own logged-in Chrome, from any agent, with no consent popup, undetectably (CreepJS 0%), and multi-agent — addresses the recurring "why not just use <alternative>" question. - add README.zh.md (简体中文) with a language switcher in both files.	2026-06-11 17:30:19 +09:00