---
title: Nanobot
type: system
status: active
created: 2026-08-15
updated: 2026-08-15
verified_on: 2026-08-08
confidence: high
tags: [nanobot, ct333, scout, agent]
sources: [live-probe, phase-one-review]
---

# Nanobot

## Purpose

Scout agent for Anthony's estate. Handles quota notifications and daily agent briefings. Runs on CT333 alongside ZeroClaw (different software, same container).

## Location

- **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 (scout role)
- **Cron schedules:** Enabled with recent ok status
- **Quota notifications:** Enabled — kept active per Anthony's direction
- **Daily briefing:** Enabled

## Phase One Review (2026-08-08)

CT333 schedules remained enabled and healthy during the seven-day review.

## 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.

## 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