A Flight Recorder
for Your Mind

Pilots use flight recorders because memory fails under pressure. We built Metronix on the same premise: if an agent thinks, acts, breaks, or hands work off, you should be able to reconstruct what happened and recover cleanly.

Memory replay in motion.

Watch Metronix preserve agent state, retrieve context, and make memory inspectable as work moves forward.

Bring memory online with one command.

Bootstrap Metronix locally or into your deployment workflow, then wire it to the agents that need durable state.

Persistent Memory

Store operational memory outside the prompt: decisions, tool outputs, task progress, facts, artifacts, and handoffs that agents need across long-running workflows.

Structured State

Model agent state explicitly instead of burying it inside chat history. Sessions, tasks, approvals, checkpoints, and workflow metadata stay queryable and durable.

Permission Boundaries

Apply RBAC and policy checks to memory reads, writes, and handoffs so agents do not inherit access they were never supposed to have.

Agent-to-Agent Context Sharing

Pass context between planners, reviewers, operators, and domain agents without flattening everything into one giant prompt-shaped hairball.

Recovery Checkpoints

Resume work after a crash, timeout, or bad model decision using replayable checkpoints instead of asking the agent to please remember what it was doing.

Auditability

Track who wrote memory, which policy allowed it, what changed, and how a later action was derived. Postmortems become possible instead of theatrical.

• ›Prompts as the temporary source of truth
• ›Chat history as accidental state storage
• ›Vector hits without permission semantics
• ›No replayable checkpoints after failure
• ›No durable handoff between specialized agents
• ›Weak forensic trail when something goes wrong

• ›Persistent memory across sessions and workflows
• ›Explicit task state and durable checkpoints
• ›Permission boundaries on reads, writes, and handoffs
• ›Agent-to-agent context sharing with provenance
• ›Audit logs for recovery and postmortems
• ›Self-hosted memory layer for production agents

What Breaks Without an Actual Memory Layer

MemoryAgentBench end-to-end accuracy, with Metronix also leading LoCoMo at 52.8% under the same evaluation harness.

Open Source Community Edition

The adoption loop should start with developers, not procurement. Community Edition makes the core memory layer easy to run, inspect, fork, self-host, and plug into existing agent stacks without asking permission from a sales team.

Ship features people can star, fork, benchmark, and argue about on the internet

Every meaningful release can become a GitHub release, technical post, thread, forum post, and demo clip. That flywheel works a lot better when the homepage makes the open-source posture obvious instead of hiding it behind packaging.

Notes for people building agents in public

Architecture notes, benchmark methodology, and product decisions with enough detail to be useful instead of merely ornamental.

Join the Builders Fixing Agent Memory

Clone it, run it, break it, improve it. The goal is a project developers actually want to contribute to, not another brochure pretending to be a platform.