@openparachute/agent 0.1.2 → 0.2.2

package/.claude/skills/add-wechat/scripts/wire-dm.ts

@@ -1,172 +0,0 @@
-#!/usr/bin/env pnpm exec tsx
-/**
- * Wire a WeChat DM (or group) to an agent group.
- *
- * After /add-wechat installs the adapter and the user scans the QR login,
- * the first inbound message from another WeChat account auto-creates a
- * `messaging_groups` row. This script finds that row, asks the operator
- * which agent group to wire it to, and inserts the `messaging_group_agents`
- * join row with sensible defaults — the "post-login wiring" step /add-wechat
- * otherwise requires manual SQL for.
- *
- * Usage:
- *   pnpm exec tsx .claude/skills/add-wechat/scripts/wire-dm.ts
- *
- * Flags:
- *   --platform-id <id>      Wire a specific messaging group (default: most recent unwired)
- *   --agent-group <id>      Target agent group (default: interactive pick; or solo admin group)
- *   --sender-policy <p>     public | strict (default: public)
- *   --session-mode <m>      shared | per-thread (default: shared)
- *   --non-interactive       Fail instead of prompting
- */
-import Database from 'better-sqlite3';
-import path from 'node:path';
-import readline from 'node:readline';
-
-const DB_PATH = process.env.NANOCLAW_DB_PATH ?? path.join(process.cwd(), 'data', 'v2.db');
-
-type SenderPolicy = 'public' | 'strict' | 'request_approval';
-
-interface Args {
-  platformId?: string;
-  agentGroupId?: string;
-  senderPolicy: SenderPolicy;
-  sessionMode: 'shared' | 'per-thread';
-  interactive: boolean;
-}
-
-function parseArgs(argv: string[]): Args {
-  const args: Args = {
-    // Default matches the router's auto-create (`request_approval`) so the
-    // admin gets an approval card on the next unknown-sender DM rather than
-    // a silent allow. Pass `--sender-policy public` to open the channel to
-    // anyone, or `strict` to require explicit membership.
-    senderPolicy: 'request_approval',
-    sessionMode: 'shared',
-    interactive: true,
-  };
-  for (let i = 0; i < argv.length; i++) {
-    const flag = argv[i];
-    const val = argv[i + 1];
-    switch (flag) {
-      case '--platform-id': args.platformId = val; i++; break;
-      case '--agent-group': args.agentGroupId = val; i++; break;
-      case '--sender-policy':
-        if (val !== 'public' && val !== 'strict' && val !== 'request_approval') {
-          throw new Error(`bad --sender-policy: ${val} (use public | strict | request_approval)`);
-        }
-        args.senderPolicy = val; i++; break;
-      case '--session-mode':
-        if (val !== 'shared' && val !== 'per-thread') throw new Error(`bad --session-mode: ${val}`);
-        args.sessionMode = val; i++; break;
-      case '--non-interactive': args.interactive = false; break;
-      case '--help': case '-h':
-        console.log('See .claude/skills/add-wechat/scripts/wire-dm.ts header for usage.');
-        process.exit(0);
-    }
-  }
-  return args;
-}
-
-async function prompt(q: string): Promise<string> {
-  const rl = readline.createInterface({ input: process.stdin, output: process.stdout });
-  return new Promise((resolve) => rl.question(q, (a) => { rl.close(); resolve(a.trim()); }));
-}
-
-function generateId(prefix: string): string {
-  return `${prefix}-${Date.now()}-${Math.random().toString(36).slice(2, 8)}`;
-}
-
-async function main(): Promise<void> {
-  const args = parseArgs(process.argv.slice(2));
-  const db = new Database(DB_PATH);
-  db.pragma('journal_mode = WAL');
-
-  // 1. Pick the messaging group
-  let platformId = args.platformId;
-  if (!platformId) {
-    const rows = db.prepare(`
-      SELECT mg.id, mg.platform_id, mg.name, mg.is_group, mg.created_at
-      FROM messaging_groups mg
-      LEFT JOIN messaging_group_agents mga ON mga.messaging_group_id = mg.id
-      WHERE mg.channel_type = 'wechat' AND mga.id IS NULL
-      ORDER BY mg.created_at DESC
-    `).all() as Array<{ id: string; platform_id: string; name: string | null; is_group: number; created_at: string }>;
-
-    if (rows.length === 0) {
-      console.error('No unwired WeChat messaging groups found.');
-      console.error('Send a message to the bot first (from another WeChat account), then re-run.');
-      process.exit(1);
-    }
-
-    if (rows.length === 1 || !args.interactive) {
-      platformId = rows[0].platform_id;
-      console.log(`Using most recent unwired group: ${platformId} (${rows[0].is_group ? 'group' : 'DM'})`);
-    } else {
-      console.log('Unwired WeChat messaging groups:');
-      rows.forEach((r, i) => {
-        console.log(`  ${i + 1}. ${r.platform_id}  (${r.is_group ? 'group' : 'DM'}, ${r.created_at})`);
-      });
-      const pick = await prompt('Pick one [1]: ');
-      const idx = pick === '' ? 0 : parseInt(pick, 10) - 1;
-      if (Number.isNaN(idx) || idx < 0 || idx >= rows.length) throw new Error('invalid choice');
-      platformId = rows[idx].platform_id;
-    }
-  }
-
-  const mg = db.prepare(
-    'SELECT id, platform_id, is_group FROM messaging_groups WHERE channel_type = ? AND platform_id = ?'
-  ).get('wechat', platformId) as { id: string; platform_id: string; is_group: number } | undefined;
-  if (!mg) throw new Error(`no wechat messaging_group with platform_id = ${platformId}`);
-
-  // 2. Pick the agent group
-  let agentGroupId = args.agentGroupId;
-  if (!agentGroupId) {
-    const agents = db.prepare('SELECT id, name, is_admin FROM agent_groups ORDER BY is_admin DESC, created_at ASC')
-      .all() as Array<{ id: string; name: string; is_admin: number }>;
-    if (agents.length === 0) throw new Error('no agent groups exist — create one first');
-
-    const adminAgents = agents.filter((a) => a.is_admin === 1);
-    if (adminAgents.length === 1 && !args.interactive) {
-      agentGroupId = adminAgents[0].id;
-      console.log(`Auto-selected sole admin agent group: ${adminAgents[0].name} (${agentGroupId})`);
-    } else if (args.interactive) {
-      console.log('Agent groups:');
-      agents.forEach((a, i) => {
-        console.log(`  ${i + 1}. ${a.name} (${a.id})${a.is_admin ? ' [admin]' : ''}`);
-      });
-      const pick = await prompt('Pick one [1]: ');
-      const idx = pick === '' ? 0 : parseInt(pick, 10) - 1;
-      if (Number.isNaN(idx) || idx < 0 || idx >= agents.length) throw new Error('invalid choice');
-      agentGroupId = agents[idx].id;
-    } else {
-      throw new Error('multiple agent groups exist; pass --agent-group <id>');
-    }
-  }
-
-  const ag = db.prepare('SELECT id, name FROM agent_groups WHERE id = ?').get(agentGroupId) as
-    { id: string; name: string } | undefined;
-  if (!ag) throw new Error(`no agent_group with id = ${agentGroupId}`);
-
-  // 3. Update sender policy + wire
-  const tx = db.transaction(() => {
-    db.prepare('UPDATE messaging_groups SET unknown_sender_policy = ? WHERE id = ?')
-      .run(args.senderPolicy, mg.id);
-
-    db.prepare(`
-      INSERT INTO messaging_group_agents
-        (id, messaging_group_id, agent_group_id, trigger_rules, response_scope, session_mode, priority, created_at)
-      VALUES (?, ?, ?, '', 'all', ?, 10, datetime('now'))
-    `).run(generateId('mga'), mg.id, ag.id, args.sessionMode);
-  });
-  tx();
-
-  console.log('');
-  console.log(`WIRED platform_id=${mg.platform_id} agent_group=${ag.name} policy=${args.senderPolicy} mode=${args.sessionMode}`);
-  db.close();
-}
-
-main().catch((err) => {
-  console.error('FAILED:', err.message);
-  process.exit(1);
-});

package/.claude/skills/add-whatsapp/SKILL.md

@@ -1,264 +0,0 @@
----
-name: add-whatsapp
-description: Add WhatsApp channel via native Baileys adapter. Direct connection — no Chat SDK bridge. Uses QR code or pairing code for authentication.
----
-
-# Add WhatsApp Channel
-
-Adds WhatsApp support via the native Baileys adapter (no Chat SDK bridge).
-
-## Install
-
-NanoClaw doesn't ship channels in trunk. This skill copies the native WhatsApp (Baileys) adapter and its `whatsapp-auth` setup step in from the `channels` branch. No Chat SDK bridge.
-
-### Pre-flight (idempotent)
-
-Skip to **Credentials** if all of these are already in place:
-
-- `src/channels/whatsapp.ts` exists
-- `src/channels/index.ts` contains `import './whatsapp.js';`
-- `setup/whatsapp-auth.ts` and `setup/groups.ts` both exist
-- `setup/index.ts`'s `STEPS` map contains both `'whatsapp-auth':` and `groups:`
-- `@whiskeysockets/baileys`, `qrcode`, `pino` are listed in `package.json` dependencies
-
-Otherwise continue. Every step below is safe to re-run.
-
-### 1. Fetch the channels branch
-
-```bash
-git fetch origin channels
-```
-
-### 2. Copy the adapter and setup steps
-
-```bash
-git show origin/channels:src/channels/whatsapp.ts > src/channels/whatsapp.ts
-git show origin/channels:setup/whatsapp-auth.ts   > setup/whatsapp-auth.ts
-git show origin/channels:setup/groups.ts          > setup/groups.ts
-```
-
-### 3. Append the self-registration import
-
-Append to `src/channels/index.ts` (skip if already present):
-
-```typescript
-import './whatsapp.js';
-```
-
-### 4. Register the setup steps
-
-In `setup/index.ts`, add these entries to the `STEPS` map (skip lines already present):
-
-```typescript
-groups: () => import('./groups.js'),
-'whatsapp-auth': () => import('./whatsapp-auth.js'),
-```
-
-### 5. Install the adapter packages (pinned)
-
-```bash
-pnpm install @whiskeysockets/baileys@6.17.16 qrcode@1.5.4 @types/qrcode@1.5.6 pino@9.6.0
-```
-
-### 6. Build
-
-```bash
-pnpm run build
-```
-
-## Credentials
-
-WhatsApp uses linked-device authentication — no API key, just a one-time pairing from your phone.
-
-### Check current state
-
-Check if WhatsApp is already authenticated. If `store/auth/creds.json` exists, skip to "Shared vs dedicated number".
-
-```bash
-test -f store/auth/creds.json && echo "WhatsApp auth exists" || echo "No WhatsApp auth"
-```
-
-### Detect environment
-
-Check whether the environment is headless (no display server):
-
-```bash
-[[ -z "$DISPLAY" && -z "$WAYLAND_DISPLAY" && "$OSTYPE" != darwin* ]] && echo "IS_HEADLESS=true" || echo "IS_HEADLESS=false"
-```
-
-### Ask the user
-
-Use `AskUserQuestion` to collect configuration. **Adapt auth options based on environment:**
-
-If IS_HEADLESS=true AND not WSL → AskUserQuestion: How do you want to authenticate WhatsApp?
-- **Pairing code** (Recommended) - Enter a numeric code on your phone (no camera needed, requires phone number)
-- **QR code in terminal** - Displays QR code in the terminal (can be too small on some displays)
-
-Otherwise (macOS, desktop Linux, or WSL) → AskUserQuestion: How do you want to authenticate WhatsApp?
-- **QR code in browser** (Recommended) - Opens a browser window with a large, scannable QR code
-- **Pairing code** - Enter a numeric code on your phone (no camera needed, requires phone number)
-- **QR code in terminal** - Displays QR code in the terminal (can be too small on some displays)
-
-If they chose pairing code:
-
-AskUserQuestion: What is your phone number? (Digits only — country code followed by your 10-digit number, no + prefix, spaces, or dashes. Example: 14155551234 where 1 is the US country code and 4155551234 is the phone number.)
-
-### Clean previous auth state (if re-authenticating)
-
-```bash
-rm -rf store/auth/
-```
-
-### Run WhatsApp authentication
-
-For QR code in browser (recommended):
-
-```bash
-pnpm exec tsx setup/index.ts --step whatsapp-auth -- --method qr-browser
-```
-
-(Bash timeout: 150000ms)
-
-Tell the user:
-
-> A browser window will open with a QR code.
->
-> 1. Open WhatsApp > **Settings** > **Linked Devices** > **Link a Device**
-> 2. Scan the QR code in the browser
-> 3. The page will show "Authenticated!" when done
-
-For QR code in terminal:
-
-```bash
-pnpm exec tsx setup/index.ts --step whatsapp-auth -- --method qr-terminal
-```
-
-(Bash timeout: 150000ms)
-
-Tell the user:
-
-> 1. Open WhatsApp > **Settings** > **Linked Devices** > **Link a Device**
-> 2. Scan the QR code displayed in the terminal
-
-For pairing code:
-
-Tell the user to have WhatsApp open on **Settings > Linked Devices > Link a Device**, ready to tap **"Link with phone number instead"** — the code expires in ~60 seconds and must be entered immediately.
-
-Run the auth process in the background and poll `store/pairing-code.txt` for the code:
-
-```bash
-rm -f store/pairing-code.txt && pnpm exec tsx setup/index.ts --step whatsapp-auth -- --method pairing-code --phone <their-phone-number> > /tmp/wa-auth.log 2>&1 &
-```
-
-Then immediately poll for the code (do NOT wait for the background command to finish):
-
-```bash
-for i in $(seq 1 20); do [ -f store/pairing-code.txt ] && cat store/pairing-code.txt && break; sleep 1; done
-```
-
-Display the code to the user the moment it appears. Tell them:
-
-> **Enter this code now** — it expires in ~60 seconds.
->
-> 1. Open WhatsApp > **Settings** > **Linked Devices** > **Link a Device**
-> 2. Tap **Link with phone number instead**
-> 3. Enter the code immediately
-
-After the user enters the code, poll for authentication to complete:
-
-```bash
-for i in $(seq 1 60); do grep -q 'STATUS: authenticated' /tmp/wa-auth.log 2>/dev/null && echo "authenticated" && break; grep -q 'STATUS: failed' /tmp/wa-auth.log 2>/dev/null && echo "failed" && break; sleep 2; done
-```
-
-**If failed:** logged_out → delete `store/auth/` and re-run. timeout → ask user, offer retry.
-
-### Verify authentication succeeded
-
-```bash
-test -f store/auth/creds.json && echo "Authentication successful" || echo "Authentication failed"
-```
-
-### Shared vs dedicated number
-
-AskUserQuestion: Is this a shared phone number (personal WhatsApp) or a dedicated number?
-- **Shared number** — your personal WhatsApp (bot prefixes messages with its name)
-- **Dedicated number** — a separate phone/SIM for the assistant
-
-If dedicated, add to `.env`:
-
-```bash
-ASSISTANT_HAS_OWN_NUMBER=true
-```
-
-## Next Steps
-
-If you're in the middle of `/setup`, return to the setup flow now.
-
-Otherwise, run `/manage-channels` to wire this channel to an agent group.
-
-## Channel Info
-
-- **type**: `whatsapp`
-- **terminology**: WhatsApp calls them "groups" and "chats." A "chat" is a 1:1 DM; a "group" has multiple members.
-- **how-to-find-id**: DMs use `<phone>@s.whatsapp.net` (e.g. `14155551234@s.whatsapp.net`). Groups use `<id>@g.us`. To find your number: `node -e "const c=JSON.parse(require('fs').readFileSync('store/auth/creds.json','utf-8'));console.log(c.me?.id?.split(':')[0]+'@s.whatsapp.net')"`. Groups are auto-discovered — check `sqlite3 data/v2.db "SELECT platform_id, name FROM messaging_groups WHERE channel_type='whatsapp' AND is_group=1"`.
-- **supports-threads**: no
-- **typical-use**: Interactive chat — direct messages or small groups
-- **default-isolation**: Same agent group if you're the only participant across multiple chats. Separate agent group if different people are in different groups.
-
-### Features
-
-- Markdown formatting — `**bold**`→`*bold*`, `*italic*`→`_italic_`, headings→bold, code blocks preserved
-- Approval questions — `ask_user_question` renders with `/approve`, `/reject` slash commands
-- File attachments — send and receive images, video, audio, documents
-- Reactions — send emoji reactions on messages
-- Typing indicators — composing presence updates
-- Credential requests — text fallback (WhatsApp has no modal support)
-
-Not supported (WhatsApp linked device limitation): edit messages, delete messages.
-
-## Troubleshooting
-
-### QR code expired
-
-QR codes expire after ~60 seconds. Re-run the auth command:
-
-```bash
-rm -rf store/auth/ && pnpm exec tsx setup/index.ts --step whatsapp-auth -- --method qr-browser
-```
-
-### Pairing code not working
-
-Codes expire in ~60 seconds. Delete auth and retry:
-
-```bash
-rm -rf store/auth/ && pnpm exec tsx setup/index.ts --step whatsapp-auth -- --method pairing-code --phone <phone>
-```
-
-Ensure: digits only (no `+`), phone has internet, WhatsApp is updated.
-
-If pairing code keeps failing, switch to QR-browser auth instead:
-
-```bash
-rm -rf store/auth/ && pnpm exec tsx setup/index.ts --step whatsapp-auth -- --method qr-browser
-```
-
-### "waiting for this message" on reactions
-
-Signal sessions corrupted from rapid restarts. Clear sessions:
-
-```bash
-systemctl --user stop nanoclaw
-rm store/auth/session-*.json
-systemctl --user start nanoclaw
-```
-
-### Bot not responding
-
-1. Auth exists: `test -f store/auth/creds.json`
-2. Connected: `grep "Connected to WhatsApp" logs/nanoclaw.log | tail -1`
-3. Channel wired: `sqlite3 data/v2.db "SELECT mg.platform_id, mg.name FROM messaging_groups mg JOIN messaging_group_agents mga ON mg.id=mga.messaging_group_id WHERE mg.channel_type='whatsapp'"`
-4. Service running: `systemctl --user status nanoclaw`
-
-### "conflict" disconnection
-
-Two instances connected with same credentials. Ensure only one NanoClaw process is running.

package/.claude/skills/add-whatsapp-cloud/REMOVE.md

@@ -1,6 +0,0 @@
-# Remove WhatsApp Cloud API Channel
-
-1. Comment out `import './whatsapp-cloud.js'` in `src/channels/index.ts`
-2. Remove `WHATSAPP_ACCESS_TOKEN`, `WHATSAPP_PHONE_NUMBER_ID`, `WHATSAPP_APP_SECRET`, `WHATSAPP_VERIFY_TOKEN` from `.env`
-3. `pnpm uninstall @chat-adapter/whatsapp`
-4. Rebuild and restart

package/.claude/skills/add-whatsapp-cloud/SKILL.md

@@ -1,95 +0,0 @@
----
-name: add-whatsapp-cloud
-description: Add WhatsApp Business Cloud API channel via Chat SDK. Official Meta API.
----
-
-# Add WhatsApp Cloud API Channel
-
-Connect NanoClaw to WhatsApp via the official Meta WhatsApp Business Cloud API.
-
-## Install
-
-NanoClaw doesn't ship channels in trunk. This skill copies the WhatsApp Cloud adapter in from the `channels` branch.
-
-### Pre-flight (idempotent)
-
-Skip to **Credentials** if all of these are already in place:
-
-- `src/channels/whatsapp-cloud.ts` exists
-- `src/channels/index.ts` contains `import './whatsapp-cloud.js';`
-- `@chat-adapter/whatsapp` is listed in `package.json` dependencies
-
-Otherwise continue. Every step below is safe to re-run.
-
-### 1. Fetch the channels branch
-
-```bash
-git fetch origin channels
-```
-
-### 2. Copy the adapter
-
-```bash
-git show origin/channels:src/channels/whatsapp-cloud.ts > src/channels/whatsapp-cloud.ts
-```
-
-### 3. Append the self-registration import
-
-Append to `src/channels/index.ts` (skip if the line is already present):
-
-```typescript
-import './whatsapp-cloud.js';
-```
-
-### 4. Install the adapter package (pinned)
-
-```bash
-pnpm install @chat-adapter/whatsapp@4.26.0
-```
-
-### 5. Build
-
-```bash
-pnpm run build
-```
-
-## Credentials
-
-1. Go to [Meta for Developers](https://developers.facebook.com/apps/) and create an app (type: Business).
-2. Add the **WhatsApp** product.
-3. Go to **WhatsApp** > **API Setup**:
-   - Note the **Phone Number ID** (not the phone number itself).
-   - Generate a **permanent System User access token** with `whatsapp_business_messaging` permission.
-4. Go to **WhatsApp** > **Configuration**:
-   - Set webhook URL: `https://your-domain/webhook/whatsapp`.
-   - Set a **Verify Token** (any random string you choose).
-   - Subscribe to webhook fields: `messages`.
-5. Copy the **App Secret** from **Settings** > **Basic**.
-
-### Configure environment
-
-Add to `.env`:
-
-```bash
-WHATSAPP_ACCESS_TOKEN=your-system-user-access-token
-WHATSAPP_PHONE_NUMBER_ID=your-phone-number-id
-WHATSAPP_APP_SECRET=your-app-secret
-WHATSAPP_VERIFY_TOKEN=your-verify-token
-```
-
-Sync to container: `mkdir -p data/env && cp .env data/env/env`
-
-## Next Steps
-
-If you're in the middle of `/setup`, return to the setup flow now.
-
-Otherwise, run `/manage-channels` to wire this channel to an agent group.
-
-## Channel Info
-
-- **type**: `whatsapp-cloud`
-- **terminology**: WhatsApp Cloud API supports 1:1 conversations only (no group chats). Each conversation is with a phone number.
-- **how-to-find-id**: The platform ID is the Phone Number ID from the Meta Business dashboard (not the phone number itself). Find it under WhatsApp > API Setup.
-- **supports-threads**: no
-- **typical-use**: Interactive 1:1 chat -- direct messages only
-- **default-isolation**: Same agent group if you're the only person messaging the bot. Each additional person who messages gets their own conversation automatically, but they share the agent's workspace and memory -- use a separate agent group if you need information isolation between different contacts.

package/.claude/skills/add-whatsapp-cloud/VERIFY.md

@@ -1,3 +0,0 @@
-# Verify WhatsApp Cloud API Channel
-
-Send a message to your WhatsApp Business number. The bot should respond within a few seconds. Note: WhatsApp Cloud API only supports 1:1 DMs, not group chats.

package/.claude/skills/claw/SKILL.md

@@ -1,131 +0,0 @@
----
-name: claw
-description: Install the claw CLI tool — run NanoClaw agent containers from the command line without opening a chat app.
----
-
-# claw — NanoClaw CLI
-
-`claw` is a Python CLI that sends prompts directly to a NanoClaw agent container from the terminal. It reads registered groups from the NanoClaw database, picks up secrets from `.env`, and pipes a JSON payload into a container run — no chat app required.
-
-## What it does
-
-- Send a prompt to any registered group by name, folder, or JID
-- Default target is the main group (no `-g` needed for most use)
-- Resume a previous session with `-s <session-id>`
-- Read prompts from stdin (`--pipe`) for scripting and piping
-- List all registered groups with `--list-groups`
-- Auto-detects `container` or `docker` runtime (or override with `--runtime`)
-- Prints the agent's response to stdout; session ID to stderr
-- Verbose mode (`-v`) shows the command, redacted payload, and exit code
-
-## Prerequisites
-
-- Python 3.8 or later
-- NanoClaw installed with a built and tagged container image (`nanoclaw-agent:latest`)
-- Either `container` (Apple Container, macOS 15+) or `docker` available in `PATH`
-
-## Install
-
-Run this skill from within the NanoClaw directory. The script auto-detects its location, so the symlink always points to the right place.
-
-### 1. Copy the script
-
-```bash
-mkdir -p scripts
-cp "${CLAUDE_SKILL_DIR}/scripts/claw" scripts/claw
-chmod +x scripts/claw
-```
-
-### 2. Symlink into PATH
-
-```bash
-mkdir -p ~/bin
-ln -sf "$(pwd)/scripts/claw" ~/bin/claw
-```
-
-Make sure `~/bin` is in `PATH`. Add this to `~/.zshrc` or `~/.bashrc` if needed:
-
-```bash
-export PATH="$HOME/bin:$PATH"
-```
-
-Then reload the shell:
-
-```bash
-source ~/.zshrc   # or ~/.bashrc
-```
-
-### 3. Verify
-
-```bash
-claw --list-groups
-```
-
-You should see registered groups. If NanoClaw isn't running or the database doesn't exist yet, the list will be empty — that's fine.
-
-## Usage Examples
-
-```bash
-# Send a prompt to the main group
-claw "What's on my calendar today?"
-
-# Send to a specific group by name (fuzzy match)
-claw -g "family" "Remind everyone about dinner at 7"
-
-# Send to a group by exact JID
-claw -j "120363336345536173@g.us" "Hello"
-
-# Resume a previous session
-claw -s abc123 "Continue where we left off"
-
-# Read prompt from stdin
-echo "Summarize this" | claw --pipe -g dev
-
-# Pipe a file
-cat report.txt | claw --pipe "Summarize this report"
-
-# List all registered groups
-claw --list-groups
-
-# Force a specific runtime
-claw --runtime docker "Hello"
-
-# Use a custom image tag (e.g. after rebuilding with a new tag)
-claw --image nanoclaw-agent:dev "Hello"
-
-# Verbose mode (debug info, secrets redacted)
-claw -v "Hello"
-
-# Custom timeout for long-running tasks
-claw --timeout 600 "Run the full analysis"
-```
-
-## Troubleshooting
-
-### "neither 'container' nor 'docker' found"
-
-Install Docker Desktop or Apple Container (macOS 15+), or pass `--runtime` explicitly.
-
-### "no secrets found in .env"
-
-The script auto-detects your NanoClaw directory and reads `.env` from it. Check that the file exists and contains at least one of: `CLAUDE_CODE_OAUTH_TOKEN`, `ANTHROPIC_API_KEY`, `ANTHROPIC_AUTH_TOKEN`.
-
-### Container times out
-
-The default timeout is 300 seconds. For longer tasks, pass `--timeout 600` (or higher). If the container consistently hangs, check that your `nanoclaw-agent:latest` image is up to date by running `./container/build.sh`.
-
-### "group not found"
-
-Run `claw --list-groups` to see what's registered. Group lookup does a fuzzy partial match on name and folder — if your query matches multiple groups, you'll get an error listing the ambiguous matches.
-
-### Container crashes mid-stream
-
-Containers run with `--rm` so they are automatically removed. If the agent crashes before emitting the output sentinel, `claw` falls back to printing raw stdout. Use `-v` to see what the container produced. Rebuild the image with `./container/build.sh` if crashes are consistent.
-
-### Override the NanoClaw directory
-
-If `claw` can't find your database or `.env`, set the `NANOCLAW_DIR` environment variable:
-
-```bash
-export NANOCLAW_DIR=/path/to/your/nanoclaw
-```