better-dsh 0.2.5-c → 0.2.5-e

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/google-workspace.md

@@ -1,191 +0,0 @@
----
-sidebar_position: 2
-sidebar_label: "Google Workspace"
-title: "Google Workspace — Gmail, Calendar, Drive, Sheets & Docs"
-description: "Send email, manage calendar events, search Drive, read/write Sheets, and access Docs — all through OAuth2-authenticated Google APIs"
----
-
-# Google Workspace Skill
-
-Gmail, Calendar, Drive, Contacts, Sheets, and Docs integration for Hermes. Uses OAuth2 with automatic token refresh. Prefers the [Google Workspace CLI (`gws`)](https://github.com/googleworkspace/cli) when available for broader coverage, and falls back to Google's Python client libraries otherwise.
-
-**Skill path:** `skills/productivity/google-workspace/`
-
-## Setup
-
-The setup is fully agent-driven — ask Hermes to set up Google Workspace and it walks you through each step. The flow:
-
-1. **Create a Google Cloud project** and enable the required APIs (Gmail, Calendar, Drive, Sheets, Docs, People)
-2. **Create OAuth 2.0 credentials** (Desktop app type) and download the client secret JSON
-3. **Authorize** — Hermes generates an auth URL, you approve in the browser, paste back the redirect URL
-4. **Done** — token auto-refreshes from that point on
-
-:::tip Email-only users
-If you only need email (no Calendar/Drive/Sheets), use the **himalaya** skill instead — it works with a Gmail App Password and takes 2 minutes. No Google Cloud project needed.
-:::
-
-## Gmail
-
-### Searching
-
-```bash
-$GAPI gmail search "is:unread" --max 10
-$GAPI gmail search "from:boss@company.com newer_than:1d"
-$GAPI gmail search "has:attachment filename:pdf newer_than:7d"
-```
-
-Returns JSON with `id`, `from`, `subject`, `date`, `snippet`, and `labels` for each message.
-
-### Reading
-
-```bash
-$GAPI gmail get MESSAGE_ID
-```
-
-Returns the full message body as text (prefers plain text, falls back to HTML).
-
-### Sending
-
-```bash
-# Basic send
-$GAPI gmail send --to user@example.com --subject "Hello" --body "Message text"
-
-# HTML email
-$GAPI gmail send --to user@example.com --subject "Report" \
-  --body "<h1>Q4 Results</h1><p>Details here</p>" --html
-
-# Custom From header (display name + email)
-$GAPI gmail send --to user@example.com --subject "Hello" \
-  --from '"Research Agent" <user@example.com>' --body "Message text"
-
-# With CC
-$GAPI gmail send --to user@example.com --cc "team@example.com" \
-  --subject "Update" --body "FYI"
-```
-
-### Custom From Header
-
-The `--from` flag lets you customize the sender display name on outgoing emails. This is useful when multiple agents share the same Gmail account but you want recipients to see different names:
-
-```bash
-# Agent 1
-$GAPI gmail send --to client@co.com --subject "Research Summary" \
-  --from '"Research Agent" <shared@company.com>' --body "..."
-
-# Agent 2  
-$GAPI gmail send --to client@co.com --subject "Code Review" \
-  --from '"Code Assistant" <shared@company.com>' --body "..."
-```
-
-**How it works:** The `--from` value is set as the RFC 5322 `From` header on the MIME message. Gmail allows customizing the display name on your own authenticated email address without any additional configuration. Recipients see the custom display name (e.g. "Research Agent") while the email address stays the same.
-
-**Important:** If you use a *different email address* in `--from` (not the authenticated account), Gmail requires that address to be configured as a [Send As alias](https://support.google.com/mail/answer/22370) in Gmail Settings → Accounts → Send mail as.
-
-The `--from` flag works on both `send` and `reply`:
-
-```bash
-$GAPI gmail reply MESSAGE_ID \
-  --from '"Support Bot" <shared@company.com>' --body "We're on it"
-```
-
-### Replying
-
-```bash
-$GAPI gmail reply MESSAGE_ID --body "Thanks, that works for me."
-```
-
-Automatically threads the reply (sets `In-Reply-To` and `References` headers) and uses the original message's thread ID.
-
-### Labels
-
-```bash
-# List all labels
-$GAPI gmail labels
-
-# Add/remove labels
-$GAPI gmail modify MESSAGE_ID --add-labels LABEL_ID
-$GAPI gmail modify MESSAGE_ID --remove-labels UNREAD
-```
-
-## Calendar
-
-```bash
-# List events (defaults to next 7 days)
-$GAPI calendar list
-$GAPI calendar list --start 2026-03-01T00:00:00Z --end 2026-03-07T23:59:59Z
-
-# Create event (timezone required)
-$GAPI calendar create --summary "Team Standup" \
-  --start 2026-03-01T10:00:00-07:00 --end 2026-03-01T10:30:00-07:00
-
-# With location and attendees
-$GAPI calendar create --summary "Lunch" \
-  --start 2026-03-01T12:00:00Z --end 2026-03-01T13:00:00Z \
-  --location "Cafe" --attendees "alice@co.com,bob@co.com"
-
-# Delete event
-$GAPI calendar delete EVENT_ID
-```
-
-:::warning
-Calendar times **must** include a timezone offset (e.g. `-07:00`) or use UTC (`Z`). Bare datetimes like `2026-03-01T10:00:00` are ambiguous and will be treated as UTC.
-:::
-
-## Drive
-
-```bash
-$GAPI drive search "quarterly report" --max 10
-$GAPI drive search "mimeType='application/pdf'" --raw-query --max 5
-```
-
-## Sheets
-
-```bash
-# Read a range
-$GAPI sheets get SHEET_ID "Sheet1!A1:D10"
-
-# Write to a range
-$GAPI sheets update SHEET_ID "Sheet1!A1:B2" --values '[["Name","Score"],["Alice","95"]]'
-
-# Append rows
-$GAPI sheets append SHEET_ID "Sheet1!A:C" --values '[["new","row","data"]]'
-```
-
-## Docs
-
-```bash
-$GAPI docs get DOC_ID
-```
-
-Returns the document title and full text content.
-
-## Contacts
-
-```bash
-$GAPI contacts list --max 20
-```
-
-## Output Format
-
-All commands return JSON. Key fields per service:
-
-| Command | Fields |
-|---------|--------|
-| `gmail search` | `id`, `threadId`, `from`, `to`, `subject`, `date`, `snippet`, `labels` |
-| `gmail get` | `id`, `threadId`, `from`, `to`, `subject`, `date`, `labels`, `body` |
-| `gmail send/reply` | `status`, `id`, `threadId` |
-| `calendar list` | `id`, `summary`, `start`, `end`, `location`, `description`, `htmlLink` |
-| `calendar create` | `status`, `id`, `summary`, `htmlLink` |
-| `drive search` | `id`, `name`, `mimeType`, `modifiedTime`, `webViewLink` |
-| `contacts list` | `name`, `emails`, `phones` |
-| `sheets get` | 2D array of cell values |
-
-## Troubleshooting
-
-| Problem | Fix |
-|---------|-----|
-| `NOT_AUTHENTICATED` | Run setup (ask Hermes to set up Google Workspace) |
-| `REFRESH_FAILED` | Token revoked — re-run authorization steps |
-| `HttpError 403: Insufficient Permission` | Missing scope — revoke and re-authorize with the right services |
-| `HttpError 403: Access Not Configured` | API not enabled in Google Cloud Console |
-| `ModuleNotFoundError` | Run setup script with `--install-deps` |

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/optional/autonomous-ai-agents/autonomous-ai-agents-antigravity-cli.md

@@ -1,259 +0,0 @@
----
-title: "Antigravity Cli — Operate the Antigravity CLI (agy): plugins, auth, sandbox"
-sidebar_label: "Antigravity Cli"
-description: "Operate the Antigravity CLI (agy): plugins, auth, sandbox"
----
-
-{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
-
-# Antigravity Cli
-
-Operate the Antigravity CLI (agy): plugins, auth, sandbox.
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Optional — install with `hermes skills install official/autonomous-ai-agents/antigravity-cli` |
-| Path | `optional-skills/autonomous-ai-agents\antigravity-cli` |
-| Version | `0.2.0` |
-| Author | Tony Simons (asimons81), Hermes Agent |
-| License | MIT |
-| Platforms | linux, macos, windows |
-| Tags | `Coding-Agent`, `Antigravity`, `CLI`, `Auth`, `Plugins`, `Sandbox` |
-| Related skills | [`grok`](/docs/user-guide/skills/optional/autonomous-ai-agents/autonomous-ai-agents-grok), [`codex`](/docs/user-guide/skills/bundled/autonomous-ai-agents/autonomous-ai-agents-codex), [`claude-code`](/docs/user-guide/skills/bundled/autonomous-ai-agents/autonomous-ai-agents-claude-code), [`hermes-agent`](/docs/user-guide/skills/bundled/autonomous-ai-agents/autonomous-ai-agents-hermes-agent) |
-
-## Reference: full SKILL.md
-
-:::info
-The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
-:::
-
-# Antigravity CLI (`agy`)
-
-Operator guide for the Antigravity CLI, invoked as `agy`. Run all `agy`
-commands through the Hermes `terminal` tool; inspect its config and logs with
-`read_file`. This skill is reference + procedure — it does not wrap a network
-API, so there is nothing to authenticate from Hermes itself.
-
-## When to Use
-
-- Installing, updating, or smoke-testing the `agy` binary
-- Driving non-interactive `agy --print` / `agy -p` one-shots
-- Debugging Antigravity auth, sandbox, permissions, or plugin state
-- Reading Antigravity settings, keybindings, conversations, or logs
-
-## Mental model
-
-Antigravity has two layers — keep them distinct or the guidance will be wrong:
-
-1. **Shell wrapper commands** — `agy help`, `agy install`, `agy plugin`,
-   `agy update`, `agy changelog`. Run these through the `terminal` tool.
-2. **Interactive in-session slash commands** — `/config`, `/permissions`,
-   `/skills`, `/agents`, etc. These only exist inside a running `agy` TUI
-   session, not on the shell wrapper.
-
-`agy help` shows the shell wrapper surface, NOT the in-session slash commands.
-
-## Prerequisites
-
-- The `agy` binary on PATH. Verify through the `terminal` tool:
-  `command -v agy && agy --version`.
-- No env vars or API keys required by this skill — Antigravity manages its own
-  auth via the OS keyring / browser sign-in (see Authentication below).
-
-## How to Run
-
-Invoke every `agy` command through the `terminal` tool. Examples:
-
-```
-terminal(command="agy --version")
-terminal(command="agy help")
-terminal(command="agy plugin list")
-terminal(command="agy --print 'Summarize the repo in 3 bullets'", workdir="/path/to/project")
-```
-
-For an interactive multi-turn TUI session, launch `agy` with `pty=true` (and
-tmux for capture/monitoring), the same pattern the `codex` / `claude-code`
-skills use. For one-shot smoke tests and scripted prompts, prefer
-`agy --print` (non-interactive).
-
-To inspect Antigravity's own files, use `read_file` on the paths under Core
-paths below — do not `cat` them through the terminal.
-
-## Delegation patterns
-
-`agy` is a coding-agent backend in the same family as `codex` / `claude-code`,
-so the same delegation shapes apply. Use these when handing real work (features,
-fixes, reviews, second opinions) to Antigravity rather than just smoke-testing.
-
-### One-shot (preferred for scripted prompts and second opinions)
-
-```
-terminal(command="agy -p 'Review this diff for bugs and security issues' --model 'Gemini 3.1 Pro (High)'", workdir="/path/to/repo", timeout=300)
-```
-
-`-p` is non-interactive: it runs the prompt and exits. Pick the engine with
-`--model` (run `agy models` for the exact display strings, e.g.
-`'Gemini 3.1 Pro (High)'`, `'Claude Opus 4.6 (Thinking)'`). Add extra context
-roots with repeatable `--add-dir`.
-
-### Long / bounded runs (tests, builds, multi-file changes)
-
-Background it and get notified on completion, the same as the `codex` skill:
-
-```
-terminal(command="agy -p 'Implement the change described in TASK.md and run the tests' --dangerously-skip-permissions", workdir="/path/to/repo", background=true, notify_on_complete=true)
-# then: process(action="poll"/"log"/"wait", session_id=<id>)
-```
-
-### Interactive multi-turn (PTY + tmux)
-
-For a conversational session, launch `agy -i` (or bare `agy`) under `pty=true`
-with tmux for `capture-pane` / `send-keys`, exactly the pattern documented in
-the `codex` / `claude-code` skills. Resume later with `--continue` / `-c` or a
-specific `--conversation <id>`.
-
-### Parallel instances (batch sub-issue / worktree fan-out)
-
-Create one git worktree per task and launch an independent `agy -p` in each
-(background), then collect results — same worktree fan-out the `codex` skill
-uses for batch issue fixing. Bound concurrency to what the machine and your
-review capacity can absorb.
-
-### Output + bounding caveat (differs from Claude Code)
-
-- `agy -p` returns **plain text** — there is **no `--output-format json`** and
-  no result envelope with `session_id` / cost / turn count. Parse stdout
-  directly; don't expect a JSON object.
-- There is **no `--max-turns`**. A print run is bounded by **`--print-timeout`**
-  (default `5m`). Raise it for long tasks: `--print-timeout 20m`. Pair with the
-  `terminal` `timeout=` so the outer call doesn't cut the run short.
-
-### Orchestration boundary
-
-Antigravity is a **worker execution backend or third-opinion reviewer** — an
-execution detail owned by the agent/profile running a task, NOT a first-class
-orchestration primitive. Do not put `agy` on a kanban board as its own card or
-treat it as a coordination layer; route work through the normal task graph and
-let the assigned worker choose `agy` (vs. codex/claude-code/direct tools) as its
-method. Reach for it explicitly only when the user asks, when a worker is
-configured to wrap it, or when you want a Gemini-family cross-check against
-another agent's plan or diff.
-
-## Core paths
-
-- Binary / entrypoint: `agy`
-- App data dir: `~/.gemini/antigravity-cli/`
-- Settings file: `~/.gemini/antigravity-cli/settings.json`
-- Keybindings file: `~/.gemini/antigravity-cli/keybindings.json`
-- Logs: `~/.gemini/antigravity-cli/log/cli-*.log`
-- Conversations: `~/.gemini/antigravity-cli/conversations/`
-- Brain artifacts: `~/.gemini/antigravity-cli/brain/`
-- History: `~/.gemini/antigravity-cli/history.jsonl`
-- Plugin staging: `~/.gemini/antigravity-cli/plugins/<plugin_name>/`
-
-## Quick Reference
-
-### Wrapper commands
-- `agy changelog`
-- `agy help`
-- `agy install`
-- `agy plugin` / `agy plugins`
-- `agy update`
-
-### Useful flags
-- `--add-dir`
-- `--continue` / `-c`
-- `--conversation`
-- `--dangerously-skip-permissions`
-- `--print` / `-p`
-- `--print-timeout`
-- `--prompt`
-- `--prompt-interactive` / `-i`
-- `--sandbox`
-- `--log-file`
-- `--version`
-
-### Plugin subcommands (`agy plugin --help`)
-- `list`, `import [source]`, `install <target>`, `uninstall <name>`,
-  `enable <name>`, `disable <name>`, `validate [path]`, `link <mp> <target>`,
-  `help`
-
-### Install flags (`agy install --help`)
-- `--dir`, `--skip-aliases`, `--skip-path`
-
-### In-session slash commands
-- **Conversation control:** `/resume` (`/switch`), `/rewind` (`/undo`),
-  `/rename <name>`, `/clear`, `/fork`, `/reset`, `/new`
-- **Settings & tools:** `/config`, `/settings`, `/permissions`, `/model`,
-  `/keybindings`, `/statusline`, `/tasks`, `/skills`, `/mcp`, `/open <path>`,
-  `/usage`, `/logout`, `/agents`
-- **Prompt helpers:** `@` path autocomplete, `esc esc` clears the prompt (when
-  not streaming), `!` runs a terminal command directly, `?` opens help
-
-## Settings and permissions
-
-### Common settings keys (`settings.json`)
-- `allowNonWorkspaceAccess`
-- `colorScheme`
-- `permissions.allow`
-- `trustedWorkspaces`
-
-### Permission modes
-`request-review`, `always-proceed`, `strict`, `proceed-in-sandbox`.
-
-### Sandbox behavior
-- `enableTerminalSandbox` is a boolean in `settings.json`; default `false`.
-- Launch-time overrides (`--sandbox`, `--dangerously-skip-permissions`) can
-  supersede persistent settings for the current session.
-
-## Authentication behavior
-
-- The CLI tries the OS secure keyring first.
-- With no saved session, it falls back to browser-based Google sign-in.
-- Locally it opens the default browser; over SSH it prints an authorization URL
-  and expects the auth code pasted back.
-- `/logout` removes saved credentials.
-
-## Plugins
-
-- Plugins stage under `~/.gemini/antigravity-cli/plugins/<plugin_name>/`.
-- They can bundle skills, agents, rules, MCP servers, and hooks.
-- `agy plugin list` returning no imported plugins is a valid empty state.
-
-## Pitfalls
-
-- `agy help` shows wrapper commands, not interactive slash commands.
-- `agy --version` is the safe non-interactive version check; `agy version` is
-  interactive and can fail without a real TTY.
-- First place to look for failures: `~/.gemini/antigravity-cli/log/cli-*.log`
-  (read with `read_file`).
-- Don't confuse persistent JSON settings with launch-time overrides.
-- `~/.gemini/antigravity-cli/bin/agentapi` is a thin wrapper to `agy agentapi`.
-- On WSL, token storage is file-based, so auth issues are usually local-file /
-  session-state problems, not browser-only problems.
-- Workspace identity can depend on launch directory and the `.antigravitycli`
-  project marker.
-- `agy -p` prints plain text only — no `--output-format json`, no result
-  envelope. Don't try to parse a JSON object out of it (unlike `claude-code`).
-- Bound print runs with `--print-timeout` (default `5m`), not `--max-turns`
-  (which does not exist on `agy`).
-
-## Verification
-
-Confirm the install is real and usable, all through the `terminal` tool (read
-files with `read_file`):
-
-1. `terminal(command="command -v agy")`
-2. `terminal(command="agy --version")`
-3. `terminal(command="agy help")`
-4. `terminal(command="agy plugin list")`
-5. `read_file` on `~/.gemini/antigravity-cli/settings.json`
-6. `read_file` on the latest `~/.gemini/antigravity-cli/log/cli-*.log`
-7. If needed, `read_file` on `~/.gemini/antigravity-cli/keybindings.json`
-
-## Support files
-
-- `references/cli-docs.md` — condensed notes from the getting-started, usage,
-  and features docs.

package/docs/80_upstream-docs-and-skills/hermes-dev-skill/src/docs/user-guide/skills/optional/autonomous-ai-agents/autonomous-ai-agents-blackbox.md

@@ -1,161 +0,0 @@
----
-title: "Blackbox — Delegate coding tasks to the Blackbox AI multi-model CLI"
-sidebar_label: "Blackbox"
-description: "Delegate coding tasks to the Blackbox AI multi-model CLI"
----
-
-{/* This page is auto-generated from the skill's SKILL.md by website/scripts/generate-skill-docs.py. Edit the source SKILL.md, not this page. */}
-
-# Blackbox
-
-Delegate coding tasks to the Blackbox AI multi-model CLI.
-
-## Skill metadata
-
-| | |
-|---|---|
-| Source | Optional — install with `hermes skills install official/autonomous-ai-agents/blackbox` |
-| Path | `optional-skills/autonomous-ai-agents\blackbox` |
-| Version | `1.0.1` |
-| Author | Hermes Agent (Nous Research) |
-| License | MIT |
-| Platforms | linux, macos, windows |
-| Tags | `Coding-Agent`, `Blackbox`, `Multi-Agent`, `Judge`, `Multi-Model` |
-| Related skills | [`claude-code`](/docs/user-guide/skills/bundled/autonomous-ai-agents/autonomous-ai-agents-claude-code), [`codex`](/docs/user-guide/skills/bundled/autonomous-ai-agents/autonomous-ai-agents-codex), [`hermes-agent`](/docs/user-guide/skills/bundled/autonomous-ai-agents/autonomous-ai-agents-hermes-agent) |
-
-## Reference: full SKILL.md
-
-:::info
-The following is the complete skill definition that Hermes loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.
-:::
-
-# Blackbox CLI
-
-Delegate coding tasks to [Blackbox AI](https://www.blackbox.ai/) via the Hermes terminal. Blackbox is a multi-model coding agent CLI that dispatches tasks to multiple LLMs (Claude, Codex, Gemini, Blackbox Pro) and uses a judge to select the best implementation.
-
-The CLI (npm `@blackbox_ai/blackbox-cli`, binary `blackbox`) is a TypeScript coding agent (forked from Gemini CLI) and supports interactive sessions, non-interactive one-shots, checkpointing, MCP, and vision model switching.
-
-## Prerequisites
-
-- Node.js 20+ installed
-- Blackbox CLI installed: `npm install -g @blackbox_ai/blackbox-cli` (binary: `blackbox`)
-- API key from [app.blackbox.ai/dashboard](https://app.blackbox.ai/dashboard)
-- Configured: run `blackbox configure` and enter your API key
-- Use `pty=true` in terminal calls — Blackbox CLI is an interactive terminal app
-
-## One-Shot Tasks
-
-```
-terminal(command="blackbox --prompt 'Add JWT authentication with refresh tokens to the Express API'", workdir="/path/to/project", pty=true)
-```
-
-For quick scratch work:
-```
-terminal(command="cd $(mktemp -d) && git init && blackbox --prompt 'Build a REST API for todos with SQLite'", pty=true)
-```
-
-## Background Mode (Long Tasks)
-
-For tasks that take minutes, use background mode so you can monitor progress:
-
-```
-# Start in background with PTY
-terminal(command="blackbox --prompt 'Refactor the auth module to use OAuth 2.0'", workdir="~/project", background=true, pty=true)
-# Returns session_id
-
-# Monitor progress
-process(action="poll", session_id="<id>")
-process(action="log", session_id="<id>")
-
-# Send input if Blackbox asks a question
-process(action="submit", session_id="<id>", data="yes")
-
-# Kill if needed
-process(action="kill", session_id="<id>")
-```
-
-## Checkpoints & Resume
-
-Blackbox CLI has built-in checkpoint support for pausing and resuming tasks:
-
-```
-# After a task completes, Blackbox shows a checkpoint tag
-# Resume with a follow-up task:
-terminal(command="blackbox --resume-checkpoint 'task-abc123-2026-03-06' --prompt 'Now add rate limiting to the endpoints'", workdir="~/project", pty=true)
-```
-
-## Session Commands
-
-During an interactive session, use these commands:
-
-| Command | Effect |
-|---------|--------|
-| `/compress` | Shrink conversation history to save tokens |
-| `/clear` | Wipe history and start fresh |
-| `/stats` | View current token usage |
-| `Ctrl+C` | Cancel current operation |
-
-## PR Reviews
-
-Clone to a temp directory to avoid modifying the working tree:
-
-```
-terminal(command="REVIEW=$(mktemp -d) && git clone https://github.com/user/repo.git $REVIEW && cd $REVIEW && gh pr checkout 42 && blackbox --prompt 'Review this PR against main. Check for bugs, security issues, and code quality.'", pty=true)
-```
-
-## Parallel Work
-
-Spawn multiple Blackbox instances for independent tasks:
-
-```
-terminal(command="blackbox --prompt 'Fix the login bug'", workdir="/tmp/issue-1", background=true, pty=true)
-terminal(command="blackbox --prompt 'Add unit tests for auth'", workdir="/tmp/issue-2", background=true, pty=true)
-
-# Monitor all
-process(action="list")
-```
-
-## Multi-Model Mode
-
-Blackbox's unique feature is running the same task through multiple models and judging the results. Configure which models to use via `blackbox configure` — select multiple providers to enable the Chairman/judge workflow where the CLI evaluates outputs from different models and picks the best one.
-
-## Key Flags
-
-| Flag | Effect |
-|------|--------|
-| `--prompt "task"` (`-p`) | Non-interactive one-shot execution |
-| `--resume-checkpoint "tag"` | Resume from a saved checkpoint |
-| `--yolo` (`-y`) | Auto-approve all actions and model switches |
-| `--vlm-switch-mode <mode>` | Image-handling: `once`, `session`, or `persist` |
-| `-c, --checkpointing` | Enable checkpointing of file edits |
-| `blackbox configure` | Change settings, providers, models |
-| `blackbox update` | Update the CLI to the latest version |
-| `blackbox mcp` | Manage MCP servers |
-| `blackbox extensions` | Manage CLI extensions |
-| `blackbox voice <action>` / `blackbox shortcut` | Configure voice input / the `b` shortcut |
-
-## Vision Support
-
-Blackbox automatically detects images in input and can switch to multimodal analysis. VLM modes:
-- `"once"` — Switch model for current query only
-- `"session"` — Switch for entire session
-- `"persist"` — Stay on current model (no switch)
-
-## Token Limits
-
-Control token usage via `.blackboxcli/settings.json`:
-```json
-{
-  "sessionTokenLimit": 32000
-}
-```
-
-## Rules
-
-1. **Always use `pty=true`** — Blackbox CLI is an interactive terminal app and will hang without a PTY
-2. **Use `workdir`** — keep the agent focused on the right directory
-3. **Background for long tasks** — use `background=true` and monitor with `process` tool
-4. **Don't interfere** — monitor with `poll`/`log`, don't kill sessions because they're slow
-5. **Report results** — after completion, check what changed and summarize for the user
-6. **Credits cost money** — Blackbox uses a credit-based system; multi-model mode consumes credits faster
-7. **Check prerequisites** — verify `blackbox` CLI is installed before attempting delegation