From c00804e2d07f2babd5edf48fc39d5266a25f9506 Mon Sep 17 00:00:00 2001 From: lachtan Date: Wed, 24 Jun 2026 18:26:05 +0200 Subject: [PATCH] memory --- memory/MEMORY.md | 52 ++----------------- .../SKILL.md | 4 +- 2 files changed, 5 insertions(+), 51 deletions(-) rename skills/{memory-compact => compact-memory}/SKILL.md (99%) diff --git a/memory/MEMORY.md b/memory/MEMORY.md index ce30dfe..cc972d1 100644 --- a/memory/MEMORY.md +++ b/memory/MEMORY.md @@ -23,32 +23,23 @@ This file stores important information that should persist across sessions. ## 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 - podman is acceptable as alternative to Docker CLI when required - 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 uses SQLite (not markdown); must be deterministic, log all operations, split into shorter prompt + Python script - URLs should be on separate lines in both `list` and `show` output, not buried in long text lines - Reminders DB schema has no "frequency" column; scheduling uses separate tables (schedule_at, schedule_cron, schedule_random, reminder_fires) -- Use `python3` not `python` on this system (latter not found) - 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 - User wants deterministic command dispatch in nanobot (`!command text` → registered Python function/external app, no LLM involvement); expects native implementation from nanobot creators, considers existing workarounds unsatisfactory -- User wants nanobot use-case analysis framed as personal project relevance, not generic use case lists - User is interested in litellm proxy for Ollama - User considers Raspberry Pi good for testing - User wants to try writing a nanobot extension in TypeScript - No existing `!` prefix handling in nanobot — all current commands use `/` prefix only -- cli_apps tool exists at nanobot/agent/tools/cli_apps.py — relevant for calling external apps from custom commands -- Note skill DB path is `db/note.sqlite`, not `skills/note/notes.db` (the latter is empty/wrong) ## Agent Model Selection - Prioritizes agentic performance, correct tool calling, and overall result quality @@ -58,58 +49,21 @@ This file stores important information that should persist across sessions. - 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 -- Kimi K2.6 vs GLM-5.1 agent comparison: Kimi leads SWE-Bench (80.2% vs ~77.8%), tool-error recovery (91.8% vs 88.4%), code quality (Tier A vs Tier C); GLM-5.1 leads schema adherence (99.6% vs 98.9%), tool-call latency (+140ms vs +210ms); GLM-5.1 tends to hallucinate non-existent APIs - Kimi K2.6 has known bug with random switching to Chinese output (reported by Cursor and Reddit users) — critical risk for Czech use -- Both Kimi K2.6 and GLM-5.1 are Chinese-English models without specific Czech training data — both risky for Czech -- Kimi K2.6 supports `preserve_thinking` mode for multi-turn agent scenarios (retains reasoning content across turns) - minimax-m3:cloud is blocked for nanobot agent deployment due to empty tool result responses (ollama/ollama #16389) - deepseek-v4-pro:cloud is blocked for interactive nanobot agent use due to 15.4 tok/s and 57s TTFT - deepseek-v4-flash:cloud is a viable nanobot agent alternative with 1M ctx, MIT license, and ~30-50 tok/s speed - qwen3.5:397b-cloud is a viable nanobot agent alternative with multimodal support, 1M ctx, 201 languages including Czech, but has speed and accuracy tradeoffs - devstral-2:123b-cloud is a viable nanobot agent alternative with Terminal-Bench 77.3%, coding-only focus, and 128K ctx limit - User is interested in switching to GLM-5.2:cloud as primary nanobot agent model if/when it becomes available on Ollama Cloud -- GLM-5.1:cloud achieves ~198 tok/s on Ollama Cloud - Agent model comparison report saved to `results/2026-06-07_ollama-cloud-agent-model-comparison.md` - User prefers Qwen model for deep research tasks (not currently in presets) - For Ollama Cloud `/detach` research tasks, explicitly specifying the model (e.g., `qwen35`, `gemini`) is more reliable than generic model-agnostic prompts - Available model presets: gemini-flash, gemini-flash-lite, glm, haiku, kimi, minimax, sonnet -## Wiki -- Wiki content is in Czech -- Wiki compile rule: ambiguous/conflicting sources must NOT be force-compiled — leave in `cml/raw/` or move to `_hard/`, log reason to `log.md` -- Wiki lint rule: lint is report-only, never make destructive edits to existing wiki pages without user confirmation -- Wiki compilation runs in isolated background sessions without user interaction (batch/hands-off mode) -- Wiki idempotency rule: if wiki pages already exist for a source, treat as done, move raw file to `_done/`, skip reconciliation -- Duplicate wiki sources (same URL as an already-compiled source) must be detected and moved to `_hard/` -- Every processed source must be moved out of `cml/raw/` to prevent cron reprocessing -- Wiki graph regeneration: run `wiki_graph_lint.py` + `wiki_graph_extract.py` after each ingest batch that adds graph metadata -- Wiki source pages need explicit `slug` field (e.g. `slug: source-flash-attention`) and `graph.node_id` + `canonical: true` to avoid UNIQUE constraint collision with concept/entity pages sharing the same filename stem -- `wiki_graph_extract.py` patched: skip duplicate slugs (first wins) instead of crashing on `nodes.slug` UNIQUE constraint -- Wiki current state: ~21 nodes, ~130+ edges (was 17 nodes, 125 edges after initial build) -- Wiki source ingested: source-lego-mindstorms-continued-use (LEGO MINDSTORMS discontinuation, Pybricks alternative, SPIKE Prime successor) -- Wiki entities: product-lego-mindstorms, product-pybricks, product-spike-prime -- Wiki concepts: digital-preservation, alternative-firmware - -## Reminder System - -- Reminder check script: `/home/nanobot/.nanobot/workspace/skills/remind/scripts/remind_check.py` -- Execution: `exec` via `/home/nanobot/.local/bin/uv run