Concepts

Use this page when you want to understand nanobot before changing advanced settings. It explains the moving parts without requiring you to read the source first.

If you want source-file ownership and extension points, read architecture.md after this page.

Runtime Shape

nanobot has one small core loop and several ways to enter it:

The simplest path is nanobot agent -m "Hello!": one inbound message goes through the agent loop and prints the reply in your terminal. The long-running path is nanobot gateway: channels receive messages from chat apps or the WebUI, publish them to the same agent loop, and send replies back to the originating channel.

Config vs Workspace

The default instance lives under ~/.nanobot/:

You can override both with command flags:

nanobot onboard --config ./bot-a/config.json --workspace ./bot-a/workspace
nanobot agent --config ./bot-a/config.json --workspace ./bot-a/workspace -m "Hello"
nanobot gateway --config ./bot-a/config.json --workspace ./bot-a/workspace

The config file controls what nanobot may use. The workspace is where nanobot keeps state for that instance.

Agent Workspace and Project Workspace

The configured workspace is the agent workspace. A WebUI chat can also select a different project workspace for repository-specific work without moving the agent's identity or durable state.

When no separate project is selected, one directory normally serves both roles. Selecting a project changes the working context for that chat; it does not create a second agent or relocate the configured agent workspace.

Config Format

config.json accepts both camelCase and snake_case keys. The docs use camelCase because nanobot writes config back to disk with camelCase aliases, for example apiKey, modelPresets, intervalS, and maxToolResultChars.

Most examples are partial snippets. Merge them into the existing file created by nanobot onboard; do not replace the whole file unless you want to reset the instance.

One Agent Turn

A normal turn follows this flow:

1. A channel receives a user message and publishes it to the message bus.
2. The agent loop chooses a session key and builds context from the effective project workspace, agent-owned profile/skills/memory, recent messages, channel metadata, and runtime settings.
3. The provider receives the model request.
4. If the model asks for tools, the runner executes them and feeds results back to the model.
5. The final reply is saved to the session and sent back through the channel.

That flow is the same whether the message starts in the CLI, WebUI, Telegram, Discord, or another channel.

CLI, Gateway, API, and WebUI

The WebUI launcher is the normal browser entry point. Underneath, the gateway keeps the WebSocket channel and other long-running services alive. The gateway health endpoint is on gateway.port (18790 by default); the browser WebUI is served on 8765 by default, not by the health endpoint.

Provider and Model Selection

The active model should normally come from a named modelPresets entry selected by agents.defaults.modelPreset. Direct agents.defaults.provider and agents.defaults.model still form the implicit default preset for older or minimal configs. The active provider is resolved in this order:

1. If the active preset provider or implicit default provider is not "auto", nanobot uses that provider.
2. If provider is "auto", nanobot tries to infer the provider from the model name, configured API keys, local provider base URLs, or gateway providers.
3. OAuth providers such as OpenAI Codex and GitHub Copilot require explicit login and explicit provider/model selection inside the active preset.

Pin the provider inside the preset when setting up for the first time. It is easier to debug:

{
  "modelPresets": {
    "primary": {
      "provider": "openrouter",
      "model": "anthropic/claude-opus-4.5"
    }
  },
  "agents": {
    "defaults": {
      "modelPreset": "primary"
    }
  }
}

See providers.md for practical examples and configuration.md#providers for the full provider reference.

Channels and Sessions

Each channel maps inbound messages to a session key. That lets independent conversations keep separate history. The WebUI also supports multiple chats and workspace-scoped metadata for project workspaces.

agents.defaults.unifiedSession can intentionally share one session across channels for a single-user multi-device setup. Leave it off if you expect separate people, groups, channels, or projects to keep separate context.

Memory, Sessions, and Dream

nanobot uses two related stores:

Dream is a periodic consolidation job. It reads accumulated history and updates workspace memory so useful context can survive beyond short session replay.

See memory.md for the detailed design.

Tools and Safety

Tools are discovered automatically from built-in modules and plugin entry points. Common tool groups include:

• file read/write/edit and patching;
• shell execution with configurable sandboxing;
• web search and web fetch with SSRF checks;
• MCP servers;
• cron reminders, local triggers, and heartbeat tasks;
• image generation;
• subagents and runtime self-inspection.

Security-sensitive controls live in configuration.md#security. For production or shared chat apps, also configure channel access controls such as allowFrom, pairing, or WebSocket tokens.

Background Jobs

When nanobot gateway starts, it runs workspace-scoped automations and registers system jobs:

• dream, when agents.defaults.dream.enabled is true;
• heartbeat, when gateway.heartbeat.enabled is true.

Heartbeat reads <workspace>/HEARTBEAT.md. If the file has tasks under ## Active Tasks, nanobot executes them and sends only useful/actionable results to the most recently active chat target. Routine "nothing changed" results are suppressed.

User-created reminders use the same cron service but are not the same as the protected heartbeat system job. They run as scheduled turns in their origin chat/session and normally deliver the result back to that channel.

Local triggers are also session-bound, but they do not have their own schedule. Create one from the target chat with /trigger <name>, then call nanobot trigger <id> "<message>" when a local script or external service wants nanobot to respond in that session. Webhook servers, third-party auth, and event-to-message formatting stay outside nanobot. Trigger deliveries are stored in the workspace until the linked agent turn finishes successfully. If the target session is busy, the trigger waits until that session is idle instead of being injected into the active turn. The message is recorded as an automation turn in that session. Delivery is at-least-once, so external systems should tolerate repeated trigger messages; a delivery that reaches the agent but fails is marked failed rather than retried forever.

Where to Go Next