Anthony/agent-estate-wiki
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: update nanobot agent page with current runtime state

Browse Source
This commit is contained in:
Nando
2026-08-17 03:07:49 +08:00
parent f1ea8fd228
commit 5b8ce92b8c
1 changed files with 43 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/nanobot.md
+43 -38
View File
@@ -1,56 +1,61 @@
---
title: Nanobot
type: system
type: agent
status: active
created: 2026-08-15
updated: 2026-08-15
verified_on: 2026-08-08
created: 2026-07-22
updated: 2026-08-17
verified_on: 2026-08-17
confidence: high
tags: [nanobot, ct333, scout, agent]
sources: [live-probe, phase-one-review]
tags: [agent, nanobot, homelab]
sources: [live-probe, runtime-config]
---
# Nanobot
## Purpose
Scout agent for Anthony's estate. Handles quota notifications and daily agent briefings. Runs on CT333 alongside ZeroClaw (different software, same container).
Primary homelab AI agent running on `clawtest` (CT333). Handles agent orchestration, memory, tool execution, and cross-channel messaging for Anthony.
## Location
- **Host:** LXC 333, hostname `clawtest`, Tailscale IP `100.122.189.81`.
- **User:** `nano`
- **Workspace:** `/home/nano/.nanobot/workspace`
- **Container:** LXC CT333 (`clawtest`)
- **Tailscale IP:** `100.122.189.81`
- **Port:** 8766 (Nanobot), 8900 (previously, now DOWN)
- **Shares container with:** [[agents/zeroclaw]]
## Current state
- **Status: ACTIVE.** Confirmed running as of 2026-08-17.
- **Gateway:** port `8765` (HTTP API + chat completions)
- **WebSocket bridge:** port `8766`
- **Serve API:** port `8900` (host `0.0.0.0`, requires `api_key` in config)
- **WhatsApp Bridge:** `whatsapp-bridge.service` active on ct333
- **Model preset:** `freellmapi-auto` (current session); baseline context window 200,000 tokens
## Current State
## Cron jobs
- `auto-upgrade-freellmapi-safeguard` — daily at 03:30 AWST
- `morning-quota-report` — daily at 07:30 AWST
- `daily-quota-730am` — daily at 07:30 AWST
- `vault-daily-seed` — daily at 08:00 AWST
- `daily-agent-briefing` — daily at 08:15 AWST
- `rss-check-proxmox-selfhst` — Mon/Thu at 09:00 AWST
- `daily-quota-7pm` — daily at 19:00 AWST
- `evening-quota-report` — daily at 21:00 AWST
- `heartbeat` — every 30m
- `dream` — every 2h (memory consolidation)
- **Status:** Active (scout role)
- **Cron schedules:** Enabled with recent ok status
- **Quota notifications:** Enabled — kept active per Anthony's direction
- **Daily briefing:** Enabled
## Skills
Active skills include: `agent-reach`, `verify-nanobot-config-against-docs`, `cli-app-exa`, `playwright`, `system-prompts-collection`, `agent-skill-retrieval`, `enhanced-search`, `api-gateway`, `debugging-and-error-recovery`, `mnemosyne-memory-hooks`, `proxmox-shell-fallback`, `agentmail`, `langfuse`, `install-and-verify-agent-skills`, `verify-system-claims`, `skill-interceptor`, `tool-call-failure-recovery`, `using-agent-skills`, `api-vault`, `repair-memory`, `patch-config-relative-paths`, `long-task-management`, `nanobot-full-restore-backup`, `context-diet`, `frontend-design`.
## Phase One Review (2026-08-08)
## Connected systems
- [[systems/hermes-agent]]
- [[systems/omniroute]]
- [[systems/gitea]]
- [[systems/chromadb]]
CT333 schedules remained enabled and healthy during the seven-day review.
## Known issues
- Context window management requires periodic skill audits; baseline skill catalog + MCP schemas consume ~38–51K tokens per turn.
- Model preset `freellmapi-auto` may route through fallback models depending on provider availability.
- See [[incidents/nanobot-degraded-2026-08-07]] for prior outage.
## Key Rules
- **Nanobot schedules remain enabled unless Anthony explicitly approves changes.**
- **Do not conflate with ZeroClaw.** They share CT333 but are different software.
- **Do not conflate with Open-Claw.** Open-Claw is VM 403, not CT333.
## Relationship to ZeroClaw
Nanobot and ZeroClaw share LXC CT333 (`clawtest`):
- **Nanobot:** JSON config, Telegram gateway bot
- **ZeroClaw:** TOML config, autonomous daemon (root)
They are different software with different configs, different users, and different purposes. Restarting one does not affect the other.
## Relevant runbooks
- [[runbooks/restart-hermes]]
- [[runbooks/nanobot-restart]]
## Related
- [[agents/zeroclaw]] — Autonomous daemon on same container
- [[agents/open-claw]] — Separate gateway on VM 403
- [[systems/nanobot]] — Detailed system page
- [[comparisons/hermes-vs-nanobot]] — Comparison
- [[comparisons/hermes-vs-nanobot]]