You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(memory): legible capacity errors, list action, and full-store education
The project-memory budget check silently added a 3-char entry delimiter that
the rejection message never disclosed, so a near-full store reported e.g.
"2085/2200, entry (113) exceeds" — math that reads as satisfiable (2085+113<2200)
but isn't. With no visibility into the true ceiling or what was stored, the agent
could only blind-shrink the entry and loop until interrupted.
- project_memory: delimiter-aware accounting; rejections now report exact free
chars, the entry's real cost (content + separator), used/limit, and a compact
inventory (index, size, preview) so the next remove/replace is guided. Add
status() and capacity(); flag capacity failures via MemoryOpResult.full.
- Memory tool: new read-only `list` action for mid-session introspection; on a
full-store rejection, append a plain-language explanation (nothing lost, task
continues, how to free space) to the user-facing tool card.
- Raise limits MEMORY 2200->5000, USER 1375->2500 (within the 8 KB injection budget).
- /memory: show per-store capacity and a "nearly full" guidance panel at >=85%.
- memory.md: best-effort housekeeping guidance — don't loop on rejection.
0 commit comments