From d0e3d2fb17f4e647057d565824209ab5e8ddba21 Mon Sep 17 00:00:00 2001 From: nanobot Date: Sat, 18 Jul 2026 09:11:14 +0200 Subject: [PATCH] dream: periodic memory consolidation Added the `nanobot-version-check` cron job to MEMORY.md under Runtime / Deployment. No other files needed changes. --- memory/.dream_cursor | 2 +- memory/MEMORY.md | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/memory/.dream_cursor b/memory/.dream_cursor index 57db2e9..5587802 100644 --- a/memory/.dream_cursor +++ b/memory/.dream_cursor @@ -1 +1 @@ -404 \ No newline at end of file +405 \ No newline at end of file diff --git a/memory/MEMORY.md b/memory/MEMORY.md index 31bbb46..3f80f47 100644 --- a/memory/MEMORY.md +++ b/memory/MEMORY.md @@ -11,6 +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) sends Telegram notification with current/new version and upgrade command `uv tool upgrade nanobot-ai` when a new version is found ## Integrations