Danny Avila 24311a11d4 🩹 fix: Address Codex re-review on memory capability (round 6) ... - Fix a P1 regression from the prior round: the execution-context agent keeps the raw 'memory' capability marker (not the expanded set_memory/delete_memory names), so the opt-in check now matches the marker. This restores memory writes/deletes AND avoids hijacking an MCP tool that merely shares the set_memory/delete_memory name (api/app/clients/tools/util/handleTools.js). - Count repeated set_memory writes to the same key as replacements, not additions, against tokenLimit — set_memory upserts, so a same-key rewrite swaps its prior token contribution instead of double-counting (packages/api/src/agents/memory.ts) + test. - Gate the memory badge, tools dropdown, and agent-builder toggle on the full memory write permissions (USE+CREATE+UPDATE) via a shared useHasMemoryAccess hook, so a read-only-memory role no longer sees an enabled Memory control the backend would refuse to wire up.		2026-06-20 23:57:07 -04:00
..
clients	🩹 fix: Address Codex re-review on memory capability (round 6)	2026-06-20 23:57:07 -04:00
index.js	🛠️ fix: Optionally add OpenID Sig. Algo. from Server Discovery (#5398)	2025-01-21 21:49:27 -05:00