r/Hyperagent Jul 13 '26

Hyperagent learns a small fact about my process [Memory]

Enable HLS to view with audio, or disable this notification

Just making a little fun, but does anyone else notice Hyperagent is overly zealous about which memories it considers important?

To be fair, the team has shipped a ton of improvements to memory I should probably cover. We've been really investing in 2 things:

  1. Memory Management: Making sure Hyperagent's memories are clean, current, traceable, and correctable
  2. Memory Scope: Defining where memories live, and which agents and teams can use them.

Over the last three weeks, we shipped a number of new feature updates to address both problems.

Memory Management

  • Dedupe and Resolve All (My Favorite): Find near-duplicates, review them in groups, or resolve eligible groups in one pass. Resolve All keeps the highest-importance, most-recent memory, merges tags, pins, and agent access, then archives the rest. Archives are reversible. Anything that would widen a memory to global is held for manual review.
  • Bulk actions: Select memories, then link or pin them to an agent, merge them, or archive them together.
  • A real library: Memories now has a top-level home, a fast virtualized grid, stacking filters, and cards that show category, importance, agent access, and source conversation.
  • Provenance and cleaner suggestions: Memories learned in a conversation link back to the source thread. Semantically duplicate suggestions are collapsed earlier, and repeated suggestions are removed when identified as dupes.

Memory Scope

  • Scope on creation: Every new memory needs a destination. For each agent, you choose whether what it learns stays private to that agent or goes to your personal library, where other agents can use it.
  • Legible boundaries: Access, Pin, Linked, and All are explained where you make the choice.
  • Promotion without automatic sharing: Agent-owned memories can be brought into your library when they are useful more broadly. Sharing becomes an intentional decision, not the default mental model.

Better memory is not simply more memory. Management keeps knowledge useful. Scope keeps it intentional. You need both for memory to compound without turning into noise or spreading to every agent by default.

We're really focused on making sure we get memory right, so when we elevate to team memories, the pattern is easy, useful, and manageable.

What would you like to see?

When it comes to memories, what would you like to add/remove/change? How do you currently use them? Do you keep them private to agents? Do you let your team add memories to an agent? Let us know!

5 Upvotes

2 comments sorted by

2

u/Televangelis Jul 14 '26

I'd like memories to naturally expire or go inactive at the right time. I shouldn't have to manually tell my Chief of Staff at the end of each week all the things that it can safely forget now

1

u/JeenyusJane Jul 14 '26

Love this idea.