rebrand: agent-browser-stealth → chrome-use, de-fork, reset to v1.0.0
Release binaries / Build macOS ARM64 (push) Has been cancelled
Release binaries / Build macOS x64 (push) Has been cancelled
Release binaries / Build Linux ARM64 (push) Has been cancelled
Release binaries / Build Linux musl ARM64 (push) Has been cancelled
Release binaries / Build Linux musl x64 (push) Has been cancelled
Release binaries / Build Linux x64 (push) Has been cancelled
Release binaries / Build Windows x64 (push) Has been cancelled
Release binaries / Attach binaries to GitHub Release (push) Has been cancelled

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.
This commit is contained in:
leeguooooo
2026-06-12 12:56:21 +09:00
parent b4c1707a01
commit 61060486f4
89 changed files with 1897 additions and 1926 deletions
+54 -54
View File
@@ -11,16 +11,16 @@ Determine which channels and DMs have unread messages.
1. **Connect to Slack**
```bash
agent-browser connect 9222
chrome-use connect 9222
```
2. **Check Activity Tab**
- Take snapshot: `agent-browser snapshot -i`
- Take snapshot: `chrome-use snapshot -i`
- Look for Activity tab ref (usually `@e14`)
- Click: `agent-browser click @e14`
- Wait: `agent-browser wait 1000`
- Click: `chrome-use click @e14`
- Wait: `chrome-use wait 1000`
- If you see "You've read all the unreads", you have no unread messages
- Screenshot: `agent-browser screenshot activity.png`
- Screenshot: `chrome-use screenshot activity.png`
3. **Check DMs**
- Click DMs tab ref (usually `@e13`)
@@ -52,25 +52,25 @@ Get a complete list of all channels you have access to.
1. **Navigate to Channels section**
```bash
agent-browser connect 9222
agent-browser snapshot -i
chrome-use connect 9222
chrome-use snapshot -i
```
2. **Look for "Channels" treeitem**
- This is usually a collapsed section header
- Click to expand if collapsed
- Screenshot: `agent-browser screenshot all-channels.png`
- Screenshot: `chrome-use screenshot all-channels.png`
3. **Scroll through sidebar**
```bash
# If the list is long, scroll within the sidebar
agent-browser scroll down 500 --selector ".p-sidebar"
agent-browser screenshot channels-page-2.png
chrome-use scroll down 500 --selector ".p-sidebar"
chrome-use screenshot channels-page-2.png
```
4. **Parse snapshot for channel list**
```bash
agent-browser snapshot --json > channels.json
chrome-use snapshot --json > channels.json
# Search JSON for treeitem elements with level=2 under "Channels" section
```
@@ -90,24 +90,24 @@ Find all messages/threads mentioning specific terms.
1. **Open search**
```bash
agent-browser snapshot -i
chrome-use snapshot -i
# Find Search button ref (usually @e5)
agent-browser click @e5
agent-browser wait 500
chrome-use click @e5
chrome-use wait 500
```
2. **Enter search term**
```bash
# Identify search input ref from snapshot
agent-browser fill @e_search_input "your keyword"
agent-browser press Enter
agent-browser wait --load networkidle
chrome-use fill @e_search_input "your keyword"
chrome-use press Enter
chrome-use wait --load networkidle
```
3. **Capture results**
```bash
agent-browser screenshot search-results.png
agent-browser snapshot -i > search-snapshot.txt
chrome-use screenshot search-results.png
chrome-use snapshot -i > search-snapshot.txt
```
4. **Parse results**
@@ -137,35 +137,35 @@ Watch a channel and capture new messages/engagement.
1. **Navigate to channel**
```bash
agent-browser connect 9222
agent-browser snapshot -i
chrome-use connect 9222
chrome-use snapshot -i
# Find channel ref from sidebar
agent-browser click @e_channel_ref
agent-browser wait --load networkidle
chrome-use click @e_channel_ref
chrome-use wait --load networkidle
```
2. **Check channel info**
- Screenshot channel details: `agent-browser screenshot channel-header.png`
- Screenshot channel details: `chrome-use screenshot channel-header.png`
- Look for member count, description, topic
3. **View messages**
```bash
# Jump to recent/unread
agent-browser press j # Jump to unread in Slack
agent-browser wait 500
agent-browser screenshot recent-messages.png
chrome-use press j # Jump to unread in Slack
chrome-use wait 500
chrome-use screenshot recent-messages.png
```
4. **Scroll to see more**
```bash
agent-browser scroll down 500
agent-browser screenshot more-messages.png
chrome-use scroll down 500
chrome-use screenshot more-messages.png
```
5. **Check threads**
- Click on messages with thread indicators
- View replies in thread view
- Screenshot: `agent-browser screenshot thread.png`
- Screenshot: `chrome-use screenshot thread.png`
### Evidence
- Channel info screenshot
@@ -183,13 +183,13 @@ Find who said what, when, and in what context.
1. **Navigate to relevant channel or DM**
```bash
agent-browser click @e_conversation_ref
agent-browser wait 1000
chrome-use click @e_conversation_ref
chrome-use wait 1000
```
2. **Take snapshot with context**
```bash
agent-browser snapshot --json > conversation.json
chrome-use snapshot --json > conversation.json
```
3. **Find message blocks**
@@ -204,8 +204,8 @@ Find who said what, when, and in what context.
5. **Screenshot key messages**
```bash
agent-browser screenshot important-message.png
agent-browser screenshot --annotate annotated-message.png
chrome-use screenshot important-message.png
chrome-use screenshot --annotate annotated-message.png
```
---
@@ -219,19 +219,19 @@ See who reacted to a message and with what emoji.
1. **Find message with reactions**
```bash
agent-browser snapshot -i
chrome-use snapshot -i
# Look for "N reaction(s)" buttons in messages
```
2. **Click reaction button to expand**
```bash
agent-browser click @e_reaction_button
agent-browser wait 500
chrome-use click @e_reaction_button
chrome-use wait 500
```
3. **Capture reaction details**
```bash
agent-browser screenshot reactions.png
chrome-use screenshot reactions.png
# You'll see emoji, count, and list of users who reacted
```
@@ -251,26 +251,26 @@ See messages that have been pinned in a channel.
1. **Open a channel**
```bash
agent-browser click @e_channel_ref
agent-browser wait 1000
agent-browser snapshot -i
chrome-use click @e_channel_ref
chrome-use wait 1000
chrome-use snapshot -i
```
2. **Click Pins tab**
- In channel view, look for "Pins" tab ref (usually near Messages, Files tabs)
- Click it: `agent-browser click @e_pins_tab`
- Wait: `agent-browser wait 500`
- Click it: `chrome-use click @e_pins_tab`
- Wait: `chrome-use wait 500`
3. **View pinned messages**
```bash
agent-browser screenshot pins.png
agent-browser snapshot -i > pins-snapshot.txt
chrome-use screenshot pins.png
chrome-use snapshot -i > pins-snapshot.txt
```
4. **Review each pin**
- Click pin to see context
- Note who pinned it, when, and why
- Screenshot: `agent-browser screenshot pin-detail.png`
- Screenshot: `chrome-use screenshot pin-detail.png`
---
@@ -323,26 +323,26 @@ If you can't find an element:
1. **Check it's visible**
```bash
# Is the element on screen or off-screen?
agent-browser screenshot current-state.png
chrome-use screenshot current-state.png
# Compare screenshot to what you expected
```
2. **Try expanding/scrolling**
```bash
# Sidebar might need scrolling
agent-browser scroll down 300 --selector ".p-sidebar"
agent-browser snapshot -i
chrome-use scroll down 300 --selector ".p-sidebar"
chrome-use snapshot -i
```
3. **Check current URL**
```bash
agent-browser get url
chrome-use get url
# Verify you're in the right section
```
4. **Wait for page to load**
```bash
agent-browser wait --load networkidle
agent-browser wait 1000
agent-browser snapshot -i
chrome-use wait --load networkidle
chrome-use wait 1000
chrome-use snapshot -i
```