Idea
A read-only web viewer for everything memory-toolkit writes to disk:
- Workstreams — list, handoffs, last session per workstream
- Memory — search/filter across
feedback/, decisions/, reference/, notes/
- Notes timeline — daily notes with
WATCH: / DOC: / COMMIT: markers
- Sessions — index from
sessions.jsonl, click into transcripts
Since everything is markdown on the local filesystem with predictable structure (MEMORY.md, workstreams.json, frontmatter), a viewer is a pure parse-and-render job.
Scope
- Separate package — no coupling with plugin runtime, no new dependencies in the plugin itself
- Read-only — no edits, no writes. Source of truth stays in markdown files
- Static site — builds locally, optionally publishes to GitHub Pages
- Local-first — reads from
~/.claude/projects/*/memory/, no server, no cloud
Non-goals
- Not a replacement for reading markdown directly
- Not an editor — edits happen via
/memory, /park, manual edit
- Not a team / collaboration tool — memory stays per-user
Open questions
- Static build (vite + markdown renderer) vs local Electron app?
- How to handle multiple projects — one viewer per project, or project switcher?
- Session transcripts viewer — in-scope or separate RFC?
- Any privacy considerations if published to GH Pages (most memory is local-only, but notes may leak context)?
How to react
- 👍 "I'd use this" — helps gauge demand before investing
- 💬 Comment with your use case — what would you browse most often? Workstreams? Notes? Search?
- 🔨 If you want to prototype — please flag before starting so we can align on scope
Triggered by user feedback that visualization would be a killer feature. Parking here as RFC before building anything.
Idea
A read-only web viewer for everything memory-toolkit writes to disk:
feedback/,decisions/,reference/,notes/WATCH:/DOC:/COMMIT:markerssessions.jsonl, click into transcriptsSince everything is markdown on the local filesystem with predictable structure (
MEMORY.md,workstreams.json, frontmatter), a viewer is a pure parse-and-render job.Scope
~/.claude/projects/*/memory/, no server, no cloudNon-goals
/memory,/park, manual editOpen questions
How to react
Triggered by user feedback that visualization would be a killer feature. Parking here as RFC before building anything.