browse

name	browse
description	Web content retrieval via browse CLI. Includes general web page fetching (Markdown extraction) and Twitter/X content access (tweets, timelines, threads, search). Preferred over curl for all web content tasks.
triggers	["fetch web page","get web content","extract article","read webpage","web content","url content","抓取网页","获取网页内容","tweet","twitter","x.com"]

Browse Skill

Overview

This skill provides web content access via the browse CLI. It should be the default choice for accessing web pages and Twitter/X content, replacing direct curl usage in most cases.

Why use this over curl:

• Handles JavaScript-rendered pages (SPA, React, Vue, etc.)
• Extracts clean Markdown content automatically
• Provides structured Twitter/X data (not just HTML)
• No need to manually parse HTML
• Auth and domain config are centralized in ~/.config/browse-cli/config.toml

Prerequisites

The browse CLI must be installed and configured:

# Install
cd browse-cli && make install

# Configure
mkdir -p ~/.config/browse-cli
cat > ~/.config/browse-cli/config.toml << 'EOF'
url   = "https://your-domain.com"
token = "your-bearer-token"
EOF

Global Flags

All commands support:

• --json — Output raw JSON
• --plain — Output compact plain text
• --jq <expr> — Filter JSON with jq expression (requires --json)

---

Part 1: General Web Content

browse fetch

Fetches any web page and returns main content as Markdown.

Strategy:

1. First tries content negotiation with Accept: text/markdown
2. Falls back to CDP rendering + defuddle extraction

Options:

• --in-page — Run defuddle in browser context for Shadow DOM support

Examples:

browse fetch https://example.com/article
browse fetch example.com/article --in-page

Response (JSON):

{
  "url": "https://example.com/article",
  "source": "content-negotiation | defuddle",
  "title": "Article Title",
  "author": "Author Name",
  "description": "...",
  "domain": "example.com",
  "published": "2026-01-01",
  "content": "# Article Title\n\nArticle body in markdown...",
  "wordCount": 1234
}

---

Part 2: Twitter/X Content

browse tweet get

Retrieves a specific tweet with full metadata. Accepts a full x.com/twitter.com URL.

For article tweets, includes:

• article — Resolved blocks with inlined entity data
• article_markdown — Article content as Markdown
• article_title — Article title
• article_cover — Cover image URL

Example:

browse tweet get https://x.com/elonmusk/status/1234567890

browse tweet thread

Retrieves a tweet thread with replies.

Options:

• --max — Maximum replies to fetch (default: 100)

Response:

{
  "mainTweet": { ... },
  "replies": [ ... ],
  "totalCount": 42,
  "hasMore": false
}

---

Part 3: Browser Management

browse reset

Resets the browser by navigating to about:blank.

---

Usage Examples

Fetch article content

browse fetch https://example.com/article --json --jq '.content'

Get specific tweet

browse tweet get https://x.com/elonmusk/status/1234567890 --json

Get thread with replies

browse tweet thread https://x.com/elonmusk/status/1234567890 --max=50 --json

---

When to Use What

Scenario	Command	Notes
General article/blog	browse fetch <url>	Clean Markdown extraction
Specific tweet	browse tweet get <url>	Structured tweet data
Thread with replies	browse tweet thread <url>	Main tweet + replies array

---

Error Handling

• 504 Timeout: Request took too long (>120s for HTTP, or per-phase timeouts)
• 403 session_expired: Twitter session expired, needs re-login
• Navigation failed: URL unreachable or 4xx/5xx
• Exit codes: 0 success, 1 error, 2 auth failure, 3 not found

---

Notes

• The API runs on a browser-agent instance with a logged-in Chrome profile
• browse status checks connectivity and config validity