OpenCode SmartPi Memory Guardian

Problem

When a new OpenCode session starts, earlier configuration notes, debugging conclusions, and work plans are easy to lose. On low-resource ARM64 devices such as SmartPi, with only around 2GB of usable space, running a heavier memory stack is often impractical. OpenCode SmartPi Memory Guardian targets this specific setup: instead of acting as a general knowledge base, it preserves recoverable context through a minimal file set and syncs local state to Gitee or GitHub using Git, reducing the risk of losing progress after an unexpected reboot.

How It Works

The skill organizes memory into directly editable Markdown files:
- MEMORY.md: stores core SmartPi memory, system configuration, and resolved issues
- INDEX.md: provides a quick navigation index
- 2026-04-30.md: serves as a daily work log template
At the start of a session, OpenCode can read these files to reconstruct device state, existing configuration, and outstanding tasks. Before a session ends, important changes can be written back into the memory files and synchronized through git. The design stays lightweight: it expects at least 100MB of free space, Debian 10 or a compatible system, Git, and a Gitee or GitHub account.

Boundaries

It fits embedded development machines that need a small amount of cross-session engineering context, but it is not a replacement for full RAG, vector search, or enterprise audit systems. If memory content includes secrets, personal identity data, or sensitive configuration, it should be sanitized before syncing. Git synchronization provides traceable backup, but it does not automatically handle permission isolation or offline access constraints.