@symerian/symi 3.0.20 → 3.0.22

package/docs/start/wizard-cli-automation.md

@@ -1,158 +0,0 @@
----
-summary: "Scripted onboarding and agent setup for the Symi CLI"
-read_when:
-  - You are automating onboarding in scripts or CI
-  - You need non-interactive examples for specific providers
-title: "CLI Automation"
-sidebarTitle: "CLI automation"
----
-
-# CLI Automation
-
-Use `--non-interactive` to automate `symi onboard`.
-
-<Note>
-`--json` does not imply non-interactive mode. Use `--non-interactive` (and `--workspace`) for scripts.
-</Note>
-
-## Baseline non-interactive example
-
-```bash
-symi onboard --non-interactive \
-  --mode local \
-  --auth-choice apiKey \
-  --anthropic-api-key "$ANTHROPIC_API_KEY" \
-  --gateway-port 18789 \
-  --gateway-bind loopback \
-  --install-daemon \
-  --daemon-runtime node \
-  --skip-skills
-```
-
-Add `--json` for a machine-readable summary.
-
-## Provider-specific examples
-
-<AccordionGroup>
-  <Accordion title="Gemini example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice gemini-api-key \
-      --gemini-api-key "$GEMINI_API_KEY" \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-  </Accordion>
-  <Accordion title="Z.AI example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice zai-api-key \
-      --zai-api-key "$ZAI_API_KEY" \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-  </Accordion>
-  <Accordion title="Vercel AI Gateway example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice ai-gateway-api-key \
-      --ai-gateway-api-key "$AI_GATEWAY_API_KEY" \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-  </Accordion>
-  <Accordion title="Cloudflare AI Gateway example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice cloudflare-ai-gateway-api-key \
-      --cloudflare-ai-gateway-account-id "your-account-id" \
-      --cloudflare-ai-gateway-gateway-id "your-gateway-id" \
-      --cloudflare-ai-gateway-api-key "$CLOUDFLARE_AI_GATEWAY_API_KEY" \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-  </Accordion>
-  <Accordion title="Moonshot example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice moonshot-api-key \
-      --moonshot-api-key "$MOONSHOT_API_KEY" \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-  </Accordion>
-  <Accordion title="Synthetic example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice synthetic-api-key \
-      --synthetic-api-key "$SYNTHETIC_API_KEY" \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-  </Accordion>
-  <Accordion title="OpenCode Zen example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice opencode-zen \
-      --opencode-zen-api-key "$OPENCODE_API_KEY" \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-  </Accordion>
-  <Accordion title="Custom provider example">
-    ```bash
-    symi onboard --non-interactive \
-      --mode local \
-      --auth-choice custom-api-key \
-      --custom-base-url "https://llm.example.com/v1" \
-      --custom-model-id "foo-large" \
-      --custom-api-key "$CUSTOM_API_KEY" \
-      --custom-provider-id "my-custom" \
-      --custom-compatibility anthropic \
-      --gateway-port 18789 \
-      --gateway-bind loopback
-    ```
-
-    `--custom-api-key` is optional. If omitted, onboarding checks `CUSTOM_API_KEY`.
-
-  </Accordion>
-</AccordionGroup>
-
-## Add another agent
-
-Use `symi agents add <name>` to create a separate agent with its own workspace,
-sessions, and auth profiles. Running without `--workspace` launches the wizard.
-
-```bash
-symi agents add work \
-  --workspace ~/.symi/workspace-work \
-  --model openai/gpt-5.2 \
-  --bind whatsapp:biz \
-  --non-interactive \
-  --json
-```
-
-What it sets:
-
-- `agents.list[].name`
-- `agents.list[].workspace`
-- `agents.list[].agentDir`
-
-Notes:
-
-- Default workspaces follow `~/.symi/workspace-<agentId>`.
-- Add `bindings` to route inbound messages (the wizard can do this).
-- Non-interactive flags: `--model`, `--agent-dir`, `--bind`, `--non-interactive`.
-
-## Related docs
-
-- Onboarding hub: [Onboarding Wizard (CLI)](/start/wizard)
-- Full reference: [CLI Onboarding Reference](/start/wizard-cli-reference)
-- Command reference: [`symi onboard`](/cli/onboard)

package/docs/start/wizard-cli-reference.md

@@ -1,255 +0,0 @@
----
-summary: "Complete reference for CLI onboarding flow, auth/model setup, outputs, and internals"
-read_when:
-  - You need detailed behavior for symi onboard
-  - You are debugging onboarding results or integrating onboarding clients
-title: "CLI Onboarding Reference"
-sidebarTitle: "CLI reference"
----
-
-# CLI Onboarding Reference
-
-This page is the full reference for `symi onboard`.
-For the short guide, see [Onboarding Wizard (CLI)](/start/wizard).
-
-## What the wizard does
-
-Local mode (default) walks you through:
-
-- Model and auth setup (OpenAI Code subscription OAuth, Anthropic API key or setup token, plus MiniMax, GLM, Moonshot, and AI Gateway options)
-- Workspace location and bootstrap files
-- Gateway settings (port, bind, auth, tailscale)
-- Daemon install (LaunchAgent or systemd user unit)
-- Health check
-- Skills setup
-
-Remote mode configures this machine to connect to a gateway elsewhere.
-It does not install or modify anything on the remote host.
-
-## Local flow details
-
-<Steps>
-  <Step title="Existing config detection">
-    - If `~/.symi/symi.json` exists, choose Keep, Modify, or Reset.
-    - Re-running the wizard does not wipe anything unless you explicitly choose Reset (or pass `--reset`).
-    - If config is invalid or contains legacy keys, the wizard stops and asks you to run `symi doctor` before continuing.
-    - Reset uses `trash` and offers scopes:
-      - Config only
-      - Config + credentials + sessions
-      - Full reset (also removes workspace)
-  </Step>
-  <Step title="Model and auth">
-    - Full option matrix is in [Auth and model options](#auth-and-model-options).
-  </Step>
-  <Step title="Workspace">
-    - Default `~/.symi/workspace` (configurable).
-    - Seeds workspace files needed for first-run bootstrap ritual.
-    - Workspace layout: [Agent workspace](/concepts/agent-workspace).
-  </Step>
-  <Step title="Gateway">
-    - Prompts for port, bind, auth mode, and tailscale exposure.
-    - Recommended: keep token auth enabled even for loopback so local WS clients must authenticate.
-    - Disable auth only if you fully trust every local process.
-    - Non-loopback binds still require auth.
-  </Step>
-  <Step title="Channels">
-    - [WhatsApp](/channels/whatsapp): optional QR login
-    - [Telegram](/channels/telegram): bot token
-    - [Google Chat](/channels/googlechat): service account JSON + webhook audience
-    - [Mattermost](/channels/mattermost) plugin: bot token + base URL
-    - [Signal](/channels/signal): optional `signal-cli` install + account config
-    - [BlueBubbles](/channels/bluebubbles): recommended for iMessage; server URL + password + webhook
-    - [iMessage](/channels/imessage): legacy `imsg` CLI path + DB access
-    - DM security: default is pairing. First DM sends a code; approve via
-      `symi pairing approve <channel> <code>` or use allowlists.
-  </Step>
-  <Step title="Daemon install">
-    - macOS: LaunchAgent
-      - Requires logged-in user session; for headless, use a custom LaunchDaemon (not shipped).
-    - Linux and Windows via WSL2: systemd user unit
-      - Wizard attempts `loginctl enable-linger <user>` so gateway stays up after logout.
-      - May prompt for sudo (writes `/var/lib/systemd/linger`); it tries without sudo first.
-    - Runtime selection: Node (recommended; required for WhatsApp and Telegram). Bun is not recommended.
-  </Step>
-  <Step title="Health check">
-    - Starts gateway (if needed) and runs `symi health`.
-    - `symi status --deep` adds gateway health probes to status output.
-  </Step>
-  <Step title="Skills">
-    - Reads available skills and checks requirements.
-    - Lets you choose node manager: npm or pnpm (bun not recommended).
-    - Installs optional dependencies (some use Homebrew on macOS).
-  </Step>
-  <Step title="Finish">
-    - Summary and next steps, including iOS, Android, and macOS app options.
-  </Step>
-</Steps>
-
-<Note>
-If no GUI is detected, the wizard prints SSH port-forward instructions for the Control UI instead of opening a browser.
-If Control UI assets are missing, the wizard attempts to build them; fallback is `pnpm ui:build` (auto-installs UI deps).
-</Note>
-
-## Remote mode details
-
-Remote mode configures this machine to connect to a gateway elsewhere.
-
-<Info>
-Remote mode does not install or modify anything on the remote host.
-</Info>
-
-What you set:
-
-- Remote gateway URL (`ws://...`)
-- Token if remote gateway auth is required (recommended)
-
-<Note>
-- If gateway is loopback-only, use SSH tunneling or a tailnet.
-- Discovery hints:
-  - macOS: Bonjour (`dns-sd`)
-  - Linux: Avahi (`avahi-browse`)
-</Note>
-
-## Auth and model options
-
-<AccordionGroup>
-  <Accordion title="Anthropic API key (recommended)">
-    Uses `ANTHROPIC_API_KEY` if present or prompts for a key, then saves it for daemon use.
-  </Accordion>
-  <Accordion title="Anthropic OAuth (Claude Code CLI)">
-    - macOS: checks Keychain item "Claude Code-credentials"
-    - Linux and Windows: reuses `~/.claude/.credentials.json` if present
-
-    On macOS, choose "Always Allow" so launchd starts do not block.
-
-  </Accordion>
-  <Accordion title="Anthropic token (setup-token paste)">
-    Run `claude setup-token` on any machine, then paste the token.
-    You can name it; blank uses default.
-  </Accordion>
-  <Accordion title="OpenAI Code subscription (Codex CLI reuse)">
-    If `~/.codex/auth.json` exists, the wizard can reuse it.
-  </Accordion>
-  <Accordion title="OpenAI Code subscription (OAuth)">
-    Browser flow; paste `code#state`.
-
-    Sets `agents.defaults.model` to `openai-codex/gpt-5.3-codex` when model is unset or `openai/*`.
-
-  </Accordion>
-  <Accordion title="OpenAI API key">
-    Uses `OPENAI_API_KEY` if present or prompts for a key, then saves it to
-    `~/.symi/.env` so launchd can read it.
-
-    Sets `agents.defaults.model` to `openai/gpt-5.1-codex` when model is unset, `openai/*`, or `openai-codex/*`.
-
-  </Accordion>
-  <Accordion title="xAI (Grok) API key">
-    Prompts for `XAI_API_KEY` and configures xAI as a model provider.
-  </Accordion>
-  <Accordion title="OpenCode Zen">
-    Prompts for `OPENCODE_API_KEY` (or `OPENCODE_ZEN_API_KEY`).
-    Setup URL: [opencode.ai/auth](https://opencode.ai/auth).
-  </Accordion>
-  <Accordion title="API key (generic)">
-    Stores the key for you.
-  </Accordion>
-  <Accordion title="Vercel AI Gateway">
-    Prompts for `AI_GATEWAY_API_KEY`.
-    More detail: [Vercel AI Gateway](/providers/vercel-ai-gateway).
-  </Accordion>
-  <Accordion title="Cloudflare AI Gateway">
-    Prompts for account ID, gateway ID, and `CLOUDFLARE_AI_GATEWAY_API_KEY`.
-    More detail: [Cloudflare AI Gateway](/providers/cloudflare-ai-gateway).
-  </Accordion>
-  <Accordion title="MiniMax M2.1">
-    Config is auto-written.
-    More detail: [MiniMax](/providers/minimax).
-  </Accordion>
-  <Accordion title="Synthetic (Anthropic-compatible)">
-    Prompts for `SYNTHETIC_API_KEY`.
-    More detail: [Synthetic](/providers/synthetic).
-  </Accordion>
-  <Accordion title="Moonshot and Kimi Coding">
-    Moonshot (Kimi K2) and Kimi Coding configs are auto-written.
-    More detail: [Moonshot AI (Kimi + Kimi Coding)](/providers/moonshot).
-  </Accordion>
-  <Accordion title="Custom provider">
-    Works with OpenAI-compatible and Anthropic-compatible endpoints.
-
-    Non-interactive flags:
-    - `--auth-choice custom-api-key`
-    - `--custom-base-url`
-    - `--custom-model-id`
-    - `--custom-api-key` (optional; falls back to `CUSTOM_API_KEY`)
-    - `--custom-provider-id` (optional)
-    - `--custom-compatibility <openai|anthropic>` (optional; default `openai`)
-
-  </Accordion>
-  <Accordion title="Skip">
-    Leaves auth unconfigured.
-  </Accordion>
-</AccordionGroup>
-
-Model behavior:
-
-- Pick default model from detected options, or enter provider and model manually.
-- Wizard runs a model check and warns if the configured model is unknown or missing auth.
-
-Credential and profile paths:
-
-- OAuth credentials: `~/.symi/credentials/oauth.json`
-- Auth profiles (API keys + OAuth): `~/.symi/agents/<agentId>/agent/auth-profiles.json`
-
-<Note>
-Headless and server tip: complete OAuth on a machine with a browser, then copy
-`~/.symi/credentials/oauth.json` (or `$SYMI_STATE_DIR/credentials/oauth.json`)
-to the gateway host.
-</Note>
-
-## Outputs and internals
-
-Typical fields in `~/.symi/symi.json`:
-
-- `agents.defaults.workspace`
-- `agents.defaults.model` / `models.providers` (if Minimax chosen)
-- `gateway.*` (mode, bind, auth, tailscale)
-- `skills.install.nodeManager`
-- `wizard.lastRunAt`
-- `wizard.lastRunVersion`
-- `wizard.lastRunCommit`
-- `wizard.lastRunCommand`
-- `wizard.lastRunMode`
-
-`symi agents add` writes `agents.list[]` and optional `bindings`.
-
-WhatsApp credentials go under `~/.symi/credentials/whatsapp/<accountId>/`.
-Sessions are stored under `~/.symi/agents/<agentId>/sessions/`.
-
-<Note>
-Some channels are delivered as plugins. When selected during onboarding, the wizard
-prompts to install the plugin (npm or local path) before channel configuration.
-</Note>
-
-Gateway wizard RPC:
-
-- `wizard.start`
-- `wizard.next`
-- `wizard.cancel`
-- `wizard.status`
-
-Clients (macOS app and Control UI) can render steps without re-implementing onboarding logic.
-
-Signal setup behavior:
-
-- Downloads the appropriate release asset
-- Stores it under `~/.symi/tools/signal-cli/<version>/`
-- Writes `channels.signal.cliPath` in config
-- JVM builds require Java 21
-- Native builds are used when available
-- Windows uses WSL2 and follows Linux signal-cli flow inside WSL
-
-## Related docs
-
-- Onboarding hub: [Onboarding Wizard (CLI)](/start/wizard)
-- Automation and scripts: [CLI Automation](/start/wizard-cli-automation)
-- Command reference: [`symi onboard`](/cli/onboard)

package/docs/start/wizard.md

@@ -1,109 +0,0 @@
----
-summary: "CLI onboarding wizard: guided setup for gateway, workspace, channels, and skills"
-read_when:
-  - Running or configuring the onboarding wizard
-  - Setting up a new machine
-title: "Onboarding Wizard (CLI)"
-sidebarTitle: "Onboarding: CLI"
----
-
-# Onboarding Wizard (CLI)
-
-The onboarding wizard is the **recommended** way to set up Symi on macOS,
-Linux, or Windows (via WSL2; strongly recommended).
-It configures a local Gateway or a remote Gateway connection, plus channels, skills,
-and workspace defaults in one guided flow.
-
-```bash
-symi onboard
-```
-
-<Info>
-Fastest first chat: open the Control UI (no channel setup needed). Run
-`symi dashboard` and chat in the browser. Docs: [Dashboard](/web/dashboard).
-</Info>
-
-To reconfigure later:
-
-```bash
-symi configure
-symi agents add <name>
-```
-
-<Note>
-`--json` does not imply non-interactive mode. For scripts, use `--non-interactive`.
-</Note>
-
-<Tip>
-Recommended: set up a Brave Search API key so the agent can use `web_search`
-(`web_fetch` works without a key). Easiest path: `symi configure --section web`
-which stores `tools.web.search.apiKey`. Docs: [Web tools](/tools/web).
-</Tip>
-
-## QuickStart vs Advanced
-
-The wizard starts with **QuickStart** (defaults) vs **Advanced** (full control).
-
-<Tabs>
-  <Tab title="QuickStart (defaults)">
-    - Local gateway (loopback)
-    - Workspace default (or existing workspace)
-    - Gateway port **18789**
-    - Gateway auth **Token** (auto‑generated, even on loopback)
-    - Tailscale exposure **Off**
-    - Telegram + WhatsApp DMs default to **allowlist** (you'll be prompted for your phone number)
-  </Tab>
-  <Tab title="Advanced (full control)">
-    - Exposes every step (mode, workspace, gateway, channels, daemon, skills).
-  </Tab>
-</Tabs>
-
-## What the wizard configures
-
-**Local mode (default)** walks you through these steps:
-
-1. **Model/Auth** — Anthropic API key (recommended), OpenAI, or Custom Provider
-   (OpenAI-compatible, Anthropic-compatible, or Unknown auto-detect). Pick a default model.
-2. **Workspace** — Location for agent files (default `~/.symi/workspace`). Seeds bootstrap files.
-3. **Gateway** — Port, bind address, auth mode, Tailscale exposure.
-4. **Daemon** — Installs a LaunchAgent (macOS) or systemd user unit (Linux/WSL2).
-5. **Health check** — Starts the Gateway and verifies it's running.
-6. **Skills** — Installs recommended skills and optional dependencies.
-
-<Note>
-Re-running the wizard does **not** wipe anything unless you explicitly choose **Reset** (or pass `--reset`).
-If the config is invalid or contains legacy keys, the wizard asks you to run `symi doctor` first.
-</Note>
-
-**Remote mode** only configures the local client to connect to a Gateway elsewhere.
-It does **not** install or change anything on the remote host.
-
-## Add another agent
-
-Use `symi agents add <name>` to create a separate agent with its own workspace,
-sessions, and auth profiles. Running without `--workspace` launches the wizard.
-
-What it sets:
-
-- `agents.list[].name`
-- `agents.list[].workspace`
-- `agents.list[].agentDir`
-
-Notes:
-
-- Default workspaces follow `~/.symi/workspace-<agentId>`.
-- Add `bindings` to route inbound messages (the wizard can do this).
-- Non-interactive flags: `--model`, `--agent-dir`, `--bind`, `--non-interactive`.
-
-## Full reference
-
-For detailed step-by-step breakdowns, non-interactive scripting, Signal setup,
-RPC API, and a full list of config fields the wizard writes, see the
-[Wizard Reference](/reference/wizard).
-
-## Related docs
-
-- CLI command reference: [`symi onboard`](/cli/onboard)
-- Onboarding overview: [Onboarding Overview](/start/onboarding-overview)
-- macOS app onboarding: [Onboarding](/start/onboarding)
-- Agent first-run ritual: [Agent Bootstrapping](/start/bootstrapping)

package/docs/style.css

@@ -1,37 +0,0 @@
-#content > h1:first-of-type {
-  display: none !important;
-}
-
-.nav-tabs {
-  position: relative;
-}
-
-.nav-tabs-item > div {
-  opacity: 0;
-}
-
-.nav-tabs-underline {
-  position: absolute;
-  left: 0;
-  bottom: 0;
-  height: 1.5px;
-  width: var(--nav-tab-underline-width, 0);
-  transform: translateX(var(--nav-tab-underline-x, 0));
-  background-color: rgb(var(--primary));
-  border-radius: 999px;
-  pointer-events: none;
-  opacity: 0;
-  transition:
-    transform 260ms ease-in-out,
-    width 260ms ease-in-out,
-    opacity 160ms ease-in-out;
-  will-change: transform, width;
-}
-
-html.dark .nav-tabs-underline {
-  background-color: rgb(var(--primary-light));
-}
-
-.nav-tabs-underline-ready .nav-tabs-underline {
-  opacity: 1;
-}

package/docs/tools/agent-send.md

@@ -1,52 +0,0 @@
----
-summary: "Direct `symi agent` CLI runs (with optional delivery)"
-read_when:
-  - Adding or modifying the agent CLI entrypoint
-title: "Agent Send"
----
-
-# `symi agent` (direct agent runs)
-
-`symi agent` runs a single agent turn without needing an inbound chat message.
-By default it goes **through the Gateway**; add `--local` to force the embedded
-runtime on the current machine.
-
-## Behavior
-
-- Required: `--message <text>`
-- Session selection:
-  - `--to <dest>` derives the session key (group/channel targets preserve isolation; direct chats collapse to `main`), **or**
-  - `--session-id <id>` reuses an existing session by id, **or**
-  - `--agent <id>` targets a configured agent directly (uses that agent's `main` session key)
-- Runs the same embedded agent runtime as normal inbound replies.
-- Thinking/verbose flags persist into the session store.
-- Output:
-  - default: prints reply text (plus `MEDIA:<url>` lines)
-  - `--json`: prints structured payload + metadata
-- Optional delivery back to a channel with `--deliver` + `--channel` (target formats match `symi message --target`).
-- Use `--reply-channel`/`--reply-to`/`--reply-account` to override delivery without changing the session.
-
-If the Gateway is unreachable, the CLI **falls back** to the embedded local run.
-
-## Examples
-
-```bash
-symi agent --to +15555550123 --message "status update"
-symi agent --agent ops --message "Summarize logs"
-symi agent --session-id 1234 --message "Summarize inbox" --thinking medium
-symi agent --to +15555550123 --message "Trace logs" --verbose on --json
-symi agent --to +15555550123 --message "Summon reply" --deliver
-symi agent --agent ops --message "Generate report" --deliver --reply-channel slack --reply-to "#reports"
-```
-
-## Flags
-
-- `--local`: run locally (requires model provider API keys in your shell)
-- `--deliver`: send the reply to the chosen channel
-- `--reply-to`: delivery target override
-- `--reply-channel`: delivery channel override
-- `--reply-account`: delivery account id override
-- `--thinking <off|minimal|low|medium|high|xhigh>`: persist thinking level (GPT-5.2 + Codex models only)
-- `--verbose <on|full|off>`: persist verbose level
-- `--timeout <seconds>`: override agent timeout
-- `--json`: output structured JSON

package/docs/tools/apply-patch.md

@@ -1,51 +0,0 @@
----
-summary: "Apply multi-file patches with the apply_patch tool"
-read_when:
-  - You need structured file edits across multiple files
-  - You want to document or debug patch-based edits
-title: "apply_patch Tool"
----
-
-# apply_patch tool
-
-Apply file changes using a structured patch format. This is ideal for multi-file
-or multi-hunk edits where a single `edit` call would be brittle.
-
-The tool accepts a single `input` string that wraps one or more file operations:
-
-```
-*** Begin Patch
-*** Add File: path/to/file.txt
-+line 1
-+line 2
-*** Update File: src/app.ts
-@@
--old line
-+new line
-*** Delete File: obsolete.txt
-*** End Patch
-```
-
-## Parameters
-
-- `input` (required): Full patch contents including `*** Begin Patch` and `*** End Patch`.
-
-## Notes
-
-- Patch paths support relative paths (from the workspace directory) and absolute paths.
-- `tools.exec.applyPatch.workspaceOnly` defaults to `true` (workspace-contained). Set it to `false` only if you intentionally want `apply_patch` to write/delete outside the workspace directory.
-- Use `*** Move to:` within an `*** Update File:` hunk to rename files.
-- `*** End of File` marks an EOF-only insert when needed.
-- Experimental and disabled by default. Enable with `tools.exec.applyPatch.enabled`.
-- OpenAI-only (including OpenAI Codex). Optionally gate by model via
-  `tools.exec.applyPatch.allowModels`.
-- Config is only under `tools.exec`.
-
-## Example
-
-```json
-{
-  "tool": "apply_patch",
-  "input": "*** Begin Patch\n*** Update File: src/index.ts\n@@\n-const foo = 1\n+const foo = 2\n*** End Patch"
-}
-```