The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Fava Trails
FAVA Trails — Git-native, curated memory for AI agents via MCP. Draft isolation, promotion gate, thought lifecycle hooks, memory curation protocols, supersession chains.
Install
pip install fava-trailsInstall command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →FAVA Trails
Federated Agents Versioned Audit Trail, an open-source agent memory system by Machine Wisdom AI.
FAVA Trails helps agents share reviewed decisions across sessions and environments. Agents save drafts, submit them for review, and recall approved records with a history of what changed. Records are Markdown files with YAML frontmatter in a Git-compatible repository you control, exposed through MCP tools.
Get started · Product website · Two-agent case study · Machine Wisdom AI's engineering writing
New in 0.8: Jev at the memory boundary
An agent can write a plausible conclusion in seconds. Deciding whether the next agent should inherit it deserves a separate step. FAVA Trails 0.8 uses TypeSafe Jev through OpenRouter Decisions as its default Trust Gate for new installs: one typed question, an explicit approval threshold, and a review record you can inspect.
Jev scores the candidate against the supplied memory policy. FAVA applies the threshold, records the returned model and probability, and makes approved records available through governed recall. Failed reviews stop promotion. Your records remain versioned Markdown in your own repository.
Read the 0.8.0 release notes for the calibration results, existing-install configuration, and data-egress details. Review is a quality control step; it does not establish that a claim is true.
Why we built FAVA Trails
An observation from one agent can become an assumption for the next. Machine Wisdom AI built FAVA Trails to give that transition an explicit review boundary: saving a thought does not make it accepted knowledge, and an approved correction preserves the record it replaces. The result is a shared history that agents can query and operators can inspect.
This is useful when several agents reuse decisions, when work continues across sessions, or when you need to trace why a remembered conclusion changed. Review remains a quality control step; it does not independently verify the facts. The governed recall guide describes the identity and visibility boundaries.
Governed recall
Release status: The governed visibility model below ships in FAVA Trails 0.7.0, published to PyPI and GitHub on September 13, 2026. Older 0.6.0 does not include these governed-read isolation / MCP registration fixes. Confirm what you loaded with
fava-trails version— see docs/runtime-and-upgrade.md.
FAVA is the governed institutional record for decisions, observations, validation,
and lineage. It is not the operational working-context store. Default recall
and get_thought expose current approved records only. Explicit mode="authoring"
retrieves only the server-configured agent's draft/proposed records; operator-only
mode="history" selects lifecycle statuses and superseded records. Neither a
namespace nor a supplied agent_id grants access. See governed-recall.md
for identity setup, compatibility, approval provenance, and interrupted-write recovery.
Similar plugs
Reverse engineer anything with agents, from app behavior down to native binaries.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)
A cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode, OpenClaw, Grok Build & Hermes Agent. Only official website: ccswitch.io