whatisgithub

What is gitlord?

yashneil75/gitlord — explained in plain English

Analysis updated 2026-05-18

46PythonAudience · developerComplexity · 3/5LicenseSetup · easy

In one sentence

A Python framework for AI agents that stores every conversation turn as a Git commit, making sessions inspectable, rewindable, and forkable.

Mindmap

mindmap
  root((GitLord))
    What it does
      Orchestrates AI agents
      Stores turns as commits
      Git-backed history
    Tech stack
      Python
      Git
      MCP and litellm
    Use cases
      Inspectable sessions
      Rewind checkpoints
      Fork conversations
    Audience
      Developers
      Agent builders
    Setup
      pip install
      CLI commands
      Optional extras

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Build an AI agent whose entire conversation history is stored as inspectable Git commits.

USE CASE 2

Rewind an agent session to an earlier checkpoint when something goes wrong.

USE CASE 3

Fork a session into a new branch to explore an alternate line of conversation.

USE CASE 4

Manage subagents whose work is tracked and linked back to a parent session via Git.

What is it built with?

PythonGitChromaDBMCPlitellm

How does it compare?

yashneil75/gitlordagricidaniel/goghbetta-tech/harness-sdd
Stars464646
LanguagePythonPythonPython
Setup difficultyeasymoderateeasy
Complexity3/53/52/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min
Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

So what is it?

GitLord is a Python framework for building and running AI agents that stores every part of a conversation using Git itself as the storage system. Instead of keeping a session's history in a database, each turn of a conversation, whether from a user, the agent, or a subagent, is written as its own Git commit. Because of that, the entire history of an agent session is inspectable with normal Git tools, can be rewound to any earlier point, and can be forked into a new branch of possibilities the same way a codebase can. Under the hood, each session lives on its own Git branch under a dedicated refs namespace, and any subagents spawned during that session get their own nested branches. The actual content of each turn is stored as a JSON file inside the commit's tree, while metadata like the turn number, its type, which agent produced it, and token counts are attached using Git commit trailers. When a subagent finishes its work, its result gets linked back to the parent session through a trailer as well. The project is organized into separate modules that each handle one concern: low level Git operations for building commits and trees, session lifecycle management for creating and resuming conversations, subagent management for spawning and collecting results, context assembly for deduplicating and summarizing history within a token budget, an MCP server integration layer for tool discovery and calling, a model router for translating tool schemas and handling retries across different LLM providers, and an optional vector index built on ChromaDB for retrieval. A command line tool ships alongside the library, letting a user run a session, view its turn history, inspect the branch structure, show the JSON content of a specific turn by its commit hash, rewind a session back to an earlier checkpoint, or diff two turns against each other. Installation is done through pip, with optional extras for MCP server support, LLM routing through litellm, and the ChromaDB vector index. The project is released under the MIT license.

Copy-paste prompts

Prompt 1
Show me how to set up a GitLord session and append a user turn using the Python API.
Prompt 2
Explain how GitLord stores turn metadata using Git commit trailers.
Prompt 3
Walk me through the gitlord CLI commands for viewing and rewinding a session's history.
Prompt 4
Help me wire up GitLord's optional ChromaDB extra for vector search over past turns.

Frequently asked questions

What is gitlord?

A Python framework for AI agents that stores every conversation turn as a Git commit, making sessions inspectable, rewindable, and forkable.

What language is gitlord written in?

Mainly Python. The stack also includes Python, Git, ChromaDB.

What license does gitlord use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is gitlord to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is gitlord for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.