@pasko70/pibo 1.9.7 → 1.9.9

package/dist/tools/guides.js

@@ -1,563 +0,0 @@
-export const RALPH_GUIDE = {
-    name: 'ralph',
-    description: 'Create, inspect, and control Pibo Ralph jobs from the CLI.',
-    content: `---
-name: ralph
-description: Creates and controls continuous Pibo agent jobs for implementation loops, bug fixing, validation, and PRD/story execution.
-allowed-tools: Bash(pibo:*), Bash(npm:*)
----
-
-# Ralph CLI Tool
-
-Ralph runs repeatable Pibo agent jobs. Use it when the user wants an implementation loop, PRD/story execution, bug fixing, validation, or a background job that can be started, stopped, inspected, and resumed.
-
-## Required Context
-
-Ralph jobs are app-global. Choose either:
-
-- room target: \`--room <current-room-id>\`
-- shared default target: \`--default-chat\`
-
-Inside the Pibo source repo, use \`npm run --silent dev -- ralph ...\` for uninstalled local changes. For the installed CLI, use \`pibo ralph ...\`.
-
-## Discover Templates
-
-\`\`\`bash
-pibo ralph templates
-pibo ralph templates --json
-pibo tools guide ralph ralph
-\`\`\`
-
-Good defaults:
-
-- \`prd-single-story-standard\`: one failing PRD story per run; promise-complete stop policy.
-- \`prd-batch-stories\`: multiple PRD stories in priority order; commit after each story.
-- \`single-run-objective\`: one focused non-PRD objective; stops after one completed run attempt.
-
-## Create Jobs
-
-Create stopped, inspect, then start:
-
-\`\`\`bash
-pibo ralph add \\
-  --room "<room-id>" \\
-  --template prd-single-story-standard \\
-  --name "Implement story X" \\
-  --prompt "Implement exactly one failing PRD story, test it, and commit." \\
-  --json
-
-pibo ralph start <job-id>
-\`\`\`
-
-Create and start immediately:
-
-\`\`\`bash
-pibo ralph add \\
-  --room "<room-id>" \\
-  --template single-run-objective \\
-  --name "Fix bug Y" \\
-  --prompt "Reproduce and fix bug Y, then run focused tests." \\
-  --start \\
-  --json
-\`\`\`
-
-Explicit options override template fields.
-
-Runtime overrides are optional and apply to sessions created by the job:
-
-\`\`\`bash
-pibo ralph add \\
-  --room "<room-id>" \\
-  --prompt "Use a specific runtime." \\
-  --model openai/gpt-5 \\
-  --thinking high \\
-  --fast \\
-  --json
-
-pibo ralph edit <job-id> --model openai/gpt-5 --thinking medium --no-fast --json
-pibo ralph edit <job-id> --clear-model --clear-thinking --clear-fast --json
-\`\`\`
-
-Use \`--model <provider/model>\`, \`--thinking off|minimal|low|medium|high|xhigh|max\`, and \`--fast\`/\`--no-fast\` to set runtime options. Use the \`--clear-*\` flags on \`edit\` to return to profile/default runtime behavior.
-
-## Inspect and Debug
-
-\`\`\`bash
-pibo ralph status --json
-pibo ralph list --all --json
-pibo ralph runs --job <job-id> --json
-pibo ralph policy show <job-id> --json
-\`\`\`
-
-Use \`runs --json\` to debug failures, session ids, completion state, and recent activity. Prefer bounded JSON output when another agent will parse it.
-
-## Control Jobs
-
-\`\`\`bash
-pibo ralph stop <job-id>      # finish current session, then stop
-pibo ralph cancel <job-id>    # abort current session and stop
-pibo ralph edit <job-id> --prompt "Updated objective" --json
-pibo ralph remove <job-id>
-\`\`\`
-
-Prefer \`stop\` for normal shutdown and \`cancel\` only when the active run is stuck or unsafe.
-
-## Safety
-
-1. Do not start many Ralph jobs unless the user asked for parallel work.
-2. Use templates first; avoid ad-hoc long prompts when a preset fits.
-3. Inspect with \`list --json\` and \`runs --json\` before editing or canceling an unknown job.
-4. If working in the source repo before install, use \`npm run --silent dev -- ralph ...\`.
-`,
-};
-export const AGENT_BROWSER_GUIDE = {
-    name: 'agent-browser',
-    description: 'Ref-based browser automation with the Agent Browser CLI.',
-    content: `---
-name: agent-browser
-description: Fast native browser automation CLI for AI agents. Use when you need to open pages, inspect snapshots, click refs, fill fields, and keep browser state under a Pibo-owned tool home.
-allowed-tools: Bash(agent-browser:*)
----
-
-# Browser Automation with Agent Browser
-
-Agent Browser uses refs from interactive snapshots. Inspect first, act on refs, then inspect again after navigation or DOM changes.
-
-## Prerequisites
-
-Initialize one shell with the Pibo tool environment:
-
-\`\`\`bash
-eval "$(pibo tools env agent-browser)"
-agent-browser doctor --offline --quick
-\`\`\`
-
-Inside the Pibo source repo, use \`eval "$(npm run --silent dev -- tools env agent-browser)"\`. The Pibo wrapper comes first on \`PATH\` and keeps state under \`AGENT_BROWSER_HOME\`, normally \`$PIBO_HOME/tools/agent-browser/home\`. For \`agent-browser@0.27.0\`, the wrapper also redirects \`HOME\` there by default so \`~/.agent-browser\` stays inside the tool home.
-
-## Core Workflow
-
-\`\`\`bash
-agent-browser open <url>
-agent-browser snapshot -i
-agent-browser click @e1
-agent-browser fill @e2 "text"
-agent-browser snapshot -i
-agent-browser get title
-agent-browser close --all
-\`\`\`
-
-Re-run \`snapshot -i\` after navigation, submit, scroll, animation, or any DOM-changing action. Do not reuse stale refs.
-
-## Sessions
-
-Use sessions for separate browser tasks:
-
-\`\`\`bash
-agent-browser --session pibo-check open https://example.com
-AGENT_BROWSER_SESSION=pibo-check agent-browser snapshot -i
-agent-browser session list
-\`\`\`
-
-Keep mutating commands against the same session serial. Avoid parallel \`click\`, \`fill\`, \`open\`, or \`snapshot\` calls for one session.
-
-## State and Profiles
-
-The wrapper defaults browser-launching commands to a persistent Pibo profile:
-
-\`\`\`bash
-agent-browser open https://example.com
-\`\`\`
-
-Opt out when needed:
-
-\`\`\`bash
-agent-browser --fresh-profile open https://example.com
-agent-browser --profile /path/to/profile open https://example.com
-agent-browser --session-name saved-check open https://example.com
-\`\`\`
-
-Treat profiles, saved states, auth vaults, cookies, and headers as secrets. Do not print or copy their contents into chat.
-
-## Authenticated Chat Web Work
-
-Prefer isolated leases when more than one agent may use authenticated Chat Web:
-
-\`\`\`bash
-eval "$(pibo tools agent-browser lease acquire --app pibo-chat --holder "$USER")"
-agent-browser open http://4788.192.168.0.204.sslip.io/apps/chat
-agent-browser snapshot -i
-\`\`\`
-
-To prepare the reusable template profile:
-
-\`\`\`bash
-eval "$(pibo tools agent-browser auth-template env --app pibo-chat)"
-agent-browser open http://4788.192.168.0.204.sslip.io/apps/chat
-\`\`\`
-
-Sign in once, close the browser, then acquire leases from the template.
-
-For an already-open browser, inspect CDP targets:
-
-\`\`\`bash
-pibo tools agent-browser targets
-pibo tools agent-browser attach-chat
-\`\`\`
-
-## Upstream Skills
-
-Pibo keeps the full upstream skill out of default runtime context. Fetch it only when needed:
-
-\`\`\`bash
-agent-browser skills get core --full
-\`\`\`
-`,
-};
-export const BROWSER_USE_GUIDE = {
-    name: 'browser-use',
-    description: 'Local browser automation with the browser-use CLI.',
-    content: `---
-name: browser-use
-description: Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, or extract information from web pages.
-allowed-tools: Bash(browser-use:*)
----
-
-# Browser Automation with browser-use CLI
-
-The browser-use command provides persistent browser automation. A background daemon keeps the browser open across commands, so repeated commands are fast.
-
-## Prerequisites
-
-Initialize one persistent browser-use shell by applying the Pibo tool environment once:
-
-\`\`\`bash
-eval "$(pibo tools env browser-use)"
-browser-use doctor
-\`\`\`
-
-Inside the Pibo source repo, use \`eval "$(npm run --silent dev -- tools env browser-use)"\` instead. Keep running later \`browser-use\` commands in that same shell; a new shell needs the one-time initialization again. If command substitution is not available, run the env command and apply the printed exports manually. On Linux, it includes detected desktop variables such as \`DISPLAY\`, \`WAYLAND_DISPLAY\`, and \`XAUTHORITY\` when a local desktop is available.
-
-The Pibo tool environment wraps \`browser-use\`: when a new browser daemon session is started, it starts a Pibo-managed persistent Chrome profile named \`PIBo\` with CDP and connects Browser Use to it. This avoids Browser Use's normal temporary profile copy, so sign-ins made in that profile stay on disk. Pass \`--fresh-profile\` to start a fresh temporary browser profile instead.
-
-## Core Workflow
-
-1. Navigate: \`browser-use --headed --session NAME open <url>\` when a desktop is available; otherwise use \`browser-use --session NAME open <url>\`
-2. Inspect: \`browser-use state\`
-3. Interact with indices from state: \`browser-use click 5\`, \`browser-use input 3 "text"\`
-4. Verify: \`browser-use state\`, \`browser-use get value <index>\`, \`browser-use eval "js"\`, or \`browser-use screenshot\`
-5. Repeat while the browser stays open
-
-Run browser-mutating commands one at a time per session. Do not issue parallel \`click\`, \`input\`, \`open\`, \`eval\`, or \`screenshot\` calls against the same session.
-
-If a command fails, run \`browser-use close\` first to clear the session, then retry.
-
-After navigation, submit, keypress navigation, major DOM changes, or scroll on complex pages, run \`state\` again before reusing element indices.
-
-## Browser Modes
-
-\`\`\`bash
-browser-use --headed open <url>                # Starts Pibo-managed persistent PIBo Chrome via CDP
-browser-use --fresh-profile open <url>         # Starts a fresh temporary browser profile
-browser-use --connect open <url>               # Connect to local Chrome via CDP (requires --remote-debugging-port)
-browser-use --profile "Default" open <url>     # Upstream profile mode; Browser Use may copy it to a temp dir
-\`\`\`
-
-## Commands
-
-\`\`\`bash
-# Navigation
-browser-use open <url>
-browser-use back
-browser-use scroll down
-browser-use scroll up
-browser-use switch <index>
-browser-use close-tab [index]
-
-# Page state
-browser-use state
-browser-use screenshot [path.png]
-browser-use screenshot --full path.png
-
-# Interactions
-browser-use click <index>
-browser-use click <x> <y>
-browser-use type "text"
-browser-use input <index> "text"
-browser-use input <index> ""
-browser-use keys "Enter"
-browser-use keys "Control+a"
-browser-use select <index> "option"
-browser-use upload <index> <path>
-browser-use hover <index>
-browser-use dblclick <index>
-browser-use rightclick <index>
-
-# Data extraction
-browser-use eval "js code"
-browser-use get title
-browser-use get html
-browser-use get html --selector "h1"
-browser-use get text <index>
-browser-use get value <index>
-browser-use get attributes <index>
-browser-use get bbox <index>
-
-# Wait
-browser-use wait selector "css"
-browser-use wait text "Success"
-
-# Cookies
-browser-use cookies get
-browser-use cookies get --url <url>
-browser-use cookies set <name> <value>
-browser-use cookies clear
-browser-use cookies export <file>
-browser-use cookies import <file>
-
-# Session
-browser-use close
-browser-use sessions
-browser-use close --all
-\`\`\`
-
-## Authenticated Browsing
-
-For the Pibo Chat Web App, prefer an isolated authenticated lease when multiple agents may use the browser at the same time:
-
-\`\`\`bash
-eval "$(pibo tools browser-use lease acquire --app pibo-chat --holder "$USER")"
-browser-use state
-\`\`\`
-
-The lease exports \`BROWSER_USE_HOME\`, \`PIBO_BROWSER_USE_SESSION\`, \`PIBO_BROWSER_USE_CHROME_USER_DATA_DIR\`, and \`PIBO_BROWSER_USE_DEFAULT_PROFILE\`. The Pibo browser-use wrapper uses \`PIBO_BROWSER_USE_SESSION\` as the default session, so later commands can omit \`--session\` in that shell.
-
-Before acquiring leases, prepare one authenticated template profile:
-
-\`\`\`bash
-eval "$(pibo tools browser-use auth-template env)"
-browser-use --headed open http://4788.192.168.0.204.sslip.io/apps/chat
-\`\`\`
-
-Sign in once in that template browser, then close it before agents acquire leases. Inspect and clean up leases with:
-
-\`\`\`bash
-pibo tools browser-use lease list
-pibo tools browser-use lease release <lease-id>
-pibo tools browser-use lease reap-stale
-\`\`\`
-
-If a shared legacy session is already available, inspect it before navigating:
-
-\`\`\`bash
-browser-use --session pibo-auth state
-\`\`\`
-
-If \`pibo-auth\` is unavailable and must be recreated, the default wrapper behavior is enough:
-
-\`\`\`bash
-browser-use --headed --session pibo-auth open http://4788.192.168.0.204.sslip.io/apps/chat
-\`\`\`
-
-For low-level Chat Web debugging, prefer an already-open authenticated browser over launching a new profile. Start by listing CDP targets:
-
-\`\`\`bash
-npm run dev -- tools browser-use targets
-npm run dev -- tools browser-use attach-chat
-curl -s http://127.0.0.1:56663/json/list
-\`\`\`
-
-Inspect Chat Web targets and pick the one that is authenticated and has a composer textarea. \`attach-chat\` prints shell exports for the best existing authenticated Chat target. If Browser Use cannot attach cleanly or MCP resources are unavailable, use the target \`webSocketDebuggerUrl\` from \`targets\`, \`attach-chat\`, or \`/json/list\` and direct CDP \`Runtime.evaluate\`, \`Network\`, and DOM inspection.
-
-For authenticated sites, the default Pibo wrapper path is the persistent path. Use \`profile list\` only to inspect available Chrome profiles:
-
-\`\`\`bash
-browser-use profile list
-\`\`\`
-
-To intentionally use a real local Chrome user data directory instead of the Pibo-managed one, set \`PIBO_BROWSER_USE_CHROME_USER_DATA_DIR\` before starting the session.
-
-If \`browser-use --connect\` cannot find Chrome, ask the user whether they want to relaunch Chrome with remote debugging or use a managed Chromium profile.
-
-## Tips
-
-1. Apply \`eval "$(pibo tools env browser-use)"\` once per persistent shell before using the CLI from Pibo, then reuse that shell.
-2. Always run \`state\` before using element indices.
-3. Re-run \`state\` after navigation or large DOM changes because element indices can change.
-4. For forms, verify inputs with \`get value <index>\`; \`state\` does not always show current text values.
-5. For large pages, prefer \`get html --selector\`, \`get text <index>\`, or \`eval\` over dumping the full page with \`state\`.
-6. Use \`--headed\` when debugging browser behavior if the env output includes a display.
-7. Sessions persist until \`browser-use close\`.
-8. Use \`--session NAME\` for separate browser sessions.
-9. Wrap long waits or JavaScript-heavy mutations with an external timeout, for example \`timeout 30s browser-use --session NAME wait text "Success"\`.
-10. Prefer \`--json\` for machine-readable \`get\` and \`sessions\` results.
-11. \`select\` confirms the visible option text, while \`get value\` returns the underlying option value.
-12. Avoid \`browser-use --version\`; this CLI does not support it.
-13. Avoid \`extract\`; it is listed by the CLI but is not implemented in this version.
-14. If Chrome fails to start with a "SingletonLock" error, the wrapper auto-detects and terminates stale Chrome processes holding the lock. Retry your command.
-`,
-};
-export const GRAPHIFY_GUIDE = {
-    name: 'graphify',
-    description: 'Generate codebase knowledge graphs with the Graphify CLI.',
-    content: `---
-name: graphify
-description: Generates interactive codebase knowledge graphs and markdown reports from a workspace folder.
-allowed-tools: Bash(graphify:*)
----
-
-# Codebase Visualization with Graphify
-
-Graphify turns a folder into derived artifacts under \`graphify-out/\`:
-
-- \`graphify-out/graph.html\` — an interactive clickable graph;
-- \`graphify-out/graph.json\` — machine-readable graph data;
-- \`graphify-out/GRAPH_REPORT.md\` — a markdown summary with key concepts and suggested questions.
-
-Use it when a user asks to graph, map, visualize, or quickly understand a repo/workspace shape.
-
-## Prerequisites
-
-Install and apply the Pibo tool environment:
-
-\`\`\`bash
-pibo tools install graphify
-eval "$(pibo tools env graphify)"
-graphify --help
-\`\`\`
-
-Inside the Pibo source repo, use \`npm run --silent dev -- tools ...\` while testing local changes:
-
-\`\`\`bash
-npm run --silent dev -- tools install graphify
-eval "$(npm run --silent dev -- tools env graphify)"
-\`\`\`
-
-The installer uses the PyPI package \`graphifyy\` and runs \`graphify install --platform pi\` so the CLI is ready for Pi/Pibo workflows.
-
-## Core Workflow
-
-1. Choose the workspace path. Prefer the active Pibo Room or session workspace boundary when known.
-2. Run Graphify from that folder or pass the target path explicitly. With \`graphifyy==0.9.x\`, \`graphify .\` writes extraction output under \`graphify-out/\`.
-3. For a code-only workspace without an LLM key, run \`graphify cluster-only . --no-label\` after extraction to produce the HTML graph and markdown report.
-4. Put generated artifacts in an ignored room/session artifact directory when possible; do not commit them unless the user explicitly asks.
-5. Read \`graphify-out/GRAPH_REPORT.md\` first, then open \`graphify-out/graph.html\` when an interactive view is useful.
-
-\`\`\`bash
-cd /path/to/workspace
-graphify .
-graphify cluster-only . --no-label
-ls graphify-out/graph.html graphify-out/graph.json graphify-out/GRAPH_REPORT.md
-\`\`\`
-
-## Pibo Usage Notes
-
-- For Room-bound work, graph the Room workspace rather than the agent harness checkout unless the user asks otherwise.
-- If generating inside a Git repo, check \`git status --short\` before and after so graph artifacts are not accidentally included in unrelated commits.
-- Code-only extraction can run without an LLM API key. Including docs, README files, papers, images, or semantic-labeling steps may require a configured Graphify backend/API key; if no key is available, graph a code-only subdirectory or skip semantic labels with \`cluster-only . --no-label\`.
-- For large monorepos, start with a subdirectory such as \`src/\`, a code package, or a docs folder only when the needed LLM backend is configured.
-- Treat graph output as derived data. Recompute on demand when the branch or workspace changes.
-
-## Next Commands
-
-\`\`\`bash
-pibo tools show graphify
-pibo tools guide graphify graphify
-pibo tools path graphify
-pibo tools doctor graphify
-\`\`\`
-`,
-};
-export const REMOTE_BROWSER_GUIDE = {
-    name: 'remote-browser',
-    description: 'Browser automation workflow for sandboxed or remote agents.',
-    content: `---
-name: remote-browser
-description: Controls a browser from a sandboxed or remote machine. Use when the agent has no local GUI and needs to navigate websites, interact with web pages, take screenshots, or expose local dev servers via tunnels.
-allowed-tools: Bash(browser-use:*)
----
-
-# Browser Automation for Sandboxed Agents
-
-This guide is for agents running in a sandbox, CI, cloud VM, or remote coding environment.
-
-## Prerequisites
-
-Initialize one persistent browser-use shell by applying the Pibo tool environment once:
-
-\`\`\`bash
-eval "$(pibo tools env browser-use)"
-browser-use doctor
-\`\`\`
-
-Inside the Pibo source repo, use \`eval "$(npm run --silent dev -- tools env browser-use)"\` instead. Keep running later \`browser-use\` commands in that same shell; a new shell needs the one-time initialization again. If command substitution is not available, run the env command and apply the printed exports manually. On Linux, this lets Browser Use see a local desktop session when one exists.
-
-## Core Workflow
-
-1. Navigate: \`browser-use --headed --session NAME open <url>\` when a desktop is available; otherwise use \`browser-use --session NAME open <url>\`
-2. Inspect: \`browser-use state\`
-3. Interact with indices from state: \`browser-use click 5\`, \`browser-use input 3 "text"\`
-4. Verify: \`browser-use state\`, \`browser-use get value <index>\`, \`browser-use eval "js"\`, or \`browser-use screenshot\`
-5. Cleanup: \`browser-use close\`
-
-Run browser-mutating commands one at a time per session. Use separate session names for parallel workflows.
-After navigation, submit, keypress navigation, major DOM changes, or scroll on complex pages, run \`state\` again before reusing element indices.
-
-## Browser Modes
-
-\`\`\`bash
-browser-use open <url>
-browser-use --headed open <url>
-browser-use --connect open <url>
-browser-use --cdp-url ws://localhost:9222/devtools/browser/... open <url>
-\`\`\`
-
-## Commands
-
-\`\`\`bash
-browser-use open <url>
-browser-use back
-browser-use state
-browser-use screenshot [path.png]
-browser-use click <index>
-browser-use input <index> "text"
-browser-use keys "Enter"
-browser-use wait selector "css"
-browser-use wait text "Success"
-browser-use get html
-browser-use eval "document.title"
-browser-use switch <index>
-browser-use close-tab [index]
-browser-use close
-\`\`\`
-
-## Exposing Local Dev Servers
-
-\`\`\`bash
-browser-use tunnel <port>
-browser-use tunnel list
-browser-use open <tunnel-url>
-browser-use tunnel stop <port>
-\`\`\`
-
-Tunnels are independent from browser sessions and can persist after \`browser-use close\`.
-
-## Multiple Sessions
-
-\`\`\`bash
-browser-use --session agent-a open https://example.com
-browser-use --session agent-b open https://example.org
-\`\`\`
-
-Use named sessions when multiple agents or workflows need separate browsers.
-
-## Troubleshooting
-
-- Browser will not start: run \`browser-use close\`, then retry.
-- Element not found: run \`browser-use scroll down\`, then \`browser-use state\`.
-- Form value unclear: use \`browser-use get value <index>\`.
-- Large page state is noisy: use \`get html --selector\`, \`get text <index>\`, or \`eval\`.
-- Need to debug visually: use \`--headed\`.
-- Long wait hangs: wrap the command with \`timeout 30s\`.
-- Tunnel not working: run \`browser-use tunnel list\`.
-`,
-};