712a0e1e01
Adds three allowlist-friendly setup helpers so /new-setup and /new-setup-2 don't hit unmatchable commands during a fresh install: - setup/install-node.sh — idempotent Node 22 install wrapper (macOS via brew, Linux via NodeSource + apt). Replaces the raw `curl | sudo -E bash -` flow whose stdin-consuming `bash -` segment can't be pre-approved. - setup/install-docker.sh — same pattern for Docker (brew --cask on macOS, get.docker.com on Linux + usermod). - setup/set-env.ts — generic `--step set-env` that writes KEY=VALUE to .env (and optionally syncs to data/env/env) so channel-install flows don't invent `grep && sed && rm` pipelines, which split at each && and can't be tightly allowlisted. new-setup-2's Telegram path now uses set-env for TELEGRAM_BOT_TOKEN and explicitly skips /add-telegram's Credentials section. new-setup step 1 and step 2 now call the install wrappers; the raw curl/apt entries are gone from the allowed-tools list. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
156 lines
8.3 KiB
Markdown
156 lines
8.3 KiB
Markdown
---
|
|
name: new-setup-2
|
|
description: Follow-on to /new-setup. Captures the operator and agent names, wires a real messaging channel, and adds quality-of-life extras. Linear rollthrough; every step is skippable. Invoked when the user picks "continue setup" at the end of /new-setup.
|
|
allowed-tools: Bash(bash setup/probe.sh) Bash(bash setup/install-telegram.sh) Bash(bash setup/install-telegram.sh:*) Bash(pnpm exec tsx setup/index.ts:*) Bash(pnpm exec tsx scripts/init-first-agent.ts:*) Bash(tail:*) Bash(head:*) Bash(grep:*)
|
|
---
|
|
|
|
# NanoClaw phase-2 setup
|
|
|
|
Runs after `/new-setup`. At this point the host is running and a throwaway CLI-only agent exists (used during /new-setup for the end-to-end ping check — inferred name, not user-facing). This flow creates the **real** agent and wires it to a messaging channel.
|
|
|
|
**Linear — one step at a time.** Every step is skippable: if the user says "skip", "not now", "later", or similar, move on without complaint. If they say they're done at any point, stop cleanly — don't push the remaining steps.
|
|
|
|
Before each step, narrate in your own words what's about to happen — one short, friendly sentence, no jargon. Match the tone of `/new-setup`.
|
|
|
|
## Current state
|
|
|
|
!`bash setup/probe.sh`
|
|
|
|
Parse the probe block above for `INFERRED_DISPLAY_NAME` and `PLATFORM` — referenced below.
|
|
|
|
## Steps
|
|
|
|
### 1. What should the agent call you?
|
|
|
|
Plain-prose ask (do **not** use `AskUserQuestion`):
|
|
|
|
> What should your agent call you? (Default: `<INFERRED_DISPLAY_NAME>`)
|
|
|
|
Capture the answer into a local variable `OPERATOR_NAME`. **Don't persist yet** — this value is consumed by step 3's channel wiring. If the user skips or confirms the default, set `OPERATOR_NAME = INFERRED_DISPLAY_NAME`.
|
|
|
|
### 2. What's your agent's name?
|
|
|
|
Plain-prose ask:
|
|
|
|
> What would you like to call your agent? (Default: `<OPERATOR_NAME>`)
|
|
|
|
Capture as `AGENT_NAME`. If skipped, set `AGENT_NAME = OPERATOR_NAME`. Nothing persisted yet.
|
|
|
|
### 3. Timezone
|
|
|
|
Run `pnpm exec tsx setup/index.ts --step timezone` and parse the status block.
|
|
|
|
- **RESOLVED_TZ is `UTC` or `Etc/UTC`** — before leaving UTC in `.env`, confirm with `AskUserQuestion`:
|
|
|
|
- **Question**: "Your system reports UTC as the timezone. Is that right, or are you somewhere else?"
|
|
- **Header**: "Timezone"
|
|
- **Options**:
|
|
1. `Keep UTC` — "Leave timezone as UTC."
|
|
2. `I'm somewhere else` — "I'll name the IANA zone (e.g. `America/New_York`, `Europe/London`, `Asia/Tokyo`) via Other."
|
|
|
|
If they pick "I'm somewhere else" (or type an IANA zone via Other), re-run `pnpm exec tsx setup/index.ts --step timezone -- --tz <answer>` to overwrite `.env`. If they keep UTC or skip, leave UTC in place.
|
|
|
|
- **NEEDS_USER_INPUT=true** — autodetection failed. Use `AskUserQuestion` with the same two options above (reword the question to "Autodetection failed — what timezone are you in?"), then re-run `pnpm exec tsx setup/index.ts --step timezone -- --tz <answer>` if they supply one. If they skip, move on.
|
|
|
|
- Otherwise — timezone is already set; move on.
|
|
|
|
### 4. Pick a messaging channel
|
|
|
|
Print the list as a numbered plain-prose list (too many options for `AskUserQuestion`, which caps at 4). The user replies with a number or channel name. Preserve the numbering exactly:
|
|
|
|
> Which messaging channel should I wire your agent to?
|
|
>
|
|
> 1. **WhatsApp (native)** — `/add-whatsapp`
|
|
> 2. **WhatsApp Cloud (Meta official)** — `/add-whatsapp-cloud`
|
|
> 3. **Telegram** — `/add-telegram`
|
|
> 4. **Slack** — `/add-slack`
|
|
> 5. **Discord** — `/add-discord`
|
|
> 6. **iMessage** — `/add-imessage`
|
|
> 7. **Teams** — `/add-teams`
|
|
> 8. **Matrix** — `/add-matrix`
|
|
> 9. **Google Chat** — `/add-gchat`
|
|
> 10. **Linear** — `/add-linear`
|
|
> 11. **GitHub** — `/add-github`
|
|
> 12. **Webex** — `/add-webex`
|
|
> 13. **Resend (email)** — `/add-resend`
|
|
> 14. **Emacs** — `/add-emacs`
|
|
>
|
|
> Or say "skip" to leave this for later.
|
|
|
|
When the user picks one:
|
|
|
|
1. **Install the adapter.** For **Telegram**, run `bash setup/install-telegram.sh` directly — it bundles the preflight + fetch + copy + register + `pnpm install` + build from `/add-telegram` into one idempotent call. Then handle Telegram credentials inline (below) — **do not** invoke `/add-telegram` afterward; its Credentials section would generate an unapprovable `grep && sed && rm` to write `.env`. For every other channel, invoke the matching `/add-<channel>` skill via the Skill tool; it copies the adapter source in from the `channels` branch, registers it, installs the pinned npm package, and handles credentials. Some channels also run a pairing step as part of their flow.
|
|
|
|
**Telegram credentials (inline):**
|
|
- Walk the user through BotFather: `/newbot` → pick name + username ending in `bot` → copy the token.
|
|
- Remind them: in `@BotFather` → `/mybots` → their bot → Bot Settings → Group Privacy → **Turn off** (only needed if the bot will live in groups; DM-only can skip).
|
|
- Persist the token and sync it to the container mount with the generic setter:
|
|
|
|
```
|
|
pnpm exec tsx setup/index.ts --step set-env -- \
|
|
--key TELEGRAM_BOT_TOKEN --value "<token>" --sync-container
|
|
```
|
|
|
|
2. **Capture platform IDs.** After the `/add-<channel>` skill finishes (or after inline credentials for Telegram), you need two values: the operator's user-id on that platform, and the chat/channel platform-id. Each channel surfaces these differently — consult the **Channel Info** section at the bottom of that skill's `SKILL.md` for the exact path. For Telegram, run `pnpm exec tsx setup/index.ts --step pair-telegram -- --intent <main|wire-to:folder|new-agent:folder>` directly and follow its `PAIR_TELEGRAM_ISSUED`/`PAIR_TELEGRAM STATUS=success` blocks — `PLATFORM_ID` and `ADMIN_USER_ID` land in the success block.
|
|
3. **Wire the agent.** Run `init-first-agent.ts` in DM mode with `--no-cli-bonus` (this keeps the new agent off the CLI messaging group so the pre-existing throwaway agent still owns CLI routing cleanly):
|
|
|
|
```
|
|
pnpm exec tsx scripts/init-first-agent.ts \
|
|
--channel <channel> \
|
|
--user-id "<platform-user-id>" \
|
|
--platform-id "<platform-chat-id>" \
|
|
--display-name "<OPERATOR_NAME>" \
|
|
--agent-name "<AGENT_NAME>" \
|
|
--no-cli-bonus
|
|
```
|
|
|
|
4. **Announce.** On success, emit the encouragement line verbatim:
|
|
|
|
> Your agent is now available on {channel-name}, you can already start chatting — But I encourage you to continue and finish this setup, we're almost done!
|
|
|
|
Substitute `{channel-name}` with the friendly name (e.g. "Telegram", "WhatsApp", "Slack").
|
|
|
|
If the user skipped, move on to step 5.
|
|
|
|
### 5. Host directory access
|
|
|
|
By default, agent containers can only touch their own workspace. If the user wants the agent to read or write files in specific host directories, those paths need to go on the mount allowlist.
|
|
|
|
Use `AskUserQuestion`:
|
|
|
|
- **Question**: "Want your agent to read or write files in any host directories (e.g. a code project, `~/Documents`)?"
|
|
- **Header**: "Host mounts"
|
|
- **Options**:
|
|
1. `Keep isolated` — "Agent only touches its own workspace (Recommended)."
|
|
2. `Add host paths` — "I'll name the directories to allowlist via Other."
|
|
|
|
If they pick "Add host paths" (or name paths via Other), invoke `/manage-mounts` via the Skill tool to add them. If they keep it isolated or skip, move on.
|
|
|
|
### 6. Quality of life
|
|
|
|
Optional polish. Print the list; the user may pick zero, one, or several — invoke each chosen skill in sequence:
|
|
|
|
> Want to add any of these? Pick any that sound useful — or skip:
|
|
>
|
|
> - `/add-dashboard` — browser dashboard showing agent activity
|
|
> - `/add-compact` — `/compact` slash command for managing long sessions
|
|
> - `/add-karpathy-llm-wiki` — persistent knowledge-base memory for the agent
|
|
|
|
If the probe reports `PLATFORM=darwin`, also offer:
|
|
|
|
> - `/add-macos-statusbar` — macOS menu bar indicator with Start/Stop/Restart controls
|
|
|
|
Do **not** list `/add-macos-statusbar` on Linux. If the user skips everything, just move on.
|
|
|
|
### 7. Done
|
|
|
|
Short wrap-up:
|
|
|
|
> Setup complete. You can chat with your agent on {channel-name} — or via CLI with `pnpm run chat <message>`.
|
|
|
|
Substitute `{channel-name}` with whatever was wired in step 4. If step 4 was skipped, drop the "on {channel-name} — or" clause entirely so the line just mentions the CLI form.
|
|
|
|
## If anything fails
|
|
|
|
Same rule as `/new-setup`: don't bypass errors to keep moving. Read `logs/setup.log` or `logs/nanoclaw.log`, diagnose, fix the underlying cause, re-run the failed step.
|