lachtan/nanobot-runtime
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

dream: 2026-06-21 11:10, 6 change(s)

Browse Source 
[MEMORY] User wants nanobot use-case analysis framed as personal project relevance, not generic use case lists
[MEMORY] User is interested in litellm proxy for Ollama
[MEMORY] User considers Raspberry Pi good for testing
[MEMORY] User wants to try writing a nanobot extension in TypeScript
[USER-REMOVE] "Chce use case nápady pokrývající: built-in skills i integrace third-party / self-hosted nástrojů" — overlaps with line above about use case ideas; merge into single line
[MEMORY-REMOVE] "Nanobot CommandRouter has priority/exact/prefix/interceptor tiers but lacks an extension point for custom command registration with all handlers hardcoded in builtin.py ← 15d" — redundant with proposed patch line below it
[MEMORY-REMOVE] "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 ← 15d" — overly verbose; keep only the `:skillname` prefix line
[MEMORY-REMOVE] "`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 ← 15d" — overly granular implementation detail
[MEMORY-REMOVE] "Custom commands are dispatched inline before the session lock, same pattern as priority commands ← 15d" — redundant with proposed patch summary
[MEMORY-REMOVE] "Nanobot turn state machine: RESTORE→COMPACT→COMMAND→BUILD→RUN→SAVE→RESPOND→DONE; matched non-priority commands shortcut to DONE skipping BUILD/RUN/SAVE ← 15d" — overly granular implementation detail
[MEMORY-REMOVE] "Nanobot command handler return contract: OutboundMessage | None — None = fall through to LLM agent (/goal uses this hybrid pattern: returns None → LLM receives modified content) ← 15d" — overly granular implementation detail
[MEMORY-REMOVE] "`/note` skill: má být deterministický a logovat všechny provedené operace ← 22d" — consolidate with other `/note` lines into one
[MEMORY-REMOVE] "`/note` skill: má být rozdělený na kratší prompt + python skript, který provádí operace ← 22d" — consolidate with other `/note` lines into one
This commit is contained in:
nanobot
2026-06-21 11:55:23 +02:00
parent 9a880d4b20
commit 0f07a76314
3 changed files with 6 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
memory/.dream_cursor
View File

@@ -1 +1 @@
366
367

14
memory/MEMORY.md
View File

@@ -31,9 +31,7 @@ This file stores important information that should persist across sessions.
- 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 storage uses SQLite (not markdown)
- `/note` skill: má být deterministický a logovat všechny provedené operace
- `/note` skill: má být rozdělený na kratší prompt + python skript, který provádí operace
- `/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
- 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)
@@ -44,12 +42,10 @@ This file stores important information that should persist across sessions.
- 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
- Zájem o `:skillname` prefix pro deterministické vyvolání skillu bez LLM deliberace — varianta navrhovaného custom command patche s `!` prefixem
- 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
- Nanobot turn state machine: RESTORE→COMPACT→COMMAND→BUILD→RUN→SAVE→RESPOND→DONE; matched non-priority commands shortcut to DONE skipping BUILD/RUN/SAVE
- Nanobot command handler return contract: OutboundMessage | None — None = fall through to LLM agent (/goal uses this hybrid pattern: returns None → LLM receives modified content)
- 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)