nanobot-runtime/memory/MEMORY.md

Long-term Memory

This file stores important information that should persist across sessions.

Preferences

Report / result files

• Save important reports to results/ directory with descriptive, date-prefixed filenames (e.g., 2026-06-02_remind-skill-analysis-and-improvements.md)

Script-writing convention

• Location: always save scripts in the scripts/ directory.
• Language choice:
  • Extremely short script (a few lines) -> bash.
  • Longer / non-trivial script -> Python.
• Override: if the user explicitly specifies a language or location, their instruction always takes precedence.

Temporary files

• All temporary files go to tmp/ directory.
• Clean up after tests and one-off operations.

Project Context

• User wants to deploy "grill-me" plugin for Claude Code
• User wants to try "praneybehl/llm-wiki-plugin" for Claude Code — markdown-based thought management / organization
• Daily automated check for new nanobot Docker image releases with Telegram notifications (pending setup)
• Both user and assistant run on the same nanobot Docker image
• Docker CLI is unavailable in the current runtime environment
• Ollama cloud subscription: na požádání zobrazit aktuální využití (usage)
• Ollama cloud limity: 5hodinová session, 7denní týdenní okno
• /note skill: backend storage uses SQLite (not markdown)
• /note skill: má být deterministický a logovat všechny provedené operace
• /note skill: má být rozdělený na kratší prompt + python skript, který provádí operace
• nanobot podporuje cross-channel session continuity přes unifiedSession: true v config.json pod agents.defaults
• Uživatel nemá unifiedSession povolený v config.json (default false)
• Zapnutí unifiedSession sjednotí jen budoucí zprávy; existující session soubory vyžadují ruční merge/rename pro propojení minulých konverzací
• Session files are stored in /home/nanobot/.nanobot/workspace/sessions/ (confirmed after failed attempts at root .nanobot/sessions/)
• User explicitly rejected unified/Mega session approach; prefers connecting to older existing sessions instead
• Telegram slash commands (e.g., /skills) are filtered out by & ~filters.COMMAND in telegram.py:384; workaround: invoke skills without slash prefix (e.g., skills not /skills); alternative fix: remove the filter from MessageHandler
• nanobot v0.2.1 available (current: v0.2.0)

Agent Model Selection

• Ollama subscription covers all discussed models; price/cost excluded from model comparison criteria
• Prioritizes agentic performance, correct tool calling, and overall result quality
• Primary nanobot agent model: GLM-5.1:cloud (best sustained productivity over long sessions/hundreds of rounds, strong real-world agent benchmarks)
• Alternative nanobot agent model for tool-heavy tasks: Qwen 3.5:cloud (397B variant)
• Conservative fallback nanobot agent model: DeepSeek V3.2:cloud
• OpenRouter is pay-per-token alternative to Ollama subscription for model access
• Gemini Flash via Google AI Studio Free Tier: 15 RPM limit — unusable for agent work; only viable for simple prompts without tool calls
• Gemini Flash via Google AI Studio Tier 1 (paid): 360+ RPM
• Haiku (Claude) via OpenRouter: high rate limits, viable agent model alternative
• Gemini Flash Lite via OpenRouter: high rate limits, viable agent model alternative

Reminder System

• Reminder check script: /home/nanobot/.nanobot/workspace/skills/remind/scripts/remind_check.py
• Execution: exec via /home/nanobot/.local/bin/uv run <script>
• Empty output → silent exit (no notification sent)
• Each non-empty output line → forwarded as separate Telegram notification
• /remind critical issues: one-time at reminders fire repeatedly (60s tolerance window), non-atomic YAML writes, fragile manual YAML string construction, missing list subcommand, no tests for edit/send scripts, race condition between edit and send without file locking
• /remind fix priorities: P0 = atomic writes + deduplicate one-time reminders; P1 = list command + proper YAML serialization + validation; P2 = add tests; P3 = SQLite state tracking + edit command + cron step syntax

NuGet package caching

• Evaluating NuGet package hosting/caching on Linux
• Preferred solution: BaGetter (bagetter/BaGetter) — active BaGet fork with multiple upstream mirror support (PR #269), solves original BaGet's single-upstream limitation

Pending Tasks

• Seřídit BRANO na vchodových dveřích

Personal Notes

• Buy new merino shirt ("koupit nové merino triko")
• Reminder to write in travel diary: pants, pills, sprinkling ("kalhoty, prášky, sypani")

---

This file is automatically updated by nanobot when important information should be remembered.