explaingit

yoheinakajima/activegraph

Analysis updated 2026-06-24

96PythonAudience · developerComplexity · 4/5Setup · easy

TLDR

Python framework for long-running AI agent systems built on an event-sourced shared graph where behaviors react to typed object changes and runs can be forked or replayed.

Mindmap

mindmap
  root((activegraph))
    Inputs
      Graph objects and edges
      Behavior subscriptions
      LLM provider keys
    Outputs
      Append-only event log
      Forkable runs
      Replayable history
    Use Cases
      Build multi-agent workflows
      Audit and replay agent runs
      Fork experiments without re-running LLMs
    Tech Stack
      Python
      Postgres
      Prometheus
      Cypher patterns
Click or tap to explore — scroll the page freely

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 long-running multi-agent systems with a shared graph workspace

USE CASE 2

Replay or fork an agent run from any point in its history

USE CASE 3

Audit which behavior changed which object and why

USE CASE 4

Cache LLM calls across forked branches to cut model spend

What is it built with?

PythonPostgresPrometheus

How does it compare?

yoheinakajima/activegraphhuey1in/windsurfxkrishnaik06/gen-ai-with-deep-seek-r1
Stars969797
LanguagePythonPythonPython
Last pushed2025-02-05
MaintenanceStale
Setup difficultyeasymoderatemoderate
Complexity4/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 · 30min

pip install plus Python 3.11 is enough for the offline quickstart, LLM provider keys and Postgres are optional extras.

In plain English

Active Graph is a Python framework for building long-running AI agent systems where every change is recorded and can be replayed later. Instead of having agents talk directly to each other, the framework sets up a shared workspace, called a graph, that holds objects and the typed connections between them. Pieces of code called behaviors watch the graph and react when something they care about changes. The README describes this as a group of agents sharing a workspace where everyone can see what was changed, by whom, and why. You install it with pip install activegraph and run activegraph quickstart to see a bundled example, called the Diligence pack, work against recorded fixtures. No API key is needed for that first run, and the output is meant to be the same every time. There is also an interactive version of the quickstart that scaffolds a behavior, runs it, and shows the fork-and-diff workflow. Optional installs add LLM providers (Anthropic, OpenAI), Postgres storage, or Prometheus metrics. Python 3.11 or newer is required. The core idea is event sourcing. Every mutation to the graph becomes an event in an append-only log, and the current state of the graph is treated as a projection of that log. Because the history is complete, a run can be resumed, forked at any point, or compared structurally against another run. The framework reuses cached LLM responses across the shared prefix of a fork, so branching does not trigger new model calls for work that was already done. Behaviors can be plain functions, classes, LLM-backed, or attached to typed edges between objects. They subscribe by event type, by a predicate, or by a subset of Cypher patterns for matching shapes in the graph. Failures of a behavior are themselves logged as events rather than raised as exceptions, so the audit trail stays complete.

Copy-paste prompts

Prompt 1
Run the activegraph quickstart Diligence pack and explain what the fixture output is showing me
Prompt 2
Write a custom behavior in activegraph that watches edges of type owes_money and triggers an LLM follow-up
Prompt 3
Show how event sourcing in activegraph lets me fork a run after step 12 without re-paying for the earlier LLM calls
Prompt 4
Compare activegraph behaviors that subscribe by event type, predicate, and Cypher pattern with a small example for each

Frequently asked questions

What is activegraph?

Python framework for long-running AI agent systems built on an event-sourced shared graph where behaviors react to typed object changes and runs can be forked or replayed.

What language is activegraph written in?

Mainly Python. The stack also includes Python, Postgres, Prometheus.

How hard is activegraph to set up?

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

Who is activegraph for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.