8 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	947d150561	fix(docker): escape \$ as \$\$ so docker compose doesn't eat shell vars ... Real bug behind 0.27.0-fork.5 and fork.7 shipping stale linux binaries. Docker compose interpolates \${VAR} (and \$VAR) at YAML parse time against the host shell — including inside `command:` blocks. So: PID1=\$! ← compose sees \$! → host has no `!` var → "" wait \$PID1 ... ← compose sees \$PID1 → "" → becomes `wait ` SRC="...\$TARGET..." ← \$TARGET still works (set in `environment:`) cp "\$SRC" "..." ← \$SRC eaten → empty → cp errors silently Result: the per-PID error check I added in dbf272c never fired because both lines were `wait` (no args) — which waits for ALL children and exits with the LAST one's status, not each individually. A failing arm64 build couldn't fail the script. Fix: escape every script-local \$ as \$\$. Docker compose translates \$\$ → literal \$ when materializing the command for the container, and the in-container shell then expands \$VAR correctly. Verified by `docker compose config` showing the resolved command contains \$\$PID1 / \$\$SRC etc (which becomes \$PID1 / \$SRC in the container's bash).	2026-05-09 11:07:01 +09:00
leeguooooo	dbf272ced7	fix(docker): catch parallel-build failures + stop using glob in cp ... Two latent bugs in the release pipeline that conspired to ship a stale linux-x64 binary in 0.27.0-fork.5 (only caught by manually grepping the embedded version string): 1. build-linux ran x64 and arm64 in parallel and used a single `wait $PID1 $PID2` to join them. That command waits for both, but its exit code is the LAST waited pid only — so if x64 silently broke and arm64 succeeded, the outer script exited 0 and shipped whatever was already in /output from the previous release. Now we wait on each pid individually and exit 1 on either failure. 2. build-single's cp used `agent-browser*` which globs to BOTH the binary and its `.d` dependency file. When two sources are passed, cp requires the destination to be a directory. We weren't, so cp exited non-zero with "Not a directory" and the build script shrugged it off because the next line was `chmod ... || true`. Now we resolve a single explicit source path.	2026-05-09 04:30:20 +09:00
leeguoooooandClaude Opus 4.6	016d60f293	fix(docker): update Rust to 1.94 for cross-compilation builds ... Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-05-08 23:48:50 +09:00
Chris Tate	9e31100dcb	faster builds	2026-01-11 09:59:20 -06:00
Chris Tate	36b1af29f6	windows	2026-01-11 09:54:51 -06:00
Chris Tate	87f11b4190	fixes	2026-01-11 04:30:01 -06:00
Chris Tate	6b3bae760b	fixes	2026-01-11 03:23:39 -06:00