`YourMemory`: decay-based AI memory MCP with graph retrieval

Instead of keeping every note forever, it decays weak memories and reinforces recalled ones. That cuts context bloat, lifts retrieval quality, and looks worth testing for long-running agents.

[ KEY POINTS ]

Uses the Ebbinghaus forgetting curve: each recall strengthens a memory, while unused entries decay and get pruned. Memory hygiene is built into retrieval, not left to manual cleanup.
Adds a graph layer on top of the vector store to catch logical neighbors that pure semantic search misses. This targets a real failure mode in agent memory stacks.
On LoCoMo, it reports 52% Recall@5 and about 84% less token waste versus stateless vector stores. If those numbers hold, the tradeoff is strong.
Runs as a local-first MCP server on DuckDB, which keeps setup lightweight and ownership local. Better fit for persistent project agents than chat-session memory hacks.

Originalgithub.com/sachitrafa/YourMemoryRead original →

// related

#0001
#0001Agents & tools Google AI Forum24 minutes ago
`Antigravity CLI`: enable auto-accept via `/permissions`
40radar
Antigravity CLICoding agent CLI — supports auto-accept permissions
A small CLI workflow removes repeated confirmation prompts. Useful for trusted low-risk tasks, but risky around shell, file, or deployment actions.
- Run /permissions inside Antigravity CLI, then choose the auto-accept option with arrow keys and Enter.
- The behavior is close to Gemini CLI YOLO mode: fewer prompts, faster loops, weaker manual guardrails.
- Best fit is contained cleanup or repetitive edits. Keep approvals on for destructive commands, secrets, and deploys.
Source: discuss.ai.google.dev/t/help-how-to-enable-yolo-mode-or-Read original →
FIG-0011:1
40radar
FIG-0011:1
#0002
#0002Agents & tools Google AI Forum30 minutes ago
`Antigravity` Remote SSH crashes on non-AVX2 QEMU VPS
50radar
AntigravityAI coding IDE — Google's agentic development environment
Remote coding breaks on cheap virtual CPUs exposing only SSE/SSE2. Check CPU flags before moving agent workflows to budget VPS boxes.
- Exit Code 132 plus Linux invalid opcode points to SIGILL, matching a binary built with unsupported CPU instructions.
- The affected remote server exposes SSE/SSE2 only, with no AVX or AVX2; VS Code and Cursor work on the same host.
- Bundled securecoder also lacks out/extension.js, so even after the server issue there is a packaging bug to fix.
Source: discuss.ai.google.dev/t/bug-report-antigravity-server-crRead original →
FIG-0021:1
50radar
FIG-0021:1
#0003
#0003Agents & tools Google AI Forum42 minutes ago
`Antigravity IDE` 2.0.1 macOS report: fatal DI crash disables agents and marketplace
60radar
Antigravity IDEAI coding IDE — built-in Google agent workflows
A clean install can still hit aae depends on UNKNOWN service agentSessions. Treat the 2.0 update as risky on macOS until a fix lands.
- Environment is specific: Antigravity IDE 2.0.1, VSCode OSS 1.107.0, macOS Darwin arm64 25.5.0 on Apple M4 Max.
- Core failure is dependency injection: aae cannot resolve agentSessions, so the AI Agent Manager never starts.
- Marketplace also breaks with open-vsx.org extension manifest fetches returning 429, leaving plugins unavailable.
- Cache wipes across ~/Library/Application Support/Antigravity IDE, ~/.antigravity, and cache folders did not recover it.
Source: discuss.ai.google.dev/t/bug-fatal-di-crash-on-clean-instRead original →
FIG-0031:1
60radar
FIG-0031:1

`YourMemory`: decay-based AI memory MCP with graph retrieval

// related

`Antigravity CLI`: enable auto-accept via `/permissions`

`Antigravity` Remote SSH crashes on non-AVX2 QEMU VPS

`Antigravity IDE` 2.0.1 macOS report: fatal DI crash disables agents and marketplace