Files
nanobot-runtime/memory/MEMORY.md
nanobot de0f4c8a8f dream: periodic memory consolidation
memory/MEMORY.md: +0 -1
1 file changed, 0 insertions(+), 1 deletion(-)

```diff
--- memory/MEMORY.md
+++ memory/MEMORY.md
@@ -11,7 +11,6 @@
 - Runs as a systemd user service `nanobot.service`; model switching via `my` needs `tools.my.allow_set = true`
 - `compact-memory-auto-daily` runs as a system crontab script (not a nanobot cron/jobs.json job) with a fresh session per run; delivers its report straight to Telegram via Bot API
 - `nanobot-version-check` cron job (schedule `0 8 * * *` Europe/Prague) checks PyPI for latest `nanobot-ai` version and compares it against installed version from `nanobot --version`; if newer version exists, sends Telegram notification with current version, new version, and upgrade command `uv tool upgrade nanobot-ai`; if up to date, does nothing
-- `uv` is currently unavailable and system Python lacks `croniter`; remind skill CLI cannot run via `uv run` — requires direct SQLite database access instead
 
 ## Integrations
 
```
2026-08-26 02:26:43 +02:00

1.2 KiB

Long-term Memory

This file stores important information that should persist across sessions.

Project Context

  • Goal: interconnect remind, keep, note, and todo into a unified workflow

Runtime / Deployment

  • Runs as a systemd user service nanobot.service; model switching via my needs tools.my.allow_set = true
  • compact-memory-auto-daily runs as a system crontab script (not a nanobot cron/jobs.json job) with a fresh session per run; delivers its report straight to Telegram via Bot API
  • nanobot-version-check cron job (schedule 0 8 * * * Europe/Prague) checks PyPI for latest nanobot-ai version and compares it against installed version from nanobot --version; if newer version exists, sends Telegram notification with current version, new version, and upgrade command uv tool upgrade nanobot-ai; if up to date, does nothing

Integrations

  • Integrations: KAYAK is the sole flight-search source; PCTuning.cz, vtm.zive.cz, zive.cz block automated fetching

Architecture

  • Cross-channel session continuity via unifiedSession: true; backups: wood.hell → pivo.hell (recursive)

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