mirror of
https://github.com/qwibitai/nanoclaw.git
synced 2026-06-12 18:11:51 +08:00
390e09597a
Post-install was a bare instruction block: "DM the bot, run /manage-channels". Replace it with an explicit Done/Stuck-style select backed by the handoff mechanism — Claude takes over, tails logs/nanoclaw.log for the inbound, inspects data/v2.db for the auto-created messaging_group row, runs scripts/init-first-agent.ts with the discovered platform_id + AAD user id, and verifies end-to-end. Operators who want to drive it themselves pick "I'll do it myself" and get the same terse instructions as before. Default is the handoff (recommended hint). Why Teams and not the other channels: Telegram/Discord/WhatsApp already have synchronous platform IDs we capture during setup, so init-first-agent runs inline. Teams platform IDs only exist after the first real inbound, so the wiring is necessarily deferred — and that deferred work is exactly what the handoff handles best. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>