Back to directory

GitLord

A Python library that stores an AI agent's execution history as Git commits, so every prompt, response and tool call is a version-controlled, inspectable, replayable and forkable event.

GitLord

GitLord represents an AI agent's execution history as a Git repository. Each turn, such as a user prompt, an assistant response, a tool call, a tool result or a subagent result, becomes a commit on a branch under refs/agents/, so Git primitives such as branches, diffs and refs stand in for agent timelines, behavior changes and agent identity.

It lets a failed run be rewound to an earlier checkpoint and retried on a new branch, lets alternative approaches be explored as separate forks with their own history, and lets subagents run on their own branches with results passed back to the parent through Git trailers. History can be queried by turn, agent, token count, error or semantic similarity. A log repository holds turn history and metadata separately from the workspace repository holding the agent's actual files.

It is a Python package, installable with optional MCP server, LiteLLM routing and ChromaDB vector-index support.

More in AI evals

See all 269
  • Provenance gate

    github.com

    A deterministic authorization gateway that sits between an AI agent and its tools, tracing where each parameter of a side-effect call came from, and blocking the call or asking a human when the source does not check out.

  • JevBench

    benchmarkheaven.com

    A reproducible benchmark from Benchmark Heaven that ranks Jev-class typed decision models on intelligence, calibration, speed, and cost, with a published harness, scoring rules, and results.

  • A co-evolutionary adversarial red-teaming tool for AI agents that uses quality-diversity evolutionary search to autonomously breed edge-case scenarios, testing whether an agent with tool access can be made to hallucinate, deadlock or leak funds.