[USER] prefers scheduling tasks via cron jobs with `message` to leverage agent skills and LLM capabilities, rather than standalone shell scripts [MEMORY] pending task: seřídit BRANO na vchodových dveřích (adjust/fix BRANO on entrance doors) [SKILL] reminder-check-and-notify: Run remind_check.py via uv run; exit silently on empty output; forward non-empty lines as brief natural Czech Telegram notifications without progress narration or status labels
44 lines
1.2 KiB
Markdown
44 lines
1.2 KiB
Markdown
# Long-term Memory
|
|
|
|
This file stores important information that should persist across sessions.
|
|
|
|
## User Information
|
|
|
|
(Important facts about the user)
|
|
|
|
## Preferences
|
|
|
|
### Script-writing convention
|
|
- Location: always save scripts in the `scripts/` directory.
|
|
- Language choice:
|
|
- Extremely short script (a few lines) -> bash.
|
|
- Longer / non-trivial script -> Python.
|
|
- Override: if the user explicitly specifies a language or location, their instruction always takes precedence.
|
|
|
|
### Temporary files
|
|
- All temporary files go to `tmp/` directory.
|
|
- Clean up after tests and one-off operations.
|
|
|
|
## Project Context
|
|
|
|
- User wants to deploy "grill-me" plugin for Claude Code
|
|
|
|
## Reminder System
|
|
|
|
- Reminder check script: `/home/nanobot/.nanobot/workspace/skills/remind/scripts/remind_check.py`
|
|
- Execution: `exec` via `/home/nanobot/.local/bin/uv run <script>`
|
|
- Empty output → silent exit (no notification sent)
|
|
- Each non-empty output line → forwarded as separate Telegram notification
|
|
|
|
## Active Issues
|
|
|
|
- Test reminder firing every minute on 2026-05-27 needs deletion or interval adjustment
|
|
|
|
## Pending Tasks
|
|
|
|
- Seřídit BRANO na vchodových dveřích
|
|
|
|
---
|
|
|
|
*This file is automatically updated by nanobot when important information should be remembered.*
|