6.4 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Nanobot | agent | active | 2026-07-22 | 2026-11-20 | 2026-11-20 | high |
|
|
Nanobot
Purpose
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 IP100.122.189.81. - User:
nano - Workspace:
/home/nano/.nanobot/workspace
Current state
- Status: ACTIVE. Re-verified 2026-11-20:
nanobot-gatewayPID 1256104 (since 2026-11-19),/health→status ok, ready true, v0.4.1. (Prior check 2026-10-11: PID 2259048.) - Gateway: port
8765(HTTP API + chat completions) —LISTEN 0.0.0.0:8765 - WebSocket bridge: port
8766—LISTEN 0.0.0.0:8766 - Serve API: port
8900was recorded as the Serve API; not listening in the 2026-10-11ss -ltncheck. Treat as unverified/possibly removed. - Service unit names: earlier notes listed
whatsapp-bridge.service—systemctl is-active nanobot gatewayandis-active gatewayare NOT valid here (both returnedinactive). Nanobot runs as a user service under thenanobotuser (systemd --user, PID 166) plus thenanobot-gatewayprocess; it is not a system-levelnanobot.service. Check the gateway port/process, not the systemd unit.
Confirmed running on CT333 (2026-10-11)
| Process | Owner | Port(s) | Notes |
|---|---|---|---|
nanobot-gateway (PID 2259048) |
— | 8765, 8766 | The gateway |
mnemosyne MCP (mnemosyne mcp --transport std…) |
nano | — | venvs/mnemosyne-mcp venv |
chroma_query_api.py |
nano | — | started Sep 23 |
agentmail-daemon.py |
nano | — | started Sep 23 |
readlater Next dev server |
nano | 3210 | started Sep 23 |
Other listeners on CT333 include 8787, 8880, 8899, 8999, 5050, 8080 and the Tailscale 443. (Port 3000 was published by the steel-browser container, which was removed 2026-10-29.)
Docker on CT333 (verified 2026-10-11; Steel container removed 2026-10-29)
→ 2026-11-20 live list: tender_brattain, plus healthy community-spark and quirky_darwingotify, readlater, readlater-extraction-worker, kokoro-tts, edge-tts, onecli-postgres-1, ecstatic_swartz (random-name successor of tender_brattain), healthy community-spark; quirky_darwin removed; stopped qdrant present (Exited 5 months ago).
Steel is gone from CT333 too. The steel-browser container (image ghcr.io/steel-dev/steel-browser:latest, 5.53 GB, created 2026-05-30, publishing port 3000) and its image were removed on 2026-10-29. It was already orphaned — its last CDP navigation was 2026-10-20, it crashed on 2026-10-22, it received no requests after 2026-10-21, and it had no Tailscale Serve route, no entry in ~/.zeroclaw/config.toml (which uses backend = "agent_browser" on native_webdriver at 127.0.0.1:9515), and no reference from Nanobot's browser harness. → comparisons/steel-vs-camoufox
Cron jobs
Verified live 2026-11-20 from /home/nano/.nanobot/workspace/cron/jobs.json — 11 jobs, 8 enabled
(all schedules Australia/Perth):
| Job | Schedule | Enabled |
|---|---|---|
auto-upgrade-freellmapi-safeguard |
daily 03:30 | ✅ |
nightly-skills-export-sync |
daily 04:00 | ✅ |
morning-news-podcast |
daily 07:00 | ✅ |
daily-quota-730am |
daily 07:30 | ✅ |
morning-quota-report |
daily 07:30 | ❌ disabled |
vault-daily-seed |
daily 08:00 | ✅ |
daily-agent-briefing |
daily 08:15 | ❌ disabled (2026-10-30) |
daily-quota-7pm |
daily 19:00 | ✅ |
evening-quota-report |
daily 21:00 | ❌ disabled |
heartbeat |
every 30m | ✅ |
dream |
every 2h (memory consolidation) | ✅ |
No longer in the scheduler (removed at
some point before 2026-11-20; the enabled quota-notification pair rss-check-proxmox-selfhst — Mon/Thu at 09:00 AWSTdaily-quota-730am /
daily-quota-7pm remains enabled, per Anthony's standing preference).
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.
Connected systems
Known issues
- Context window management requires periodic skill audits; baseline skill catalog + MCP schemas consume ~38–51K tokens per turn.
- Model preset
freellmapi-automay route through fallback models depending on provider availability. - See incidents/nanobot-degraded-2026-08-07 for prior outage.
Relevant runbooks
Re-verified 2026-11-20 (stocktake, live probes on CT333). Gateway healthy:
GET :8765/health→{"status":"ok","ready":true,"websocket":"running","version":"0.4.1"};nanobot-gatewayPID 1256104 (started 2026-11-19), ports 8765 + 8766 listening, 8900 still not listening. Tailscale IP confirmed100.122.189.81. The mnemosyne MCP, chroma_query_api, agentmail-daemon and readlater (:3210) processes all still run.Docker drift corrected: live
docker ps -ashowsecstatic_swartz(Up 19h) where this page listedtender_brattain— Docker regenerates random names for compose-less containers, so this is a rename-class drift, not a new service.quirky_darwinis absent even with-a(removed, not stopped).community-spark,gotify,readlater,readlater-extraction-worker,kokoro-tts,edge-tts,onecli-postgres-1all Up ~9 days and healthy where applicable; a stoppedqdrant(Exited 5 months ago) also exists. No steel container or image remains; nothing on :3000.Cron verified live 2026-11-20 from
/home/nano/.nanobot/workspace/cron/jobs.json(the~/.nanobot/cron/dir is empty — the scheduler file lives underworkspace/cron/): 11 jobs, 8 enabled — see the rewritten Cron jobs section above.