dream: periodic memory consolidation

Hotovo. Jediná změna: v `memory/MEMORY.md` jsem upřesnil popis `nanobot-version-check` cron jobu podle nové historie (porovnání verzí, notifikace přes Telegram, upgrade příkaz). Ostatní soubory už obsahovaly relevantní fakta (čeština v `USER.md`, cron detaily v `MEMORY.md`), takže nebylo potřeba nic přidávat ani přesouvat. Žádný nový skill nevznikl — jde o jednorázovou konfiguraci cron jobu, ne opakovatelný workflow.
This commit is contained in:
nanobot
2026-07-26 09:16:15 +02:00
parent 5f1a172fe8
commit 882d0445b2
2 changed files with 2 additions and 2 deletions

View File

@@ -1 +1 @@
413
414

View File

@@ -11,7 +11,7 @@ This file stores important information that should persist across sessions.
- Runs as a systemd user service `nanobot.service`
- Model switching via `my` tool requires `tools.my.allow_set = true` in config
- `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 to 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
- `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