leeguooooo
61060486f4
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.
349 lines
8.2 KiB
Markdown
349 lines
8.2 KiB
Markdown
# Common Slack Tasks & Patterns
|
|
|
|
Reference guide for common automations and data extraction patterns when interacting with Slack.
|
|
|
|
## Task: Check All Unread Messages
|
|
|
|
### Goal
|
|
Determine which channels and DMs have unread messages.
|
|
|
|
### Steps
|
|
|
|
1. **Connect to Slack**
|
|
```bash
|
|
chrome-use connect 9222
|
|
```
|
|
|
|
2. **Check Activity Tab**
|
|
- Take snapshot: `chrome-use snapshot -i`
|
|
- Look for Activity tab ref (usually `@e14`)
|
|
- 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: `chrome-use screenshot activity.png`
|
|
|
|
3. **Check DMs**
|
|
- Click DMs tab ref (usually `@e13`)
|
|
- Look for "Unreads" toggle/badge
|
|
- Count visible conversations with indicators
|
|
|
|
4. **Check Channels**
|
|
- Look for "More unreads" button (usually in sidebar)
|
|
- Click it to expand list of channels with unreads
|
|
- Screenshot the expanded view
|
|
- Parse channel names from snapshot
|
|
|
|
5. **Summary**
|
|
- Activity + DMs + Channels = complete unread picture
|
|
|
|
### Evidence Capture
|
|
- Screenshot of Activity tab
|
|
- Screenshot of DMs
|
|
- Screenshot of expanded unreads sidebar
|
|
|
|
---
|
|
|
|
## Task: Find All Channels in Workspace
|
|
|
|
### Goal
|
|
Get a complete list of all channels you have access to.
|
|
|
|
### Steps
|
|
|
|
1. **Navigate to Channels section**
|
|
```bash
|
|
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: `chrome-use screenshot all-channels.png`
|
|
|
|
3. **Scroll through sidebar**
|
|
```bash
|
|
# If the list is long, scroll within the sidebar
|
|
chrome-use scroll down 500 --selector ".p-sidebar"
|
|
chrome-use screenshot channels-page-2.png
|
|
```
|
|
|
|
4. **Parse snapshot for channel list**
|
|
```bash
|
|
chrome-use snapshot --json > channels.json
|
|
# Search JSON for treeitem elements with level=2 under "Channels" section
|
|
```
|
|
|
|
### Evidence
|
|
- JSON snapshot with all channel refs
|
|
- Screenshots of channel list
|
|
- Count of total channels
|
|
|
|
---
|
|
|
|
## Task: Search for Messages Containing Keywords
|
|
|
|
### Goal
|
|
Find all messages/threads mentioning specific terms.
|
|
|
|
### Steps
|
|
|
|
1. **Open search**
|
|
```bash
|
|
chrome-use snapshot -i
|
|
# Find Search button ref (usually @e5)
|
|
chrome-use click @e5
|
|
chrome-use wait 500
|
|
```
|
|
|
|
2. **Enter search term**
|
|
```bash
|
|
# Identify search input ref from snapshot
|
|
chrome-use fill @e_search_input "your keyword"
|
|
chrome-use press Enter
|
|
chrome-use wait --load networkidle
|
|
```
|
|
|
|
3. **Capture results**
|
|
```bash
|
|
chrome-use screenshot search-results.png
|
|
chrome-use snapshot -i > search-snapshot.txt
|
|
```
|
|
|
|
4. **Parse results**
|
|
- Look for result items in snapshot
|
|
- Extract message content, sender, channel, timestamp
|
|
- Follow links to view full context
|
|
|
|
### Filters
|
|
Slack search supports filters:
|
|
- `in:channel-name` - Search in specific channel
|
|
- `from:@user` - Messages from specific user
|
|
- `before:2026-02-25` - Messages before date
|
|
- `after:2026-02-20` - Messages after date
|
|
- `has:file` - Messages with files
|
|
- `has:emoji` - Messages with reactions
|
|
|
|
Example search: `"bug report" in:engineering from:@alice after:2026-02-20`
|
|
|
|
---
|
|
|
|
## Task: Monitor a Specific Channel for Activity
|
|
|
|
### Goal
|
|
Watch a channel and capture new messages/engagement.
|
|
|
|
### Steps
|
|
|
|
1. **Navigate to channel**
|
|
```bash
|
|
chrome-use connect 9222
|
|
chrome-use snapshot -i
|
|
# Find channel ref from sidebar
|
|
chrome-use click @e_channel_ref
|
|
chrome-use wait --load networkidle
|
|
```
|
|
|
|
2. **Check channel info**
|
|
- Screenshot channel details: `chrome-use screenshot channel-header.png`
|
|
- Look for member count, description, topic
|
|
|
|
3. **View messages**
|
|
```bash
|
|
# Jump to recent/unread
|
|
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
|
|
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: `chrome-use screenshot thread.png`
|
|
|
|
### Evidence
|
|
- Channel info screenshot
|
|
- Message history screenshots
|
|
- Thread examples
|
|
|
|
---
|
|
|
|
## Task: Extract User Information from a Conversation
|
|
|
|
### Goal
|
|
Find who said what, when, and in what context.
|
|
|
|
### Steps
|
|
|
|
1. **Navigate to relevant channel or DM**
|
|
```bash
|
|
chrome-use click @e_conversation_ref
|
|
chrome-use wait 1000
|
|
```
|
|
|
|
2. **Take snapshot with context**
|
|
```bash
|
|
chrome-use snapshot --json > conversation.json
|
|
```
|
|
|
|
3. **Find message blocks**
|
|
- In JSON, look for document/listitem elements
|
|
- These contain: user name (button), timestamp (link), message text, reactions
|
|
|
|
4. **Extract structured data**
|
|
- User: Found in button element with username
|
|
- Time: Found in link with timestamp
|
|
- Content: Text content of message
|
|
- Reactions: Buttons showing emoji counts
|
|
|
|
5. **Screenshot key messages**
|
|
```bash
|
|
chrome-use screenshot important-message.png
|
|
chrome-use screenshot --annotate annotated-message.png
|
|
```
|
|
|
|
---
|
|
|
|
## Task: Track Reactions to a Message
|
|
|
|
### Goal
|
|
See who reacted to a message and with what emoji.
|
|
|
|
### Steps
|
|
|
|
1. **Find message with reactions**
|
|
```bash
|
|
chrome-use snapshot -i
|
|
# Look for "N reaction(s)" buttons in messages
|
|
```
|
|
|
|
2. **Click reaction button to expand**
|
|
```bash
|
|
chrome-use click @e_reaction_button
|
|
chrome-use wait 500
|
|
```
|
|
|
|
3. **Capture reaction details**
|
|
```bash
|
|
chrome-use screenshot reactions.png
|
|
# You'll see emoji, count, and list of users who reacted
|
|
```
|
|
|
|
4. **Extract data**
|
|
- Emoji used
|
|
- Number of people who reacted
|
|
- User names (if visible in popup)
|
|
|
|
---
|
|
|
|
## Task: Find and Review Pinned Messages
|
|
|
|
### Goal
|
|
See messages that have been pinned in a channel.
|
|
|
|
### Steps
|
|
|
|
1. **Open a channel**
|
|
```bash
|
|
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: `chrome-use click @e_pins_tab`
|
|
- Wait: `chrome-use wait 500`
|
|
|
|
3. **View pinned messages**
|
|
```bash
|
|
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: `chrome-use screenshot pin-detail.png`
|
|
|
|
---
|
|
|
|
## Pattern: Extract Timestamp from Link
|
|
|
|
In Slack snapshot, message timestamps appear as links. Example:
|
|
```
|
|
- link "Feb 25th at 10:26:22 AM" [ref=e151]
|
|
- /url: https://vercel.slack.com/archives/C0A5RTN0856/p1772036782543189
|
|
```
|
|
|
|
The URL contains the timestamp in the fragment (`p1772036782543189`). This is a Slack message ID that uniquely identifies the message.
|
|
|
|
---
|
|
|
|
## Pattern: Understanding Channel/Thread Structure
|
|
|
|
```
|
|
- treeitem "channel-name" [ref=e94] [level=2]
|
|
- group: (contains channel metadata or sub-items)
|
|
```
|
|
|
|
- **level=1**: Section headers (External connections, Starred, Channels, etc.)
|
|
- **level=2**: Individual channels/items within sections
|
|
- **level=3+**: Nested sub-items (rare in sidebar)
|
|
|
|
---
|
|
|
|
## Common Ref Patterns (Session-Dependent)
|
|
|
|
These refs vary per session, but follow patterns:
|
|
|
|
| Element | Typical Ref Range | How to Find |
|
|
|---------|------------------|------------|
|
|
| Home tab | e10-e20 | `snapshot -i \| grep "Home"` |
|
|
| DMs tab | e10-e20 | `snapshot -i \| grep "DMs"` |
|
|
| Activity tab | e10-e20 | `snapshot -i \| grep "Activity"` |
|
|
| Search | e5-e10 | `snapshot -i \| grep "Search"` |
|
|
| More unreads | e20-e30 | `snapshot -i \| grep "More unreads"` |
|
|
| Channel refs | e30+ | `snapshot -i \| grep "treeitem"` |
|
|
|
|
**Always take a fresh snapshot** to find current refs for the current session.
|
|
|
|
---
|
|
|
|
## Debugging: Element Not Found
|
|
|
|
If you can't find an element:
|
|
|
|
1. **Check it's visible**
|
|
```bash
|
|
# Is the element on screen or off-screen?
|
|
chrome-use screenshot current-state.png
|
|
# Compare screenshot to what you expected
|
|
```
|
|
|
|
2. **Try expanding/scrolling**
|
|
```bash
|
|
# Sidebar might need scrolling
|
|
chrome-use scroll down 300 --selector ".p-sidebar"
|
|
chrome-use snapshot -i
|
|
```
|
|
|
|
3. **Check current URL**
|
|
```bash
|
|
chrome-use get url
|
|
# Verify you're in the right section
|
|
```
|
|
|
|
4. **Wait for page to load**
|
|
```bash
|
|
chrome-use wait --load networkidle
|
|
chrome-use wait 1000
|
|
chrome-use snapshot -i
|
|
```
|