Your Agent Keeps Forgetting Because You Keep Switching Models

Three weeks ago, a rapidly growing model on r/LocalLLaMA went unnamed. Users referred to it as ox-alpha, a clandestine release without an official claim. Benchmarking ensued, with users debating its origins, subsequently incorporating it into their agent stacks. On August 26th, the veil was lifted revealing that ox-alpha is in fact GLM-5.3-Flash (320B parameters, 18B active, MIT). The same month saw Qwen releasing five updates within a month, posing a maintenance challenge for those running AI agents.

Every model swap necessitates retuning prompts, retesting tool interactions, and discarding previously curated context, as the model's memory erodes. This leads to a weekly tax with weekly releases. Memory that survives beyond the model is a rare asset. To address this, Uteke was developed, betting that models are commodities while memory is the true asset.

Featuring a single local binary, SQLite, and a vector index with no server, any model can access the same memory using MCP or CLI. This ensures the agent's memory remains intact through model swaps.

Performance metrics demonstrate Uteke's effectiveness: 42ms average recall at 10,000 memories, with a Recall@5 of 0.946 on LongMemEval. To experience Uteke, users can execute the command "curl -sSL codecora.dev/uteke/install | sh". The blog post, "Your Agent Keeps Forgetting Because You Keep Switching Models" delves into release timelines, the churn tax, and architecture details.