Problem
The memory plugin stores files in an opaque location tied to OPENCODE_CONFIG_DIR — users have no way to discover where their memories physically live without spelunking through the filesystem.
Request
Add a /memory slash command that opens a menu/info panel showing at minimum:
- Storage paths: Where global, session, and repo memories are stored on disk (actual filesystem paths)
- Listing: All memory files grouped by scope (global / session / repo)
- Stats: Count of memories per scope, total size
This would save users from having to manually find files via find/grepping through OPENCODE_CONFIG_DIR.
Implementation notes
- The
/memory command already exists in some OpenCode builds — this plugin should hook into or replace it
- Config info is deterministic:
OPENCODE_CONFIG_DIR/memories/ for global, same dir with session/ subfolder for session, project .opencode/ for repo
- A simple TUI list with file paths + ability to open/delete would be ideal
Problem
The memory plugin stores files in an opaque location tied to
OPENCODE_CONFIG_DIR— users have no way to discover where their memories physically live without spelunking through the filesystem.Request
Add a
/memoryslash command that opens a menu/info panel showing at minimum:This would save users from having to manually find files via
find/grepping throughOPENCODE_CONFIG_DIR.Implementation notes
/memorycommand already exists in some OpenCode builds — this plugin should hook into or replace itOPENCODE_CONFIG_DIR/memories/for global, same dir withsession/subfolder for session, project.opencode/for repo