Memory ops via the agent path over-delegate + hang; profile-write returns 0-char output (persistence unconfirmed)
Evidence
- g6-24 "store my Q3 OKR" DONE@218s: called
manage_profile_memory@12s — but the tool_result was {"elapsed_ms":0,"output_chars":0} (0-char output) — so the write's persistence is unconfirmed. It also redundantly spawned a sub-agent (0 sub tool calls).
- g6-25 "ingest into long-term memory tree + confirm what got indexed" (same thread) INCOMPLETE@299.8s: 2 serial spawns,
retrieve_memory@288s, empty reply. Never completed.
- g6-27 "reconcile two overlapping notes + forget stale" INCOMPLETE@280s: 3 serial spawns, mid-turn
manage_profile_memory@140s with no confirmation, empty reply — may have partially mutated memory.
- g6-probe (fresh thread) "what is my Q3 OKR": a trivial single-fact recall spawned a sub-agent@8.8s (over-delegation) and hung → could not even confirm the g6-24 write persisted.
Ask
The memory subsystem is effectively read-broken via the agent path: recall/ingest/reconcile over-delegate and hang, and the one write that returned gives a 0-char result. (1) Memory recall must be a direct tool call, not a sub-agent spawn (relates to #4744 over-delegation). (2) Investigate why manage_profile_memory returns output_chars:0 and whether the write actually persists. (3) Ensure ingest/reconcile complete + confirm. Highest-value area — memory is the product's core.
Memory ops via the agent path over-delegate + hang; profile-write returns 0-char output (persistence unconfirmed)
Evidence
manage_profile_memory@12s— but the tool_result was{"elapsed_ms":0,"output_chars":0}(0-char output) — so the write's persistence is unconfirmed. It also redundantly spawned a sub-agent (0 sub tool calls).retrieve_memory@288s, empty reply. Never completed.manage_profile_memory@140swith no confirmation, empty reply — may have partially mutated memory.Ask
The memory subsystem is effectively read-broken via the agent path: recall/ingest/reconcile over-delegate and hang, and the one write that returned gives a 0-char result. (1) Memory recall must be a direct tool call, not a sub-agent spawn (relates to #4744 over-delegation). (2) Investigate why
manage_profile_memoryreturnsoutput_chars:0and whether the write actually persists. (3) Ensure ingest/reconcile complete + confirm. Highest-value area — memory is the product's core.