Let Jev pick the memories, not the answer

More like this

• 

  tamara

  @tamarajtran

  found the perfect use case for @typesafeai Jev: instant compaction in 2026, why is compaction still a summarization prompt? Jev can make it instant by scoring every tool call and dropping what’s irrelevant

  

  X·Context and memory

  Pick

  Instant compaction for Claude

• 

  Baris Terzioglu

  @terzioglubrs

  Agent memory is usually just an append-only Markdown file that grows forever, and most frameworks load the whole thing into context on every single run. That has been bothering me for a while, but never quite enough to fix it for our agents. Jev feels like it might be a low effort patch to this, by simply scoring each memory against the prompt first, then load only the relevant bits for that specific request.

  

  X·Context and memory

  Agent memory is usually one growing file

• 

  Coach Shweta Bajaj

  @shwetabjaj

  Jev Skill Suggestion for Claude Code is a smart idea. Instead of loading every skill into context, Jev decides which one is actually relevant and injects only that. My takeaway: better context hygiene, less clutter, and potentially more efficient agent workflows. @typesafeai @vercel

  

  X·Context and memory

  Skill suggestion injects one skill