[!] TOPIC ARCHIVE // #AGENT-MEMORY
#Agent-Memory
All 19 guides, operator dossiers, and signals tagged with #Agent-Memory.
when the note outranks the calendar
A Qwen3 memory study, Fabric’s loopback server default, and Screenpipe event triggers all put source authority and workflow control under pressure.
agent records
A signature, a task journal, and a persistent workspace answer different questions. Only one says who is answerable for the work.
memory needs a boundary
Agent memory is becoming a system of record: what survives a session, who can inspect it, and where an agent must stop.
query surfaces, agent servers, memory layers
Tabularis, Moltis, and TencentDB Agent Memory push agent work into inspectable database, runtime, and memory infrastructure.
policy lines, payment rails, executable traces
Anthropic drew a colder line around open weights, Tilde Pay put agent spending behind KYC and payment rails, and workflow papers turned successful traces into reusable executable skills.
timers, transcripts, graphs
agent work got pushed into slower, more inspectable shapes: GitHub cooldowns, production-conversation fixes, and graph-based code context.
accounts, recordings, handoffs
Trusty Squire moves signup and API-key custody into an MCP server, Record & Replay turns human desktop work into SKILL files, and Cactus v2 exposes the local/cloud handoff threshold.
bills, gates, repo memory
OpenAI put agent work into priced APIs and a split Work surface, Wiz exposed a coding-agent approval gap, and local tools moved codebase memory into repo artifacts.
priced runs, reviewed traces, veto memory
Databricks priced coding-agent harnesses, AgentLens scored full trajectories, and new state tools turned memory into vetoes and receipts.
hidden marks, owned memory, parser risk
Claude Code prompt marks, host-owned agent memory, and a protobuf parser bug pushed today’s control story into the small layers.
scaffolds, decisions, receipts
agent scaffolding is moving into model training, repo-local decision contracts, and signed or gated world-state checks.
rooms, budgets, receipts
agent work is turning into local ops plumbing: shared rooms for coordination, active context budgets, and inspectable run receipts.
agent maintenance layer
repo guidance gets tested, coding agents get redundant, and shared memory gets judged by access control and deletion instead of recall alone.
expertise moved upstream
Anthropic and Kaggle measured the new coding-agent handoff, dropped exposed silent instruction loss, and memory systems started shipping with benchmarks and receipts.
agent maintenance layer
Shared agent memory, skill preflight scanners, and execution-repair research all pointed at the same shift: useful agents now need maintenance infrastructure.
context drift
Hyper turns company context into permissioned agent memory, a dependence paper shows emotional support leaking through task chat, and new safety papers split certification from shaky runtime interrupts.
agent work got useful where it slowed down
today’s useful agent work had friction in it: a correctable personal model, coding workflows that keep the human thinking, and tool catalogs that load late instead of eating context.
stateful work
Anthropic packaged role work into Claude plugins, while new papers framed long-term memory as governed state and workplace agents as delegated-task systems.
governed interfaces
Cloudflare's enterprise MCP architecture, MinIO's abrupt repo shutdown and fork, and YourMemory's decay-based agent memory all point to one shift: the control layer is getting explicit.