diff --git a/memory/.dream_cursor b/memory/.dream_cursor index e26ed8d..0e92c3c 100644 --- a/memory/.dream_cursor +++ b/memory/.dream_cursor @@ -1 +1 @@ -305 \ No newline at end of file +306 \ No newline at end of file diff --git a/memory/MEMORY.md b/memory/MEMORY.md index d8c18e7..fdaa6f6 100644 --- a/memory/MEMORY.md +++ b/memory/MEMORY.md @@ -18,6 +18,9 @@ This file stores important information that should persist across sessions. - All temporary files go to `tmp/` directory. - Clean up after tests and one-off operations. +### Code changes +- User prefers changes to be made in a temporary clone under `workspace/tmp/` for review before applying + ## Project Context - User wants to deploy "grill-me" plugin for Claude Code @@ -37,13 +40,12 @@ This file stores important information that should persist across 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) -- User completed detached background research on the movie *Interstate 60* (slug: `interstate-60-movie-research`) -- User archived the completed detached task `interstate-60-movie-research` on 2026-06-02 - User wants deterministic IRC-bot-style command dispatch in nanobot where `!command text` invokes a registered Python function or external app and returns output without LLM agent involvement - User expects nanobot creators to implement custom command registration natively and considers existing workaround solutions unsatisfactory -- User requested patch study only with no actual code changes for nanobot IRC-bot command dispatch feature - Nanobot CommandRouter has priority/exact/prefix/interceptor tiers but lacks an extension point for custom command registration with all handlers hardcoded in builtin.py - Proposed nanobot patch adds a custom command tier to CommandRouter dispatching before session lock configured via `commands` section in config.json supporting exec script and python module/function handler types +- `AgentLoop.__init__` does not accept a `config` parameter; custom command loading must happen in `from_config()` after instance creation, guarded by `_custom_commands_loaded` flag to prevent duplicate registration +- Custom commands are dispatched inline before the session lock, same pattern as priority commands ## Agent Model Selection - Ollama subscription covers all discussed models; price/cost excluded from model comparison criteria