@cydm/pie 1.0.50 → 2.1.0

package/README.md

@@ -299,31 +299,48 @@ The full contract (identity rules, schema, host integration) lives in [`docs/ext
 
 ## Browser Tools
 
-The built-in `browser-tools` skill uses Microsoft's Playwright CLI for visible browser automation. Its runtime dependencies ship with the CLI; do not run `npm install` inside the skill directory.
+The built-in `chrome-devtools-axi` skill uses the chrome-devtools-axi CLI to drive a real Chrome browser over the Chrome DevTools Protocol. Its runtime dependencies ship with the CLI; do not run `npm install` inside the skill directory.
 
-Resolve the skill resource and run Playwright commands:
+Resolve the skill resource and run browser commands:
 
 ```bash
-node <resolvedPath for browser-tools/playwright-cli.js> open https://example.com
-node <resolvedPath for browser-tools/playwright-cli.js> snapshot
-node <resolvedPath for browser-tools/playwright-cli.js> screenshot
-node <resolvedPath for browser-tools/playwright-cli.js> console
-node <resolvedPath for browser-tools/playwright-cli.js> requests
+node <resolvedPath for chrome-devtools-axi/chrome-devtools-axi-cli.js> open https://example.com
+node <resolvedPath for chrome-devtools-axi/chrome-devtools-axi-cli.js> snapshot
+node <resolvedPath for chrome-devtools-axi/chrome-devtools-axi-cli.js> screenshot /tmp/page.png
+node <resolvedPath for chrome-devtools-axi/chrome-devtools-axi-cli.js> console
+node <resolvedPath for chrome-devtools-axi/chrome-devtools-axi-cli.js> network
 ```
 
-If Playwright's Chromium browser is not installed, run:
+The CLI launches or attaches to a real Chrome/Edge browser; see `--help` for connection modes (headed mode, auto-connect, custom profile, remote browser URL) and `CHROME_DEVTOOLS_AXI_SESSION` for concurrent isolated sessions.
 
-```bash
-node <resolvedPath for browser-tools/playwright-cli.js> install-browser chromium
-```
+Run `pie doctor` to check whether chrome-devtools-axi and a Chrome browser are discoverable.
+
+## Terminal UI Automation
+
+The built-in `tui-use` skill drives interactive terminal programs - REPLs, pdb/gdb debugger sessions, and full-screen TUI apps - through a PTY: read the screen as text, send keystrokes, and wait for output with `wait`/`wait --text`. Pie ships only the skill definition; the CLI runs on demand via `npx -y --install-strategy=nested tui-use@0.1.20` (the version tag in the skill is the lock). Use plain `bash` for anything non-interactive. First invocation installs the PTY runtime (macOS/Windows prebuilt; Linux compiles node-pty from source) and starts a session daemon (state in `~/.tui-use`); Windows ConPTY is not officially verified upstream.
+
+## Desktop Control (computer-use)
+
+The built-in `computer-use` extension (vendored from `@injaneity/pi-computer-use@0.5.1`, frozen and self-maintained by Pie) controls real desktop applications on macOS, Windows, and Linux through a native accessibility helper. Desktop control is a last resort - prefer API, CLI, or web tools whenever they can accomplish the task.
+
+Tools are tiered:
+
+- **Observe tier (default)** - `find_roots`, `observe_ui`, `search_ui`, `expand_ui`, `inspect_ui`, `read_text`, `wait_for`, plus the CDP browser tools `launch_browser`, `navigate_browser`, `evaluate_browser`. These only read screen/UI state.
+- **Act tier (first-use confirmation)** - `act_ui` synthesizes real input (click, type, scroll, keypress, drag). The first `act_ui` call in each session asks for confirmation (class `computer_use_act`); YOLO mode bypasses it, and non-interactive hosts block it deterministically.
+
+Platform notes:
+
+- **macOS** (14+): the signed helper app installs to `~/.pie/computer-use/pie-computer-use.app` on first use. Grant **Accessibility** and **Screen Recording** to `pie-computer-use.app` in System Settings → Privacy & Security; interactive sessions guide you through the prompts. Re-grant after helper updates (re-signing invalidates old grants).
+- **Windows**: the helper installs to `~/.pie/helpers/computer-use/windows-bridge.exe` and needs an interactive desktop session.
+- **Linux**: the helper installs to `~/.pie/helpers/computer-use/linux-bridge` and needs an AT-SPI2 bus (a running desktop session; headless servers are not supported).
 
-Run `pie doctor` to check whether Playwright CLI and its browser runtime are discoverable.
+Config: `~/.pie/extensions/computer-use.json` (user) or `.pie/computer-use.json` (project) with `browser_use`, `headless`, `cursor_overlay`, `managed_browser`; env overrides `PIE_COMPUTER_USE_BROWSER_USE` / `PIE_COMPUTER_USE_HEADLESS` / `PIE_COMPUTER_USE_CURSOR_OVERLAY` / `PIE_COMPUTER_USE_MANAGED_BROWSER`. Run `/computer-use` (slash command) to inspect the loaded config, and `pie doctor` for helper install status. The extension can be toggled like any other (`/settings/extensions`, identity `computer-use`).
 
 ## Web Research
 
 Pie exposes one default model-visible web tool: `web_research`. Use it for public web research, current information, online documentation, and internet inspiration. Pass `query` for research, `url` to fetch a known page/PDF, or `query` with `mode: "search"` for low-level search results. Workspace search remains separate: use `grep_text`, `find_files`, and `list_dir` for local repository content.
 
-`web_search` and `web_fetch` remain lower-level internal primitives for probes, diagnostics, and tests; they are not separate default model-visible tools. `web_search` does not scrape DuckDuckGo or fall back to `bash` with `curl` or Python HTTP scripts. If the configured provider/model cannot perform native web search, Pie returns a clear unavailable result with provider/configuration details. In the CLI, `web_research` can use browser-tools for browser-rendered sources when the Playwright runtime is available; Unity reports those pages as `requires_browser`.
+`web_search` and `web_fetch` remain lower-level internal primitives for probes, diagnostics, and tests; they are not separate default model-visible tools. `web_search` does not scrape DuckDuckGo or fall back to `bash` with `curl` or Python HTTP scripts. If the configured provider/model cannot perform native web search, Pie returns a clear unavailable result with provider/configuration details. In the CLI, `web_research` can use chrome-devtools-axi for browser-rendered sources when a Chrome browser is available; Unity reports those pages as `requires_browser`.
 
 `web_research` records route health and latency in Pie's state directory so later runs can prefer providers with better source quality, fewer timeouts, and lower rate-limit pressure. `pie doctor --json` reports the recorded provider health, and `verify:web` writes web metrics including p50/p95 latency, failure categories, and citation quality artifacts.
 
@@ -346,7 +363,7 @@ pie doctor
 pie doctor --json
 ```
 
-Doctor checks Node/npm, model configuration, API key availability, writable Pie data paths, Playwright browser readiness, Unity bridge hints, and runtime log location. User-facing errors stay concise; detailed debugging goes to `~/.pie/logs/pie-cli.log` and session trace artifacts.
+Doctor checks Node/npm, model configuration, API key availability, writable Pie data paths, chrome-devtools-axi and Chrome browser readiness, Unity bridge hints, and runtime log location. User-facing errors stay concise; detailed debugging goes to `~/.pie/logs/pie-cli.log` and session trace artifacts.
 
 ## Output Modes
 
@@ -396,7 +413,7 @@ npm run verify:terminal:matrix
 Use `npm run verify:agent` when model credentials are available and you want the real daily agent gate.
 Use `npm run verify:agent:nightly` before release candidates that claim real-provider reliability.
 Use `UNITY_EDITOR="/path/to/Unity" npm run verify:unity:reliability` before Unity release candidates. For live Unity Dev RPC coverage, run `PIE_UNITY_REAL_RPC=1 UNITY_EDITOR="/path/to/Unity" npm run verify:unity:reliability`.
-Set `PIE_REAL_BROWSER=1` when you want `verify:browser` to open a real browser session instead of only checking the Playwright CLI contract.
+Set `PIE_REAL_BROWSER=1` when you want `verify:browser` to open a real browser session instead of only checking the chrome-devtools-axi CLI contract.
 Set `PIE_REAL_WEB=1` when you want `verify:web` to run real provider web research smoke with fetched or browser-read citations.
 
 ## Publishing

package/dist/builtin/extensions/ask-user/index.js

@@ -1,9 +1,10 @@
 import { createRequire as __createRequire } from "node:module"; const require = __createRequire(import.meta.url);
 import {
   createAskUserCapability
-} from "../../../chunks/chunk-DZS34ACX.js";
-import "../../../chunks/chunk-FKAO25XH.js";
-import "../../../chunks/chunk-K6ZOCJ4V.js";
+} from "../../../chunks/chunk-PMPD56N2.js";
+import "../../../chunks/chunk-QJH6YN2W.js";
+import "../../../chunks/chunk-IM43UYVV.js";
+import "../../../chunks/chunk-XXGYUYXI.js";
 import "../../../chunks/chunk-LZQXQOPJ.js";
 
 // builtin/extensions/ask-user/index.ts

package/dist/builtin/extensions/ask-user/package.json

@@ -1,9 +1,10 @@
 {
-  "name": "@pie/ask-user-extension",
-  "version": "1.0.0",
-  "type": "module",
-  "pie": {
-    "name": "ask-user",
-    "main": "index.ts"
-  }
+	"name": "@pie/ask-user-extension",
+	"version": "1.0.0",
+	"type": "module",
+	"pie": {
+		"name": "ask-user",
+		"main": "index.js"
+	},
+	"main": "index.js"
 }

package/dist/builtin/extensions/changelog/package.json

@@ -1,11 +1,11 @@
 {
-  "name": "@pie/extension-changelog",
-  "version": "1.0.0",
-  "description": "Intelligent changelog management with gap detection",
-  "main": "index.ts",
-  "type": "module",
-  "pie": {
-    "name": "changelog",
-    "main": "index.ts"
-  }
+	"name": "@pie/extension-changelog",
+	"version": "1.0.0",
+	"description": "Intelligent changelog management with gap detection",
+	"main": "index.js",
+	"type": "module",
+	"pie": {
+		"name": "changelog",
+		"main": "index.js"
+	}
 }