Feature: Dashboard UI for memory curation (promote/demote/bury)

[lee-fuhr]

(Re-filed from memory repo—my assistant pointed out I filed in the wrong place! And yes, I did mean memory-ts.)

Context

I've been building a dashboard UI for memory-ts and wanted to share some patterns that might be useful for the project or other users.

Features Implemented

1. Memory Curation Controls

• Promote/Demote: Incremental importance adjustment (±0.1 steps)
• Bury/Unbury: Toggle exclude_from_retrieval to hide memories from surfacing without deleting them
• Uses PATCH endpoint (which I added locally - see Feature request: PATCH endpoint for updating memory metadata #3)

2. Filtering & Sorting

• Filter by: Scope (global/project), Status (active/buried/superseded), Importance range
• Sort by: Importance (default), Most recent, Oldest
• Tag filtering: Click any #tag to filter by that tag

3. Visual Feedback

• Color-coded importance bars (green=high, yellow=medium, gray=low)
• Buried memories shown at 40% opacity with badge
• Project source display (project_id + path) so you know which session a memory came from

Screenshot

Terminal aesthetic with cyan accent:

• Scanline overlay effect
• JetBrains Mono font
• Dark theme (#0a0a0f background)

API Changes Required

The dashboard needs a PATCH endpoint to update memories. I added this locally (see issue #3):

PATCH /memory/:id
{
  "project_id": "...",
  "importance_weight": 0.9,
  "exclude_from_retrieval": true,
  "status": "archived"
}

Questions

1. Would a dashboard component be welcome in the main repo?
2. Any interest in the terminal aesthetic as a theme option?
3. Should curation features (promote/demote/bury) be part of core, or stay as add-ons?

Happy to contribute code if there's interest!

[RodrigoLuglio]

This is incredible work - I really appreciate the care you put into this.

The PATCH endpoint is now in v0.4.15 (closes #3), so your dashboard should work against the official API.

For the dashboard itself - I'd love to keep it as a companion package rather than in core. The memory system's philosophy is "invisible by default" - install and forget. A dashboard is a power-user tool, better as an opt-in.

Two paths:

1. You publish it yourself (full ownership, your pace)
2. We publish as @rlabs-inc/memory-dashboard (happy to collaborate)

Either way, once it's up we'll add it to the README under "Community Tools" / "Ecosystem".

The terminal aesthetic sounds beautiful btw - scanlines and JetBrains Mono? That's exactly my vibe.

[lee-fuhr]

Fantastic, I hope it'll be useful for some people. Here's what mine looks like now:

I have some session management commands I made that are, I think, injecting memories more proactively into the system, that ballooned my overall memory count pretty quickly from ~250 to ~500. Do you have a sense of how many is too many?

[lee-fuhr]

Going with the independent route - keeps things simple for my use case (personal tool I tinker with, happy for others to use).

Repo is public and ready: https://github.com/lee-fuhr/memory-dashboard

Feel free to add it to the ecosystem section whenever. Thanks again for the quick PATCH implementation - the promote/demote/bury features actually persist now.

[RodrigoLuglio]

I'm the one who thank you for the contribution my friend! Happy that you are using the memory system and cared about contributing. I really appreciate.
And please, let me know how it is going, what do you like, what you don't. Let's make it better! :)

And it is looking awesome, I'm gonna give it a spin right now!

[RodrigoLuglio]

Fantastic, I hope it'll be useful for some people. Here's what mine looks like now:

I have some session management commands I made that are, I think, injecting memories more proactively into the system, that ballooned my overall memory count pretty quickly from ~250 to ~500. Do you have a sense of how many is too many?

As per the amount of memories injected per message, if that's what you talking about, my idea is that none is better than noise, not sure what you meant, are you talking about the amount of injected memories per turn or about how many stored memories are too many? Sorry, English is not my mother language, sometimes I find hard to understand the correct meaning of some sentences.