@jackwener/opencli 1.0.1 → 1.0.4

package/docs/adapters/desktop/notion.md

@@ -0,0 +1,29 @@
+# Notion
+
+Control the **Notion Desktop App** from the terminal via Chrome DevTools Protocol (CDP).
+
+## Prerequisites
+
+Launch with remote debugging port:
+```bash
+/Applications/Notion.app/Contents/MacOS/Notion --remote-debugging-port=9230
+```
+
+## Setup
+
+```bash
+export OPENCLI_CDP_ENDPOINT="http://127.0.0.1:9230"
+```
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `opencli notion status` | Check CDP connection |
+| `opencli notion search "query"` | Quick Find search (Cmd+P) |
+| `opencli notion read` | Read the current page content |
+| `opencli notion new "title"` | Create a new page (Cmd+N) |
+| `opencli notion write "text"` | Append text to the current page |
+| `opencli notion sidebar` | List pages from the sidebar |
+| `opencli notion favorites` | List pages from the Favorites section |
+| `opencli notion export` | Export page as Markdown |

package/docs/adapters/desktop/wechat.md

@@ -0,0 +1,28 @@
+# WeChat (微信)
+
+Control **WeChat Mac Desktop** from the terminal via AppleScript + Accessibility API.
+
+> **Note:** WeChat is a native macOS app (not Electron), so CDP is not available. This adapter uses AppleScript keyboard simulation and clipboard operations.
+
+## Prerequisites
+
+1. WeChat must be running and logged in
+2. Terminal must have **Accessibility permission** (System Settings → Privacy & Security → Accessibility)
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `opencli wechat status` | Check if WeChat is running |
+| `opencli wechat send "msg"` | Send message in the active chat (clipboard paste + Enter) |
+| `opencli wechat read` | Read current chat content (Cmd+A → Cmd+C) |
+| `opencli wechat search "keyword"` | Open search and type a query (Cmd+F) |
+| `opencli wechat chats` | Switch to Chats tab (Cmd+1) |
+| `opencli wechat contacts` | Switch to Contacts tab (Cmd+2) |
+
+## Limitations
+
+- **No CDP support** — WeChat is native Cocoa, not Electron
+- `send` requires the correct conversation to be already open
+- `read` captures whatever is visible via select-all + copy
+- `search` types the query but cannot programmatically click results

package/docs/adapters/index.md

@@ -0,0 +1,49 @@
+# All Adapters
+
+Run `opencli list` for the live registry.
+
+## Browser Adapters
+
+| Site | Commands | Mode |
+|------|----------|------|
+| **[twitter](/adapters/browser/twitter)** | `trending` `bookmarks` `profile` `search` `timeline` `thread` `following` `followers` `notifications` `post` `reply` `delete` `like` `article` `follow` `unfollow` `bookmark` `unbookmark` `download` `accept` `reply-dm` | 🔐 Browser |
+| **[reddit](/adapters/browser/reddit)** | `hot` `frontpage` `popular` `search` `subreddit` `read` `user` `user-posts` `user-comments` `upvote` `save` `comment` `subscribe` `saved` `upvoted` | 🔐 Browser |
+| **[bilibili](/adapters/browser/bilibili)** | `hot` `search` `me` `favorite` `history` `feed` `subtitle` `dynamic` `ranking` `following` `user-videos` `download` | 🔐 Browser |
+| **[zhihu](/adapters/browser/zhihu)** | `hot` `search` `question` `download` | 🔐 Browser |
+| **[xiaohongshu](/adapters/browser/xiaohongshu)** | `search` `notifications` `feed` `me` `user` `download` | 🔐 Browser |
+| **[xueqiu](/adapters/browser/xueqiu)** | `feed` `hot-stock` `hot` `search` `stock` `watchlist` | 🔐 Browser |
+| **[youtube](/adapters/browser/youtube)** | `search` `video` `transcript` | 🔐 Browser |
+| **[v2ex](/adapters/browser/v2ex)** | `hot` `latest` `topic` `daily` `me` `notifications` | 🌐 / 🔐 |
+| **[weibo](/adapters/browser/weibo)** | `hot` | 🔐 Browser |
+| **[linkedin](/adapters/browser/linkedin)** | `search` | 🔐 Browser |
+| **[coupang](/adapters/browser/coupang)** | `search` `add-to-cart` | 🔐 Browser |
+| **[boss](/adapters/browser/boss)** | `search` `detail` | 🔐 Browser |
+| **[ctrip](/adapters/browser/ctrip)** | `search` | 🔐 Browser |
+| **[reuters](/adapters/browser/reuters)** | `search` | 🔐 Browser |
+| **[smzdm](/adapters/browser/smzdm)** | `search` | 🔐 Browser |
+
+## Public API Adapters
+
+| Site | Commands | Mode |
+|------|----------|------|
+| **[hackernews](/adapters/browser/hackernews)** | `top` | 🌐 Public |
+| **[github](/adapters/browser/github)** | `search` | 🌐 Public |
+| **[bbc](/adapters/browser/bbc)** | `news` | 🌐 Public |
+| **[apple-podcasts](/adapters/browser/apple-podcasts)** | `search` `episodes` `top` | 🌐 Public |
+| **[xiaoyuzhou](/adapters/browser/xiaoyuzhou)** | `podcast` `podcast-episodes` `episode` | 🌐 Public |
+| **[yahoo-finance](/adapters/browser/yahoo-finance)** | `quote` | 🌐 Public |
+
+## Desktop Adapters
+
+| App | Description | Commands |
+|-----|-------------|----------|
+| **[Cursor](/adapters/desktop/cursor)** | Control Cursor IDE | `status` `send` `read` `new` `dump` `composer` `model` `extract-code` `ask` `screenshot` `history` `export` |
+| **[Codex](/adapters/desktop/codex)** | Drive OpenAI Codex CLI agent | `status` `send` `read` `new` `extract-diff` `model` `ask` `screenshot` `history` `export` |
+| **[Antigravity](/adapters/desktop/antigravity)** | Control Antigravity Ultra | `status` `send` `read` `new` `dump` `extract-code` `model` `watch` |
+| **[ChatGPT](/adapters/desktop/chatgpt)** | Automate ChatGPT macOS app | `status` `new` `send` `read` `ask` |
+| **[ChatWise](/adapters/desktop/chatwise)** | Multi-LLM client | `status` `new` `send` `read` `ask` `model` `history` `export` `screenshot` |
+| **[Notion](/adapters/desktop/notion)** | Search, read, write pages | `status` `search` `read` `new` `write` `sidebar` `favorites` `export` |
+| **[Discord](/adapters/desktop/discord)** | Desktop messages & channels | `status` `send` `read` `channels` `servers` `search` `members` |
+| **[Feishu](/adapters/desktop/feishu)** | 飞书/Lark via AppleScript | `status` `send` `read` `search` `new` |
+| **[WeChat](/adapters/desktop/wechat)** | 微信 via AppleScript | `status` `send` `read` `search` `chats` `contacts` |
+| **[NeteaseMusic](/adapters/desktop/neteasemusic)** | 网易云音乐 via CDP | `status` `playing` `play` `next` `prev` `search` `playlist` `like` `lyrics` `volume` |

package/docs/advanced/cdp.md

@@ -0,0 +1,103 @@
+# Connecting OpenCLI via CDP (Remote/Headless Servers)
+
+If you cannot use the opencli Browser Bridge extension (e.g., in a remote headless server environment without a UI), OpenCLI provides an alternative: connecting directly to Chrome via **CDP (Chrome DevTools Protocol)**.
+
+Because CDP binds to `localhost` by default for security reasons, accessing it from a remote server requires an additional networking tunnel.
+
+This guide is broken down into three phases:
+1. **Preparation**: Start Chrome with CDP enabled locally.
+2. **Network Tunnels**: Expose that CDP port to your remote server using either **SSH Tunnels** or **Reverse Proxies**.
+3. **Execution**: Run OpenCLI on your server.
+
+---
+
+## Phase 1: Preparation (Local Machine)
+
+First, you need to start a Chrome browser on your local machine with remote debugging enabled.
+
+**macOS:**
+```bash
+/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
+  --remote-debugging-port=9222 \
+  --user-data-dir="$HOME/chrome-debug-profile" \
+  --remote-allow-origins="*"
+```
+
+**Linux:**
+```bash
+google-chrome \
+  --remote-debugging-port=9222 \
+  --user-data-dir="$HOME/chrome-debug-profile" \
+  --remote-allow-origins="*"
+```
+
+**Windows:**
+```cmd
+"C:\Program Files\Google\Chrome\Application\chrome.exe" ^
+  --remote-debugging-port=9222 ^
+  --user-data-dir="%USERPROFILE%\chrome-debug-profile" ^
+  --remote-allow-origins="*"
+```
+
+> **Note**: The `--remote-allow-origins="*"` flag is often required for modern Chrome versions to accept cross-origin CDP WebSocket connections (e.g. from reverse proxies like ngrok).
+
+Once this browser instance opens, **log into the target websites you want to use** (e.g., bilibili.com, zhihu.com) so that the session contains the correct cookies.
+
+---
+
+## Phase 2: Remote Access Methods
+
+Once CDP is running locally on port `9222`, you must securely expose this port to your remote server. Choose one of the two methods below depending on your network conditions.
+
+### Method A: SSH Tunnel (Recommended)
+
+If your local machine has SSH access to the remote server, this is the most secure and straightforward method.
+
+Run this command on your **Local Machine** to forward the remote server's port `9222` back to your local port `9222`:
+
+```bash
+ssh -R 9222:localhost:9222 your-server-user@your-server-ip
+```
+
+Leave this SSH session running in the background.
+
+### Method B: Reverse Proxy (ngrok / frp / socat)
+
+If you cannot establish a direct SSH connection (e.g., due to NAT or firewalls), you can use an intranet penetration tool like `ngrok`.
+
+Run this command on your **Local Machine** to expose your local port `9222` to the public internet securely via ngrok:
+
+```bash
+ngrok http 9222
+```
+
+This will print a forwarding URL, such as `https://abcdef.ngrok.app`. **Copy this URL**.
+
+---
+
+## Phase 3: Execution (Remote Server)
+
+Now switch to your **Remote Server** where OpenCLI is installed. 
+
+Depending on the network tunnel method you chose in Phase 2, set the `OPENCLI_CDP_ENDPOINT` environment variable and run your commands.
+
+### If you used Method A (SSH Tunnel):
+
+```bash
+export OPENCLI_CDP_ENDPOINT="http://localhost:9222"
+opencli doctor                    # Verify connection
+opencli bilibili hot --limit 5    # Test a command
+```
+
+### If you used Method B (Reverse Proxy like ngrok):
+
+```bash
+# Use the URL you copied from ngrok earlier
+export OPENCLI_CDP_ENDPOINT="https://abcdef.ngrok.app"
+opencli doctor                    # Verify connection
+opencli bilibili hot --limit 5    # Test a command
+```
+
+> *Tip: If you provide a standard HTTP/HTTPS CDP endpoint, OpenCLI requests the `/json` target list and picks the most likely inspectable app/page target automatically. If multiple app targets exist, you can further narrow selection with `OPENCLI_CDP_TARGET` (for example `antigravity` or `codex`).*
+
+If you plan to use this setup frequently, you can persist the environment variable by adding the `export` line to your `~/.bashrc` or `~/.zshrc` on the server.

package/docs/advanced/download.md

@@ -0,0 +1,63 @@
+# Download Support
+
+OpenCLI supports downloading images, videos, and articles from supported platforms.
+
+## Supported Platforms
+
+| Platform | Content Types | Notes |
+|----------|---------------|-------|
+| **xiaohongshu** | Images, Videos | Downloads all media from a note |
+| **bilibili** | Videos | Requires `yt-dlp` installed |
+| **twitter** | Images, Videos | Downloads from user media tab or single tweet |
+| **zhihu** | Articles (Markdown) | Exports articles with optional image download |
+
+## Prerequisites
+
+For video downloads from streaming platforms, install `yt-dlp`:
+
+```bash
+# Install yt-dlp
+pip install yt-dlp
+# or
+brew install yt-dlp
+```
+
+## Usage Examples
+
+```bash
+# Download images/videos from Xiaohongshu note
+opencli xiaohongshu download --note_id abc123 --output ./xhs
+
+# Download Bilibili video (requires yt-dlp)
+opencli bilibili download --bvid BV1xxx --output ./bilibili
+opencli bilibili download --bvid BV1xxx --quality 1080p
+
+# Download Twitter media from user
+opencli twitter download --username elonmusk --limit 20 --output ./twitter
+
+# Download single tweet media
+opencli twitter download --tweet-url "https://x.com/user/status/123" --output ./twitter
+
+# Export Zhihu article to Markdown
+opencli zhihu download --url "https://zhuanlan.zhihu.com/p/xxx" --output ./zhihu
+
+# Export with local images
+opencli zhihu download --url "https://zhuanlan.zhihu.com/p/xxx" --download-images
+```
+
+## Pipeline Step (YAML Adapters)
+
+The `download` step can be used in YAML pipelines:
+
+::: v-pre
+```yaml
+pipeline:
+  - fetch: https://api.example.com/media
+  - download:
+      url: ${{ item.imageUrl }}
+      dir: ./downloads
+      filename: ${{ item.title | sanitize }}.jpg
+      concurrency: 5
+      skip_existing: true
+```
+:::

package/docs/advanced/electron.md

@@ -0,0 +1,125 @@
+---
+description: How to CLI-ify and automate any Electron Desktop Application via CDP
+---
+
+# CLI-ifying Electron Applications (Skill Guide)
+
+Based on the successful automation of **Cursor**, **Codex**, **Antigravity**, **ChatWise**, **Notion**, and **Discord** desktop apps, this guide serves as the standard operating procedure (SOP) for adapting ANY Electron-based application into an OpenCLI adapter.
+
+## Core Concept
+
+Electron apps are essentially local Chromium browser instances. By exposing a debugging port (CDP — Chrome DevTools Protocol) at launch time, we can use the Browser Bridge to pierce through the UI layer, accessing and controlling all underlying state including React/Vue components and Shadow DOM.
+
+> **Note:** Not all desktop apps are Electron. WeChat (native Cocoa) and Feishu/Lark (custom Lark Framework) embed Chromium but do NOT expose CDP. For those apps, use the AppleScript + clipboard approach instead (see [Non-Electron Pattern](#non-electron-pattern-applescript)).
+
+### Launching the Target App
+```bash
+/Applications/AppName.app/Contents/MacOS/AppName --remote-debugging-port=9222
+```
+
+### Verifying Electron
+```bash
+# Check for Electron Framework in the app bundle
+ls /Applications/AppName.app/Contents/Frameworks/Electron\ Framework.framework
+# If this directory exists → Electron → CDP works
+# If not → check for libEGL.dylib (embedded Chromium/CEF, CDP may not work)
+```
+
+## The 5-Command Pattern (CDP / Electron)
+
+Every new Electron adapter should implement these 5 commands in `src/clis/<app_name>/`:
+
+### 1. `status.ts` — Connection Test
+```typescript
+export const statusCommand = cli({
+  site: 'myapp',
+  name: 'status',
+  domain: 'localhost',
+  strategy: Strategy.UI,
+  browser: true,       // Requires CDP connection
+  args: [],
+  columns: ['Status', 'Url', 'Title'],
+  func: async (page: IPage) => {
+    const url = await page.evaluate('window.location.href');
+    const title = await page.evaluate('document.title');
+    return [{ Status: 'Connected', Url: url, Title: title }];
+  },
+});
+```
+
+### 2. `dump.ts` — Reverse Engineering Core
+Modern app DOMs are huge and obfuscated. **Never guess selectors.** Dump first, then extract precise class names with AI or `grep`:
+```typescript
+const dom = await page.evaluate('document.body.innerHTML');
+fs.writeFileSync('/tmp/app-dom.html', dom);
+const snap = await page.snapshot({ interactive: false });
+fs.writeFileSync('/tmp/app-snapshot.json', JSON.stringify(snap, null, 2));
+```
+
+### 3. `send.ts` — Advanced Text Injection
+Electron apps often use complex rich-text editors (Monaco, Lexical, ProseMirror). Setting `.value` directly is ignored by React state.
+
+**Best practice:** Use `document.execCommand('insertText')` to perfectly simulate real user input, fully piercing React state:
+```javascript
+const composer = document.querySelector('[contenteditable="true"]');
+composer.focus();
+document.execCommand('insertText', false, 'Hello');
+```
+Then submit with `await page.pressKey('Enter')`.
+
+### 4. `read.ts` — Context Extraction
+Don't extract the entire page text. Use `dump.ts` output to find the real "conversation container":
+- Look for semantic selectors: `[role="log"]`, `[data-testid="conversation"]`, `[data-content-search-turn-key]`
+- Format output as Markdown — readable by both humans and LLMs
+
+### 5. `new.ts` — Keyboard Shortcuts
+Many GUI actions respond to native shortcuts rather than button clicks:
+```typescript
+const isMac = process.platform === 'darwin';
+await page.pressKey(isMac ? 'Meta+N' : 'Control+N');
+await page.wait(1); // Wait for re-render
+```
+
+## Environment Variable
+```bash
+export OPENCLI_CDP_ENDPOINT="http://127.0.0.1:9222"
+```
+
+## Non-Electron Pattern (AppleScript)
+
+For native macOS apps (WeChat, Feishu) that don't expose CDP:
+```typescript
+export const statusCommand = cli({
+  site: 'myapp',
+  strategy: Strategy.PUBLIC,
+  browser: false,       // No browser needed
+  func: async (page: IPage | null) => {
+    const output = execSync("osascript -e 'application \"MyApp\" is running'", { encoding: 'utf-8' }).trim();
+    return [{ Status: output === 'true' ? 'Running' : 'Stopped' }];
+  },
+});
+```
+
+Core techniques:
+- **status**: `osascript -e 'application "AppName" is running'`
+- **send**: `pbcopy` → activate window → `Cmd+V` → `Enter`
+- **read**: `Cmd+A` → `Cmd+C` → `pbpaste`
+- **search**: Activate → `Cmd+F`/`Cmd+K` → `keystroke "query"`
+
+## Pitfalls & Gotchas
+
+1. **Port conflicts (EADDRINUSE)**: Only one app per port. Use unique ports: Codex=9222, ChatGPT=9224, Cursor=9226, ChatWise=9228, Notion=9230, Discord=9232
+2. **IPage abstraction**: OpenCLI wraps the browser page as `IPage` (`src/types.ts`). Use `page.pressKey()` and `page.evaluate()`, NOT direct DOM APIs
+3. **Timing**: Always add `await page.wait(0.5)` to `1.0` after DOM mutations. Returning too early disconnects prematurely
+4. **AppleScript requires Accessibility**: Terminal app must be granted permission in System Settings → Privacy & Security → Accessibility
+
+## Port Assignment Table
+
+| App | Port | Mode |
+|-----|------|------|
+| Codex | 9222 | CDP |
+| ChatGPT | 9224 | CDP / AppleScript |
+| Cursor | 9226 | CDP |
+| ChatWise | 9228 | CDP |
+| Notion | 9230 | CDP |
+| Discord App | 9232 | CDP |

package/docs/advanced/remote-chrome.md

@@ -0,0 +1,72 @@
+# Remote Chrome
+
+Run OpenCLI on a server or headless environment by connecting to a remote Chrome instance.
+
+## Use Cases
+
+- Running CLI commands on a remote server
+- CI/CD automation with headed browser
+- Shared team browser sessions
+
+## Setup
+
+### 1. Start Chrome on the Remote Machine
+
+```bash
+# On the remote machine (or your Mac)
+/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome \
+  --remote-debugging-port=9222
+```
+
+### 2. SSH Tunnel (If Needed)
+
+If the remote Chrome is on a different machine, create an SSH tunnel:
+
+```bash
+# On your local machine or server
+ssh -L 9222:127.0.0.1:9222 user@remote-host
+```
+
+::: warning
+Use `127.0.0.1` instead of `localhost` in the SSH command to avoid IPv6 resolution issues that can cause timeouts.
+:::
+
+### 3. Configure OpenCLI
+
+```bash
+export OPENCLI_CDP_ENDPOINT="http://127.0.0.1:9222"
+```
+
+### 4. Verify
+
+```bash
+# Test the connection
+curl http://127.0.0.1:9222/json/version
+
+# Run a diagnostic
+opencli doctor
+```
+
+## CI/CD Integration
+
+For CI/CD environments, use a real Chrome instance with `xvfb`:
+
+::: v-pre
+```yaml
+steps:
+  - uses: browser-actions/setup-chrome@latest
+    id: setup-chrome
+  - run: |
+      xvfb-run --auto-servernum \
+        ${{ steps.setup-chrome.outputs.chrome-path }} \
+        --remote-debugging-port=9222 &
+```
+:::
+
+Set the browser executable path:
+::: v-pre
+```yaml
+env:
+  OPENCLI_BROWSER_EXECUTABLE_PATH: ${{ steps.setup-chrome.outputs.chrome-path }}
+```
+:::

package/docs/developer/ai-workflow.md

@@ -0,0 +1,66 @@
+# AI Workflow
+
+OpenCLI is designed with AI agents in mind. This guide covers the AI-native discovery and code generation tools.
+
+## Quick Mode (One-Shot)
+
+Generate a single command for a specific page URL — just a URL + one-line goal, 4 steps done:
+
+```bash
+opencli generate https://example.com --goal "trending"
+```
+
+This runs: explore → synthesize → register in one shot.
+
+For the complete one-shot workflow details, see [CLI-ONESHOT.md](https://github.com/jackwener/opencli/blob/main/CLI-ONESHOT.md).
+
+## Full Mode (Explorer Workflow)
+
+### Step 1: Deep Explore
+
+Discover APIs, infer capabilities, and detect framework:
+
+```bash
+opencli explore https://example.com --site mysite
+```
+
+Outputs to `.opencli/explore/<site>/`:
+- `manifest.json` — Site metadata
+- `endpoints.json` — Discovered API endpoints
+- `capabilities.json` — Inferred capabilities
+- `auth.json` — Authentication strategy details
+
+### Step 2: Synthesize
+
+Generate YAML adapters from explore artifacts:
+
+```bash
+opencli synthesize mysite
+```
+
+### Step 3: Strategy Cascade
+
+Auto-probe authentication strategies: `PUBLIC → COOKIE → HEADER`:
+
+```bash
+opencli cascade https://api.example.com/data
+```
+
+### Step 4: Validate & Test
+
+```bash
+opencli validate                           # Validate generated YAML
+opencli <site> <command> --limit 3 -f json # Test the command
+```
+
+## 5-Tier Authentication Strategy
+
+The explorer uses a decision tree to determine the best authentication approach:
+
+1. **PUBLIC** — No auth, direct API call
+2. **COOKIE** — Reuse Chrome session cookies
+3. **HEADER** — Custom auth headers
+4. **BROWSER** — Full browser automation
+5. **CDP** — Chrome DevTools Protocol for Electron apps
+
+For the complete browser exploration workflow and debugging guide, see [CLI-EXPLORER.md](https://github.com/jackwener/opencli/blob/main/CLI-EXPLORER.md).

package/docs/developer/architecture.md

@@ -0,0 +1,90 @@
+# Architecture
+
+OpenCLI is built on a **Dual-Engine Architecture** that supports both declarative YAML pipelines and programmatic TypeScript adapters.
+
+## High-Level Architecture
+
+```
+┌─────────────────────────────────────────────────────┐
+│                     opencli CLI                      │
+│              (Commander.js entry point)               │
+├─────────────────────────────────────────────────────┤
+│                   Engine Layer                        │
+│  ┌──────────────┐  ┌──────────────┐  ┌────────────┐ │
+│  │   Registry   │  │   Dynamic    │  │   Output   │ │
+│  │  (commands)  │  │   Loader     │  │ Formatter  │ │
+│  └──────────────┘  └──────────────┘  └────────────┘ │
+├─────────────────────────────────────────────────────┤
+│                 Adapter Layer                         │
+│  ┌─────────────────┐  ┌──────────────────────────┐  │
+│  │  YAML Pipeline  │  │  TypeScript Adapters     │  │
+│  │  (declarative)  │  │  (browser/desktop/AI)    │  │
+│  └─────────────────┘  └──────────────────────────┘  │
+├─────────────────────────────────────────────────────┤
+│              Connection Layer                         │
+│  ┌─────────────────┐  ┌──────────────────────────┐  │
+│  │ Browser Bridge  │  │  CDP (Chrome DevTools)   │  │
+│  │ (Extension+WS)  │  │  (Electron apps)         │  │
+│  └─────────────────┘  └──────────────────────────┘  │
+└─────────────────────────────────────────────────────┘
+```
+
+## Core Modules
+
+### Registry (`src/registry.ts`)
+Central command registry. All adapters register their commands via the `cli()` function with metadata: site, name, description, domain, strategy, args, columns.
+
+### Engine (`src/engine.ts`)
+Command discovery and execution engine. Discovers commands from the registry, parses arguments, executes the appropriate adapter, and routes output through the formatter.
+
+### Browser (`src/browser.ts`)
+Manages connections to Chrome via the Browser Bridge WebSocket daemon. Handles JSON-RPC messaging, tab management, and extension/standalone mode switching.
+
+### Pipeline (`src/pipeline/`)
+The YAML pipeline engine. Processes declarative steps:
+- **fetch** — HTTP requests with cookie/header strategies
+- **map** — Data transformation with template expressions
+- **limit** — Result truncation
+- **filter** — Conditional filtering
+- **download** — Media download support
+
+### Output (`src/output.ts`)
+Unified output formatting: `table`, `json`, `yaml`, `md`, `csv`.
+
+## Authentication Strategies
+
+OpenCLI uses a 3-tier authentication strategy:
+
+| Strategy | How It Works | When to Use |
+|----------|-------------|-------------|
+| `public` | Direct HTTP fetch, no auth | Public APIs (HackerNews, BBC) |
+| `cookie` | Reuse Chrome cookies via Browser Bridge | Logged-in sites (Bilibili, Zhihu) |
+| `header` | Custom auth headers | API-key based services |
+
+## Directory Structure
+
+```
+src/
+├── main.ts              # Entry point
+├── engine.ts            # Command execution engine
+├── registry.ts          # Command registry
+├── browser.ts           # Browser Bridge connection
+├── output.ts            # Output formatting
+├── doctor.ts            # Diagnostic tool
+├── pipeline/            # YAML pipeline engine
+│   ├── runner.ts
+│   ├── template.ts
+│   ├── transform.ts
+│   └── steps/
+│       ├── fetch.ts
+│       ├── map.ts
+│       ├── limit.ts
+│       ├── filter.ts
+│       └── download.ts
+└── clis/                # Site adapters
+    ├── twitter/
+    ├── reddit/
+    ├── bilibili/
+    ├── cursor/
+    └── ...
+```