publishport-opencli 1.0.1 → 1.0.3

package/dist/src/validate.js

@@ -1,3 +1,3 @@
-import{getRegistry as O,fullName as M}from"./registry.js";import{getRegisteredStepNames as Q}from"./pipeline/registry.js";function U(){return new Set(Q())}export function validateClisWithTarget(q,F){const x=O(),B=[];let I=0,H=0;if(x.size===0)return{ok:!0,results:[{label:"(registry)",errors:[],warnings:["Registry is empty — no commands discovered. Did discoverClis() run?"]}],errors:0,warnings:1,commands:0};let D=F;if(F?.includes("/")){const G=x.get(F);if(G)D=M(G)}const E=new Set;for(const[G,J]of x){if(E.has(J))continue;if(G!==M(J))continue;E.add(J);if(D){if(D.includes("/")){if(G!==D)continue}else if(J.site!==D)continue}const L=V(J);B.push(L);I+=L.errors.length;H+=L.warnings.length}return{ok:I===0,results:B,errors:I,warnings:H,commands:B.length}}function V(q){const F=M(q),x=[],B=[];if(!q.description)B.push("Missing description");if(q.browser&&!q.domain)B.push('Browser command without "domain" — authenticated browser context may not work');if(Array.isArray(q.pipeline)){const H=U();for(let D=0;D<q.pipeline.length;D++){const E=q.pipeline[D];if(E&&typeof E==="object"){for(const G of Object.keys(E))if(!H.has(G))B.push(`Pipeline step ${D}: unknown step name "${G}" (did you mean one of: ${[...H].join(", ")}?)`)}}}const I=q;if(!q.func&&!q.pipeline&&!I._lazy)x.push('Command has neither "func" nor "pipeline" — it cannot execute');if(q.args&&q.args.length>0){const H=new Set;let D=!1;for(const E of q.args){if(H.has(E.name))x.push(`Duplicate arg name "${E.name}"`);H.add(E.name);if(E.positional&&D)B.push(`Positional arg "${E.name}" appears after named args`);if(!E.positional)D=!0}}return{label:F,errors:x,warnings:B}}export function renderValidationReport(q){const F=[`opencli validate: ${q.ok?"PASS":"FAIL"}`,`Checked ${q.commands} command(s)`,`Errors: ${q.errors}  Warnings: ${q.warnings}`];for(const x of q.results)if(x.errors.length>0||x.warnings.length>0){F.push(`
+import{getRegistry as O,fullName as M}from"./registry.js";import{getRegisteredStepNames as Q}from"./pipeline/registry.js";function U(){return new Set(Q())}export function validateClisWithTarget(q,F){const x=O(),B=[];let I=0,H=0;if(x.size===0)return{ok:!0,results:[{label:"(registry)",errors:[],warnings:["Registry is empty — no commands discovered. Did discoverClis() run?"]}],errors:0,warnings:1,commands:0};let D=F;if(F?.includes("/")){const G=x.get(F);if(G)D=M(G)}const E=new Set;for(const[G,J]of x){if(E.has(J))continue;if(G!==M(J))continue;E.add(J);if(D){if(D.includes("/")){if(G!==D)continue}else if(J.site!==D)continue}const L=V(J);B.push(L);I+=L.errors.length;H+=L.warnings.length}return{ok:I===0,results:B,errors:I,warnings:H,commands:B.length}}function V(q){const F=M(q),x=[],B=[];if(!q.description)B.push("Missing description");if(q.browser&&!q.domain)B.push('Browser command without "domain" — authenticated browser context may not work');if(Array.isArray(q.pipeline)){const H=U();for(let D=0;D<q.pipeline.length;D++){const E=q.pipeline[D];if(E&&typeof E==="object"){for(const G of Object.keys(E))if(!H.has(G))B.push(`Pipeline step ${D}: unknown step name "${G}" (did you mean one of: ${[...H].join(", ")}?)`)}}}const I=q;if(!q.func&&!q.pipeline&&!I._lazy)x.push('Command has neither "func" nor "pipeline" — it cannot execute');if(q.args&&q.args.length>0){const H=new Set;let D=!1;for(const E of q.args){if(H.has(E.name))x.push(`Duplicate arg name "${E.name}"`);H.add(E.name);if(E.positional&&D)B.push(`Positional arg "${E.name}" appears after named args`);if(!E.positional)D=!0}}return{label:F,errors:x,warnings:B}}export function renderValidationReport(q){const F=[`ppcli validate: ${q.ok?"PASS":"FAIL"}`,`Checked ${q.commands} command(s)`,`Errors: ${q.errors}  Warnings: ${q.warnings}`];for(const x of q.results)if(x.errors.length>0||x.warnings.length>0){F.push(`
 ${x.label}:`);for(const B of x.errors)F.push(`  ❌ ${B}`);for(const B of x.warnings)F.push(`  ⚠️  ${B}`)}return F.join(`
 `)}

package/dist/src/validate.test.d.ts

@@ -4,6 +4,6 @@
  * Focus: regression guards for the "single source of truth" link between
  * pipeline step registry (src/pipeline/registry.ts) and validate.ts step
  * allowlist. A new step registered via `registerStep()` must automatically
- * be allowlisted by `opencli validate` — no parallel hand-maintained list.
+ * be allowlisted by `ppcli validate` — no parallel hand-maintained list.
  */
 export {};

package/docs/guide/browser-bridge.md

@@ -2,7 +2,7 @@
 
 > **⚠️ Important**: Browser commands reuse your Chrome login session. You must be logged into the target website in Chrome before running commands.
 
-OpenCLI connects to your browser through a lightweight **Browser Bridge** Chrome Extension + micro-daemon (zero config, auto-start).
+ppcli connects to your browser through a lightweight **Browser Bridge** Chrome Extension + micro-daemon (zero config, auto-start).
 
 ## Extension Installation
 
@@ -22,7 +22,7 @@ OpenCLI connects to your browser through a lightweight **Browser Bridge** Chrome
 That's it! The daemon auto-starts when you run any browser command. No tokens, no manual configuration.
 
 ```bash
-opencli doctor            # Check extension + daemon connectivity
+ppcli doctor            # Check extension + daemon connectivity
 ```
 
 ## Tab Targeting
@@ -30,49 +30,49 @@ opencli doctor            # Check extension + daemon connectivity
 Browser commands require an explicit `<session>` positional immediately after `browser`. Use the same session name for a multi-step flow, and use different names to isolate parallel work.
 
 ```bash
-opencli browser baidu open https://www.baidu.com/
-opencli browser baidu tab list
-opencli browser baidu tab new https://www.baidu.com/
-opencli browser baidu eval --tab <targetId> 'document.title'
-opencli browser baidu tab select <targetId>
-opencli browser baidu get title
-opencli browser baidu tab close <targetId>
+ppcli browser baidu open https://www.baidu.com/
+ppcli browser baidu tab list
+ppcli browser baidu tab new https://www.baidu.com/
+ppcli browser baidu eval --tab <targetId> 'document.title'
+ppcli browser baidu tab select <targetId>
+ppcli browser baidu get title
+ppcli browser baidu tab close <targetId>
 ```
 
 Key rules:
 
-- `opencli browser <session> open <url>` and `opencli browser <session> tab new [url]` return a `targetId`.
-- `opencli browser <session> tab list` prints the `targetId` values of tabs that already exist.
+- `ppcli browser <session> open <url>` and `ppcli browser <session> tab new [url]` return a `targetId`.
+- `ppcli browser <session> tab list` prints the `targetId` values of tabs that already exist.
 - `--tab <targetId>` routes a single browser command to that specific tab.
 - `tab new` creates a new tab but does not change the default browser target.
-- `tab select <targetId>` makes that tab the default target for later untargeted `opencli browser ...` commands.
+- `tab select <targetId>` makes that tab the default target for later untargeted `ppcli browser ...` commands.
 - `tab close <targetId>` removes the tab; if it was the current default target, the stored default is cleared.
 
 ## Session Lifecycle
 
-Use a stable session name when you want multiple `opencli browser` commands to keep operating on the same page:
+Use a stable session name when you want multiple `ppcli browser` commands to keep operating on the same page:
 
 ```bash
-opencli browser my-session open https://example.com
-opencli browser my-session state
-opencli browser my-session extract "main"
+ppcli browser my-session open https://example.com
+ppcli browser my-session state
+ppcli browser my-session extract "main"
 ```
 
 Owned browser sessions use an interactive tab lease with a 10-minute idle timeout. Release it explicitly when done:
 
 ```bash
-opencli browser my-session close
+ppcli browser my-session close
 ```
 
-Use `opencli browser <session> bind` when you want to attach OpenCLI to a Chrome tab you already opened manually. Bound sessions do not have the owned-session idle close timer; they stay attached until `unbind`, tab close, window close, or daemon restart. For owned sessions, use `--window foreground` to watch OpenCLI work in a visible automation window, or `--window background` to keep that automation window out of the way.
+Use `ppcli browser <session> bind` when you want to attach ppcli to a Chrome tab you already opened manually. Bound sessions do not have the owned-session idle close timer; they stay attached until `unbind`, tab close, window close, or daemon restart. For owned sessions, use `--window foreground` to watch ppcli work in a visible automation window, or `--window background` to keep that automation window out of the way.
 
-The `OpenCLI Browser` and `OpenCLI Adapter` tab groups are extension-managed automation containers; avoid putting your own long-lived tabs in them or renaming them.
+The `ppcli Browser` and `ppcli Adapter` tab groups are extension-managed automation containers; avoid putting your own long-lived tabs in them or renaming them.
 
 ## How It Works
 
 ```
 ┌─────────────┐     WebSocket      ┌──────────────┐     Chrome API     ┌─────────┐
-│  opencli    │ ◄──────────────► │  micro-daemon │ ◄──────────────► │  Chrome  │
+│  ppcli    │ ◄──────────────► │  micro-daemon │ ◄──────────────► │  Chrome  │
 │  (Node.js)  │    localhost:19825  │  (auto-start) │    Extension       │ Browser  │
 └─────────────┘                    └──────────────┘                    └─────────┘
 ```
@@ -84,11 +84,11 @@ The daemon manages the WebSocket connection between your CLI commands and the Ch
 The daemon auto-starts on first browser command and stays alive persistently.
 
 ```bash
-opencli daemon stop      # Graceful shutdown
+ppcli daemon stop      # Graceful shutdown
 ```
 
-The daemon is persistent — it stays alive until you explicitly stop it (`opencli daemon stop`) or uninstall the package.
+The daemon is persistent — it stays alive until you explicitly stop it (`ppcli daemon stop`) or uninstall the package.
 
-## Running OpenCLI from a remote machine
+## Running ppcli from a remote machine
 
 If you need to run `opencli` on a remote server (CI runner, agent host) but keep the browser session on your local machine, see [Remote Orchestration](/guide/remote-orchestration). It walks through the SSH reverse-tunnel pattern so the daemon never leaves localhost.

package/docs/guide/electron-app-cli.md

@@ -1,10 +1,10 @@
 ---
-description: How to turn a new Electron desktop app into an OpenCLI adapter
+description: How to turn a new Electron desktop app into an ppcli adapter
 ---
 
 # Add a New Electron App CLI
 
-This guide is the **fast entry point** for turning a new Electron desktop application into an OpenCLI adapter.
+This guide is the **fast entry point** for turning a new Electron desktop application into an ppcli adapter.
 
 If you want the full background and deeper SOP, read:
 - [CLI-ifying Electron Applications](/advanced/electron)
@@ -38,7 +38,7 @@ If Electron is present, the next step is usually to launch the app with a debugg
 /Applications/AppName.app/Contents/MacOS/AppName --remote-debugging-port=<unique-port>
 ```
 
-Then point OpenCLI at that CDP endpoint:
+Then point ppcli at that CDP endpoint:
 
 ```bash
 export OPENCLI_CDP_ENDPOINT="http://127.0.0.1:<unique-port>"

package/docs/guide/exit-codes.md

@@ -17,8 +17,8 @@
 ## Example: branch on exit code
 
 ```bash
-opencli spotify status || echo "exit $?"   # 69 if browser not running
+ppcli spotify status || echo "exit $?"   # 69 if browser not running
 
-opencli gh issue list 2>/dev/null
-[ $? -eq 77 ] && opencli gh auth login      # auto-auth if not logged in
+ppcli gh issue list 2>/dev/null
+[ $? -eq 77 ] && ppcli gh auth login      # auto-auth if not logged in
 ```

package/docs/guide/extending-opencli.md

@@ -1,46 +1,46 @@
-# Extending OpenCLI
+# Extending ppcli
 
-OpenCLI has five extension paths. Pick the path based on where you want the source code to live and how you want commands to be shared.
+ppcli has five extension paths. Pick the path based on where you want the source code to live and how you want commands to be shared.
 
 | Goal | Use | Source location | Command surface |
 |------|-----|-----------------|-----------------|
-| Build a personal website command in your own Git repo | Local plugin | Your project directory, symlinked into `~/.opencli/plugins/` | `opencli <plugin> <command>` |
-| Quickly draft a private adapter on this machine | User adapter | `~/.opencli/clis/<site>/<command>.js` | `opencli <site> <command>` |
-| Edit an official adapter locally | Adapter override | `~/.opencli/clis/<site>/` | `opencli <site> <command>` |
-| Publish or install third-party commands | Plugin | Git repo, installed into `~/.opencli/plugins/` | `opencli <plugin> <command>` |
-| Wrap an existing local binary | External CLI | `~/.opencli/external-clis.yaml` | `opencli <tool> ...` |
+| Build a personal website command in your own Git repo | Local plugin | Your project directory, symlinked into `~/.ppcli/plugins/` | `ppcli <plugin> <command>` |
+| Quickly draft a private adapter on this machine | User adapter | `~/.ppcli/clis/<site>/<command>.js` | `ppcli <site> <command>` |
+| Edit an official adapter locally | Adapter override | `~/.ppcli/clis/<site>/` | `ppcli <site> <command>` |
+| Publish or install third-party commands | Plugin | Git repo, installed into `~/.ppcli/plugins/` | `ppcli <plugin> <command>` |
+| Wrap an existing local binary | External CLI | `~/.ppcli/external-clis.yaml` | `ppcli <tool> ...` |
 
 ## Personal commands in your own Git repo
 
 Use a local plugin when you want the code to stay in a normal project directory and be managed by Git.
 
 ```bash
-opencli plugin create my-cnn
+ppcli plugin create my-cnn
 cd my-cnn
 git init
-opencli plugin install file://$(pwd)
-opencli my-cnn hello
+ppcli plugin install file://$(pwd)
+ppcli my-cnn hello
 ```
 
-`plugin install file://...` creates a symlink under `~/.opencli/plugins/`. Your source files stay in your project directory, so edits and commits happen there.
+`plugin install file://...` creates a symlink under `~/.ppcli/plugins/`. Your source files stay in your project directory, so edits and commits happen there.
 
 This is the recommended path for custom commands you own long-term.
 
-## Private adapters in `~/.opencli/clis`
+## Private adapters in `~/.ppcli/clis`
 
 Use a user adapter when you want the fastest local adapter loop and do not need a separate project directory.
 
 ```bash
-opencli browser init cnn/top
-# edit ~/.opencli/clis/cnn/top.js
-opencli browser verify cnn/top
-opencli cnn top
+ppcli browser init cnn/top
+# edit ~/.ppcli/clis/cnn/top.js
+ppcli browser verify cnn/top
+ppcli cnn top
 ```
 
 User adapters are loaded from:
 
 ```text
-~/.opencli/clis/<site>/<command>.js
+~/.ppcli/clis/<site>/<command>.js
 ```
 
 This path is convenient for quick local automation. For code you want to version, review, or share, prefer a plugin.
@@ -48,11 +48,11 @@ This path is convenient for quick local automation. For code you want to version
 If the command takes required positional args and no fixture exists yet, seed the first verify run explicitly:
 
 ```bash
-opencli browser verify instagram/collection-create --write-fixture --seed-args opencli-verify
-opencli browser verify example/detail --write-fixture --seed-args '["https://example.com/item/1", "--limit", 3]'
+ppcli browser verify instagram/collection-create --write-fixture --seed-args opencli-verify
+ppcli browser verify example/detail --write-fixture --seed-args '["https://example.com/item/1", "--limit", 3]'
 ```
 
-`--seed-args` is only used when the fixture has no `args`. Once the fixture is written, `opencli browser verify` reads args from `~/.opencli/sites/<site>/verify/<command>.json`.
+`--seed-args` is only used when the fixture has no `args`. Once the fixture is written, `ppcli browser verify` reads args from `~/.ppcli/sites/<site>/verify/<command>.json`.
 
 `browser verify` also enforces row shape before fixture checks: each row should
 stay compact (at most 12 top-level keys), avoid nesting deeper than one level,
@@ -63,28 +63,28 @@ and keep id-shaped fields such as `id` / `user_id` at the top level.
 Use `adapter eject` when you want to customize an existing official adapter.
 
 ```bash
-opencli adapter eject twitter
-# edit ~/.opencli/clis/twitter/*.js
-opencli adapter reset twitter
+ppcli adapter eject twitter
+# edit ~/.ppcli/clis/twitter/*.js
+ppcli adapter reset twitter
 ```
 
-Files in `~/.opencli/clis/<site>/<command>.js` override packaged adapters with the same `site/command` on this machine. `opencli browser verify <site>/<command>` also runs the local override, so a passing local verify does not prove that the packaged adapter was changed.
+Files in `~/.ppcli/clis/<site>/<command>.js` override packaged adapters with the same `site/command` on this machine. `ppcli browser verify <site>/<command>` also runs the local override, so a passing local verify does not prove that the packaged adapter was changed.
 
 The packaged `cli-manifest.json` only describes bundled adapters. User adapters are discovered at runtime and do not need manifest entries.
 
-After copying a local fix into the repository for a PR, remove the local copy or run `opencli adapter reset <site>` after merge. Otherwise the local file keeps shadowing future package updates. `opencli doctor` warns when it detects this shadowing.
+After copying a local fix into the repository for a PR, remove the local copy or run `ppcli adapter reset <site>` after merge. Otherwise the local file keeps shadowing future package updates. `ppcli doctor` warns when it detects this shadowing.
 
 ## Plugins for sharing commands
 
 Plugins are third-party command packages. They can be installed from GitHub, any git-cloneable URL, or a local directory.
 
 ```bash
-opencli plugin install github:user/opencli-plugin-my-tool
-opencli plugin install https://github.com/user/opencli-plugin-my-tool
-opencli plugin install file:///absolute/path/to/plugin
-opencli plugin list
-opencli plugin update --all
-opencli plugin uninstall my-tool
+ppcli plugin install github:user/opencli-plugin-my-tool
+ppcli plugin install https://github.com/user/opencli-plugin-my-tool
+ppcli plugin install file:///absolute/path/to/plugin
+ppcli plugin list
+ppcli plugin update --all
+ppcli plugin uninstall my-tool
 ```
 
 Each plugin directory is scanned for `.ts` and `.js` command files. TypeScript plugins are transpiled during install.
@@ -105,15 +105,15 @@ For a Git-hosted plugin collection, declare sub-plugins in `opencli-plugin.json`
 ```
 
 ```bash
-opencli plugin install github:user/opencli-plugins
-opencli plugin install github:user/opencli-plugins/cnn
+ppcli plugin install github:user/opencli-plugins
+ppcli plugin install github:user/opencli-plugins/cnn
 ```
 
 For local development, install each sub-plugin directory directly:
 
 ```bash
-opencli plugin install file:///absolute/path/opencli-plugins/packages/cnn
-opencli plugin install file:///absolute/path/opencli-plugins/packages/reuters
+ppcli plugin install file:///absolute/path/opencli-plugins/packages/cnn
+ppcli plugin install file:///absolute/path/opencli-plugins/packages/reuters
 ```
 
 Local `file://` installs expect the target directory itself to be a valid plugin with command files. For a monorepo root, push it to GitHub and install it with the GitHub monorepo flow.
@@ -123,12 +123,12 @@ Local `file://` installs expect the target directory itself to be a valid plugin
 Use external CLI registration when the command already exists as a binary on your machine and you want it available through `opencli`.
 
 ```bash
-opencli external register my-tool \
+ppcli external register my-tool \
   --binary my-tool \
   --install "npm i -g my-tool" \
   --desc "My internal CLI"
 
-opencli my-tool --help
+ppcli my-tool --help
 ```
 
 External CLIs pass stdio and exit codes through to the underlying binary.

package/docs/guide/getting-started.md

@@ -7,7 +7,7 @@
 [![Node.js Version](https://img.shields.io/node/v/@jackwener/opencli?style=flat-square)](https://nodejs.org)
 [![License](https://img.shields.io/npm/l/@jackwener/opencli?style=flat-square)](https://github.com/jackwener/opencli/blob/main/LICENSE)
 
-OpenCLI turns **any website** or **Electron app** into a command-line interface — Bilibili, Zhihu, 小红书, Twitter/X, Reddit, YouTube, Antigravity, and [many more](/adapters/) — powered by browser session reuse and AI-native discovery.
+ppcli turns **any website** or **Electron app** into a command-line interface — Bilibili, Zhihu, 小红书, Twitter/X, Reddit, YouTube, Antigravity, and [many more](/adapters/) — powered by browser session reuse and AI-native discovery.
 
 ## Highlights
 
@@ -15,7 +15,7 @@ OpenCLI turns **any website** or **Electron app** into a command-line interface
 - **Browser Automation** — `browser` gives AI agents direct browser control: click, type/fill, extract, screenshot — fully scriptable.
 - **Website → CLI** — Turn any website into a deterministic CLI: 100+ site surfaces are already registered, or author your own with the `opencli-adapter-author` skill.
 - **Account-safe** — Reuses Chrome's logged-in state; your credentials never leave the browser.
-- **AI Agent ready** — `opencli browser *` primitives (`open` / `network` / `state` / `eval` / `init` / `verify`) drive the adapter-authoring loop.
+- **AI Agent ready** — `ppcli browser *` primitives (`open` / `network` / `state` / `eval` / `init` / `verify`) drive the adapter-authoring loop.
 - **Zero LLM cost** — No tokens consumed at runtime. Run 10,000 times and pay nothing.
 - **Deterministic** — Same command, same output schema, every time. Pipeable, scriptable, CI-friendly.
 
@@ -30,10 +30,10 @@ npm install -g @jackwener/opencli
 ### Basic Usage
 
 ```bash
-opencli list                              # See all commands
-opencli hackernews top --limit 5          # Public API, no browser
-opencli bilibili hot --limit 5            # Browser command
-opencli zhihu hot -f json                 # JSON output
+ppcli list                              # See all commands
+ppcli hackernews top --limit 5          # Public API, no browser
+ppcli bilibili hot --limit 5            # Browser command
+ppcli zhihu hot -f json                 # JSON output
 ```
 
 ### Output Formats
@@ -41,27 +41,27 @@ opencli zhihu hot -f json                 # JSON output
 All built-in commands support `--format` / `-f`:
 
 ```bash
-opencli bilibili hot -f table   # Default: rich terminal table
-opencli bilibili hot -f json    # JSON (pipe to jq or LLMs)
-opencli bilibili hot -f yaml    # YAML (human-readable)
-opencli bilibili hot -f md      # Markdown
-opencli bilibili hot -f csv     # CSV
-opencli bilibili hot -v         # Verbose: show pipeline debug
+ppcli bilibili hot -f table   # Default: rich terminal table
+ppcli bilibili hot -f json    # JSON (pipe to jq or LLMs)
+ppcli bilibili hot -f yaml    # YAML (human-readable)
+ppcli bilibili hot -f md      # Markdown
+ppcli bilibili hot -f csv     # CSV
+ppcli bilibili hot -v         # Verbose: show pipeline debug
 ```
 
 ### Tab Completion
 
-OpenCLI supports intelligent tab completion to speed up command input:
+ppcli supports intelligent tab completion to speed up command input:
 
 ```bash
 # Add shell completion to your startup config
-echo 'eval "$(opencli completion zsh)"' >> ~/.zshrc              # Zsh
-echo 'eval "$(opencli completion bash)"' >> ~/.bashrc            # Bash
-echo 'opencli completion fish | source' >> ~/.config/fish/config.fish  # Fish
+echo 'eval "$(ppcli completion zsh)"' >> ~/.zshrc              # Zsh
+echo 'eval "$(ppcli completion bash)"' >> ~/.bashrc            # Bash
+echo 'ppcli completion fish | source' >> ~/.config/fish/config.fish  # Fish
 
 # Restart your shell, then press Tab to complete:
-opencli [Tab]          # Complete site names (bilibili, zhihu, twitter...)
-opencli bilibili [Tab] # Complete commands (hot, search, me, download...)
+ppcli [Tab]          # Complete site names (bilibili, zhihu, twitter...)
+ppcli bilibili [Tab] # Complete commands (hot, search, me, download...)
 ```
 
 The completion includes:
@@ -74,7 +74,7 @@ The completion includes:
 
 - [Installation details](/guide/installation)
 - [Browser Bridge setup](/guide/browser-bridge)
-- [Extending OpenCLI — custom commands, plugins, and external CLIs](/guide/extending-opencli)
+- [Extending ppcli — custom commands, plugins, and external CLIs](/guide/extending-opencli)
 - [Plugins — extend with community adapters](/guide/plugins)
 - [All available adapters](/adapters/)
 - [For developers / AI agents](/developer/contributing)

package/docs/guide/installation.md

@@ -15,11 +15,11 @@ npm install -g @jackwener/opencli
 
 ```bash
 git clone git@github.com:jackwener/opencli.git
-cd opencli
+cd ppcli
 npm install
 npm run build
 npm link      # Link binary globally
-opencli list  # Now you can use it anywhere!
+ppcli list  # Now you can use it anywhere!
 ```
 
 ## Update
@@ -27,7 +27,7 @@ opencli list  # Now you can use it anywhere!
 ```bash
 npm install -g @jackwener/opencli@latest
 
-# If you use the packaged OpenCLI skills, refresh them too
+# If you use the packaged ppcli skills, refresh them too
 npx skills add jackwener/opencli
 ```
 
@@ -46,7 +46,7 @@ npx skills add jackwener/opencli --skill smart-search
 ## Verify Installation
 
 ```bash
-opencli --version   # Check version
-opencli list        # List all commands
-opencli doctor      # Diagnose connectivity
+ppcli --version   # Check version
+ppcli list        # List all commands
+ppcli doctor      # Diagnose connectivity
 ```

package/docs/guide/plugins.md

@@ -1,49 +1,49 @@
 # Plugins
 
-OpenCLI supports community-contributed plugins. Install third-party adapters from GitHub, and they're automatically discovered alongside built-in commands.
+ppcli supports community-contributed plugins. Install third-party adapters from GitHub, and they're automatically discovered alongside built-in commands.
 
 ## Quick Start
 
 ```bash
 # Install a plugin
-opencli plugin install github:ByteYue/opencli-plugin-github-trending
+ppcli plugin install github:ByteYue/opencli-plugin-github-trending
 
 # List installed plugins
-opencli plugin list
+ppcli plugin list
 
 # Update one plugin
-opencli plugin update github-trending
+ppcli plugin update github-trending
 
 # Update all installed plugins
-opencli plugin update --all
+ppcli plugin update --all
 
 # Use the plugin (it's just a regular command)
-opencli github-trending repos --limit 10
+ppcli github-trending repos --limit 10
 
 # Remove a plugin
-opencli plugin uninstall github-trending
+ppcli plugin uninstall github-trending
 ```
 
 ## How Plugins Work
 
-Plugins live in `~/.opencli/plugins/<name>/`. Each subdirectory is scanned at startup for `.ts` or `.js` command files — the same formats used by built-in adapters.
+Plugins live in `~/.ppcli/plugins/<name>/`. Each subdirectory is scanned at startup for `.ts` or `.js` command files — the same formats used by built-in adapters.
 
 ### Supported Source Formats
 
 ```bash
 # GitHub shorthand
-opencli plugin install github:user/repo
-opencli plugin install github:user/repo/subplugin   # install specific sub-plugin from monorepo
-opencli plugin install https://github.com/user/repo
+ppcli plugin install github:user/repo
+ppcli plugin install github:user/repo/subplugin   # install specific sub-plugin from monorepo
+ppcli plugin install https://github.com/user/repo
 
 # Any git-cloneable URL
-opencli plugin install https://gitlab.example.com/team/repo.git
-opencli plugin install ssh://git@gitlab.example.com/team/repo.git
-opencli plugin install git@gitlab.example.com:team/repo.git
+ppcli plugin install https://gitlab.example.com/team/repo.git
+ppcli plugin install ssh://git@gitlab.example.com/team/repo.git
+ppcli plugin install git@gitlab.example.com:team/repo.git
 
 # Local plugin (for development)
-opencli plugin install file:///path/to/plugin
-opencli plugin install /path/to/plugin
+ppcli plugin install file:///path/to/plugin
+ppcli plugin install /path/to/plugin
 ```
 
 The repo name prefix `opencli-plugin-` is automatically stripped for the local directory name. For example, `opencli-plugin-hot-digest` becomes `hot-digest`.
@@ -56,7 +56,7 @@ Plugins can include an `opencli-plugin.json` manifest file at the repo root to d
 {
   "name": "my-plugin",
   "version": "1.0.0",
-  "opencli": ">=1.0.0",
+  "ppcli": ">=1.0.0",
   "description": "My awesome plugin"
 }
 ```
@@ -65,7 +65,7 @@ Plugins can include an `opencli-plugin.json` manifest file at the repo root to d
 |-------|-------------|
 | `name` | Plugin name (overrides repo-derived name) |
 | `version` | Semantic version |
-| `opencli` | Required opencli version range (e.g. `>=1.0.0`, `^1.2.0`) |
+| `opencli` | Required ppcli version range (e.g. `>=1.0.0`, `^1.2.0`) |
 | `description` | Human-readable description |
 | `plugins` | Monorepo sub-plugin declarations (see below) |
 
@@ -78,7 +78,7 @@ A single repository can contain multiple plugins by declaring a `plugins` field
 ```json
 {
   "version": "1.0.0",
-  "opencli": ">=1.0.0",
+  "ppcli": ">=1.0.0",
   "description": "My plugin collection",
   "plugins": {
     "polymarket": {
@@ -90,7 +90,7 @@ A single repository can contain multiple plugins by declaring a `plugins` field
       "path": "packages/defi",
       "description": "DeFi protocol data",
       "version": "0.8.0",
-      "opencli": ">=1.2.0"
+      "ppcli": ">=1.2.0"
     },
     "experimental": {
       "path": "packages/experimental",
@@ -104,16 +104,16 @@ A single repository can contain multiple plugins by declaring a `plugins` field
 
 ```bash
 # Install ALL enabled sub-plugins from a monorepo
-opencli plugin install github:user/opencli-plugins
+ppcli plugin install github:user/opencli-plugins
 
 # Install a SPECIFIC sub-plugin
-opencli plugin install github:user/opencli-plugins/polymarket
+ppcli plugin install github:user/opencli-plugins/polymarket
 ```
 
 ### How It Works
 
-- The monorepo is cloned once to `~/.opencli/monorepos/<repo>/`
-- Each sub-plugin gets a symlink in `~/.opencli/plugins/<name>/` pointing to its subdirectory
+- The monorepo is cloned once to `~/.ppcli/monorepos/<repo>/`
+- Each sub-plugin gets a symlink in `~/.ppcli/plugins/<name>/` pointing to its subdirectory
 - Command discovery works transparently — symlinks are scanned just like regular directories
 - Disabled sub-plugins (with `"disabled": true`) are skipped during install
 - Sub-plugins can specify their own `opencli` compatibility range
@@ -123,20 +123,20 @@ opencli plugin install github:user/opencli-plugins/polymarket
 Updating any sub-plugin from a monorepo pulls the entire repo and refreshes all sub-plugins:
 
 ```bash
-opencli plugin update polymarket   # updates the monorepo, refreshes all
+ppcli plugin update polymarket   # updates the monorepo, refreshes all
 ```
 
 ### Uninstalling
 
 ```bash
-opencli plugin uninstall polymarket   # removes just this sub-plugin's symlink
+ppcli plugin uninstall polymarket   # removes just this sub-plugin's symlink
 ```
 
 When the last sub-plugin from a monorepo is uninstalled, the monorepo clone is automatically cleaned up.
 
 ## Version Tracking
 
-OpenCLI records installed plugin versions in `~/.opencli/plugins.lock.json`. Each entry stores the plugin source, current git commit hash, install time, and last update time. `opencli plugin list` shows the short commit hash when version metadata is available.
+ppcli records installed plugin versions in `~/.ppcli/plugins.lock.json`. Each entry stores the plugin source, current git commit hash, install time, and last update time. `ppcli plugin list` shows the short commit hash when version metadata is available.
 
 ## Creating a Plugin
 
@@ -172,7 +172,7 @@ cli({
   name: 'my-command',
   description: 'My custom command',
   access: 'read', // 'read' | 'write'
-  example: 'opencli my-plugin my-command -f yaml',
+  example: 'ppcli my-plugin my-command -f yaml',
   strategy: Strategy.PUBLIC,
   browser: false,
   args: [
@@ -192,7 +192,7 @@ cli({
 
 ### TS Plugin Install Lifecycle
 
-When you run `opencli plugin install`, TS plugins are automatically set up:
+When you run `ppcli plugin install`, TS plugins are automatically set up:
 
 1. **Clone** — `git clone --depth 1` from GitHub
 2. **npm install** — Resolves regular dependencies
@@ -214,13 +214,13 @@ On startup, if both `my-command.ts` and `my-command.js` exist, the `.js` version
 
 ### Command not found after install
 
-Restart opencli (or open a new terminal) — plugins are discovered at startup.
+Restart ppcli (or open a new terminal) — plugins are discovered at startup.
 
 ### TS plugin import errors
 
 If you see `Cannot find module '@jackwener/opencli/registry'`, the host symlink may be broken. Reinstall the plugin:
 
 ```bash
-opencli plugin uninstall my-plugin
-opencli plugin install github:user/opencli-plugin-my-plugin
+ppcli plugin uninstall my-plugin
+ppcli plugin install github:user/opencli-plugin-my-plugin
 ```

package/docs/guide/remote-orchestration.md

@@ -1,6 +1,6 @@
 # Remote Orchestration
 
-Run an OpenCLI command from a remote machine (a CI runner, an agent server, a sandbox) while the **browser session stays on your local laptop**. The remote command sees `localhost:19825` like usual; behind the scenes, traffic is tunneled back to the daemon and Chrome on your machine.
+Run an ppcli command from a remote machine (a CI runner, an agent server, a sandbox) while the **browser session stays on your local laptop**. The remote command sees `localhost:19825` like usual; behind the scenes, traffic is tunneled back to the daemon and Chrome on your machine.
 
 ## When you need this
 
@@ -45,8 +45,8 @@ While that session is open, anything on the remote connecting to `localhost:1982
 
 ```bash
 # On the remote server
-opencli twitter feed
-opencli browser open https://example.com
+ppcli twitter feed
+ppcli browser open https://example.com
 ```
 
 ::: tip
@@ -104,10 +104,10 @@ After setting up the tunnel, confirm the remote sees the daemon:
 ```bash
 # On the remote server
 curl -sf http://127.0.0.1:19825/ping && echo "daemon reachable"
-opencli doctor
+ppcli doctor
 ```
 
-`opencli doctor` from the remote should report the same extension version your local Chrome is running.
+`ppcli doctor` from the remote should report the same extension version your local Chrome is running.
 
 ## Caveats