diff --git a/build.cfg b/build.cfg index 7c4a0eb..db29694 100644 --- a/build.cfg +++ b/build.cfg @@ -125,7 +125,7 @@ if [ "${COLIBRI_STAGE_TEST_AGENT}" = "auto" ]; then *) COLIBRI_STAGE_TEST_AGENT="YES" ;; esac fi -ZOT_VERSION="${ZOT_VERSION:-v0.2.42}" +ZOT_VERSION="${ZOT_VERSION:-v0.2.47}" ZOT_REPO="${ZOT_REPO:-/home/clawdie/ai/zot}" ZOT_ARTIFACT_DIR="${ZOT_ARTIFACT_DIR:-}" # Optional: bake the operator's DeepSeek key into the agent's auth.json (0600). diff --git a/live/operator-session/seed/AGENTS.md b/live/operator-session/seed/AGENTS.md index f530377..70af139 100644 --- a/live/operator-session/seed/AGENTS.md +++ b/live/operator-session/seed/AGENTS.md @@ -35,8 +35,9 @@ External MCP tools are discoverable via colibri status. ## After self-configuration 1. Verify the daemon is running: service colibri_daemon status -2. Register with mother: use the node_register MCP tool with output from - clawdie-hw-probe. +2. Register with mother: read CLAWDIE_HW_PROFILE from your environment + (the daemon collected it at boot) and call the node_register MCP tool + on the mother server with that JSON. 3. Install Hermes from /home/clawdie/ai/hermes-bsd per README-FreeBSD.md for persistent agent identity. diff --git a/scripts/stage-colibri-iso.sh b/scripts/stage-colibri-iso.sh index 10b73e3..22346e1 100755 --- a/scripts/stage-colibri-iso.sh +++ b/scripts/stage-colibri-iso.sh @@ -121,6 +121,13 @@ COLIBRI_AUTOSPAWN="YES" # support (DeepSeek native, OpenRouter, ~25 providers) and a built-in # Telegram bot mode. Set COLIBRI_AUTOSPAWN_BINARY=pi to switch back. COLIBRI_AUTOSPAWN_BINARY="zot" +# RPC prompt sent to the autospawned zot agent on first boot. +# zot is in RPC mode and blocks on stdin; this prompt kicks it off. +# The daemon collected hw-probe at boot (CLAWDIE_HW_PROFILE); the seed +# importer installed AGENTS.md with operational context; the provider +# keys are either baked or seeded. The agent's first job: register +# this node with mother, then report its assigned capabilities. +COLIBRI_AUTOSPAWN_RPC_PROMPT="You just booted. Read CLAWDIE_HW_PROFILE from your environment and call node_register on the mother MCP server with that JSON payload. Then report what capabilities mother assigned and what tasks are available. Your AGENTS.md context explains the verbs and infrastructure." # Telegram bot token — set this to enable the bot channel (@your_bot). # Leave blank to use CLI/TUI/Dashboard channels only. # TELEGRAM_BOT_TOKEN=""