# nanobot Python-based personal agent for files, chat channels and scheduled tasks. Canonical profile: https://ki-agentenkompass.de/en/agents/nanobot/ Editor: [Michael Meierhoff](https://ki-agentenkompass.de/en/about/) Sources reviewed: 2026-10-16 Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests. ## Overview nanobot is listed as a separate product profile. - Provider: HKUDS - Product family: nanobot - Profile type: Self-hosted personal agent - Environment: Own computer or server - Connections: Tools and channels according to configuration - Setup: Install the installer or Python package and configure a model. - Pricing model: Open source; model and operating costs are separate. ## Key features ### Work with files Read PDF, Word, Excel and PowerPoint files. Source: https://github.com/HKUDS/nanobot ### Work in the browser The WebUI provides setup and chat. Source: https://github.com/HKUDS/nanobot ### Connect chat channels Connect Telegram, Discord, Slack and other channels. Source: https://github.com/HKUDS/nanobot ### Schedule tasks Configure cron tasks for recurring work. Source: https://github.com/HKUDS/nanobot ### Configure models Use a model provider or local model server. Source: https://github.com/HKUDS/nanobot ## Example workflows ### Summarize a document - Your input: An anonymized PDF and a guiding question. - Possible result: A short summary for subject-matter review. - What to check: Check content, permissions and actions taken. ### Trigger a task through chat - Your input: A configured channel and a bounded test task. - Possible result: A result in the connected chat channel. - What to check: Record time spent, corrections and costs. ## Requirements and limits ### Setup Requirement: Configure the model, channels and permissions yourself. Source: https://github.com/HKUDS/nanobot ### German in everyday use Not yet confirmed: End-to-end German interaction and output quality have not been tested here. Source: https://github.com/HKUDS/nanobot ### Reliability Not yet confirmed: Success rates for specific workflows have not been measured here. Source: https://github.com/HKUDS/nanobot ## A good fit if … - you want to run a personal agent on your own machine or server - you want to talk to it through chat channels such as Telegram, Discord or Slack - you can handle the installation and model configuration yourself ## Less suitable if … - you want a managed service with central user and permission management - you expect automatic resumption after a crash or restart Editorial assessment based on provider documentation. Not a product test. ## Usable AI models Open choice nanobot does not supply a model account: you connect your own keys or sign-ins, routers such as OpenRouter, or an OpenAI-compatible endpoint. Models run locally through Ollama, LM Studio or vLLM. - Model families named: Anthropic (Claude), OpenAI (GPT), DeepSeek, xAI (Grok), Alibaba (Qwen), Moonshot (Kimi), MiniMax · Other models can be connected freely - Model choice: You choose - Your own API key: Yes - Router or custom endpoint: Yes - Local models: Yes Documented · Sources accessed on: 2026-11-05 - [nanobot: Providers and Models](https://github.com/HKUDS/nanobot/blob/main/docs/providers.md) - [nanobot: README](https://github.com/HKUDS/nanobot) ## Europe & regional availability Installation instructions and model prerequisites reviewed. The assessment covers the local operating path described; complete country and feature availability of all connected services remains open. Reviewed scope: Local software and documented self-hosting; external services assessed separately Reviewed on: 2026-10-19 ### Self-hosting with own model access With requirements Python installation and a local or server-side gateway are documented. A supported model provider or your own model server is required; nanobot does not include a model account. Region covered: Europe: own computer or server; model services are country-specific Documented reason: Technical assessment based on installation and provider selection. These sources do not establish a legal cause for regional restrictions. Official source: https://raw.githubusercontent.com/HKUDS/nanobot/main/README.md ## Accounts & permissions Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use. Configuration covered: Self-hosted nanobot instance with chat channels and the WebUI Sources reviewed: 2026-11-05 ### Account used Open in reviewed sources: The project page lists channels such as Telegram, Discord and Slack but does not describe which identity (bot account, token) the agent uses there. Evidence: https://github.com/HKUDS/nanobot ### Admin approval Documented with conditions: Check direct-message pairing, the allowlist and group-access policies separately for each chat platform: approving a private sender does not restrict group access on every platform. WebUI access grants administration of the same agent instance. Evidence: https://github.com/HKUDS/nanobot ### Data access & team sharing Documented with conditions: For a selected project folder, the default permission is workspace-only access. One instance shares its agent profile, memory and skills across projects; separate instances are meant for cases where data or preferences must stay isolated. Evidence: https://github.com/HKUDS/nanobot ## Prices and included usage Pricing checked: 2026-10-16 Open source; model and operating costs are separate. Total cost depends on access, usage and configuration. Pricing details: https://github.com/HKUDS/nanobot ## Operation & oversight Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured. Deployment covered: Self-hosted gateway in background mode with scheduled automations Sources reviewed: 2026-11-05 ### Files and working state Documented: Files created by tools remain after the chat closes. Conversation history can be kept in SQLite; temporary chats stay out of saved history and long-term memory. Evidence: https://github.com/HKUDS/nanobot ### Sign-ins Open in reviewed sources: The project page does not describe how long channel connections stay valid or what happens on expiry. Evidence: https://github.com/HKUDS/nanobot ### Starting further runs Documented: Scheduled automations run via cron. Tasks can be edited or paused and recent runs inspected; in the WebUI you manage schedules under Tasks. Missed times are not replayed after a gateway restart. Evidence: https://github.com/HKUDS/nanobot ### Human intervention Open in reviewed sources: The project page names no approval flow for tool actions, only permission settings such as the default of workspace-only access. Evidence: https://github.com/HKUDS/nanobot ### Detecting errors Documented with conditions: The command nanobot gateway logs shows background gateway logs. Failure notifications are not described. Evidence: https://github.com/HKUDS/nanobot ### Resuming after failures Documented: After a restart you reopen the topic, review saved results and explicitly resume interrupted work. Uncertain tool actions are not replayed and interrupted subagents are not relaunched automatically. Evidence: https://github.com/HKUDS/nanobot ### Editorial assessment You run and monitor the instance yourself. After restarts you resume work manually and check access rules per chat channel. ## Memory and conversation continuity Scope: Current memory and dream system Sources accessed: 2026-11-04 Conversation compaction produces history; dreaming transfers selected insights into versioned files. ### Storage and scope Documented: Workspace files SOUL.md, USER.md and memory/MEMORY.md form durable memory; history.jsonl holds compacted conversation segments. - [Memory and dreaming](https://raw.githubusercontent.com/HKUDS/nanobot/main/docs/memory.md) ### Selection and timing Documented: Compaction runs on context growth, inactivity or /compact; enabled dreaming processes new summaries on schedule or through /dream. - [Memory and dreaming](https://raw.githubusercontent.com/HKUDS/nanobot/main/docs/memory.md) ### Inspect, edit and delete Documented: Memory files can be inspected and corrected; GitStore versions changes. Archive cleanup is separate from durable facts. - [Memory and dreaming](https://raw.githubusercontent.com/HKUDS/nanobot/main/docs/memory.md) ### Agent and channel boundaries Documented: One instance shares profile and memory across projects; separate instances create separate personal memories. - [nanobot repository](https://github.com/HKUDS/nanobot) ### Retrieval Partly documented: Durable profile files supply context; dreaming reads new archive summaries. An additional vector index is not established here. - [Memory and dreaming](https://raw.githubusercontent.com/HKUDS/nanobot/main/docs/memory.md) ### Session reset and compaction Documented: Memory files survive new sessions. Compaction creates summaries; later archive cleanup does not remove original chat files. - [Memory and dreaming](https://raw.githubusercontent.com/HKUDS/nanobot/main/docs/memory.md) ## Context Configure the model, channels and permissions yourself. Provider sources reviewed; examples are editorial. No hands-on tests. ## Open points Requirements and limits, not yet confirmed: - German in everyday use - Reliability ## Sources - https://github.com/HKUDS/nanobot ## Provider Publishes nanobot and the linked product information. - Operator: HKUDS - Organization: Open-source project - Website: https://github.com/HKUDS/nanobot - Reviewed: 2026-10-16 - Provider source: https://github.com/HKUDS/nanobot [Sources and method](https://ki-agentenkompass.de/en/sources/)