pickfit

BrowseLocal AI tools

Graphiti Local

Local-first temporal knowledge graph for agent memory with human-approved updates.

Use it

Before you install: known vulnerabilities

pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.

  • pypi:filelock 3.32.7 filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files (GHSA-v4x8-3wr5-3wq8, high, fixed in 4.2.1)

Linux x86_64

  1. Install and demo via uvx --from git+https://github.com/renezander030/graphiti-local kg-demo

    uvx --from git+https://github.com/renezander030/graphiti-local kg-demo
  2. Clone repo for local CLI tests

    git clone https://github.com/renezander030/graphiti-local.git
  3. Install dependencies with uv sync --frozen and verify ingest dry-run

    cd graphiti-local && uv sync --frozen 2>&1 && export GRAPHITI_LOCAL_CONFIG="$PWD/config/ollama.example.yaml" && export KG_WORKSPACE_DIR="/tmp/kgtest2/workspace" && printf '{"name":"Test2","body":"Graphiti Local is awesome.","domain":"example"}\n' > /tmp/test2.jsonl && uv run --frozen kg-ingest /tmp/test2.jsonl

Check that it works

cd graphiti-local && uv run --frozen kg --version 2>&1

The output should contain “kg 0.10.0”.

First thing to try

cd graphiti-local && uv sync --frozen 2>&1 && export GRAPHITI_LOCAL_CONFIG="$PWD/config/ollama.example.yaml" && export KG_WORKSPACE_DIR="/tmp/kgtest2/workspace" && printf '{"name":"Test2","body":"Graphiti Local is awesome.","domain":"example"}\n' > /tmp/test2.jsonl && uv run --frozen kg-ingest /tmp/

Run uvx --from git+https://github.com/renezander030/graphiti-local kg-demo to try a question against the bundled sample graph.

What it does

  • Look up project decisions through MCP tools
    How to use it
    1. Run uvx --from git+https://github.com/renezander030/graphiti-local kg-demo to query the sample graph.
    2. Read the returned facts, such as which database a project uses.
    Tested
  • Approve and apply queued graph updates
    Not tested
  • Build a knowledge graph from your own text
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 3 features work
  4. Needs the network

Good for

  • retrieve project decisions through read-only MCP tools or kg CLI
  • answer a question against shipped synthetic graph
  • review and approve proposed graph updates

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Needed the network
  • Checked on 31 Oct 2026
  • Version 0.10.0

Differences the test machine hit

  • README: kg ask reading demo graph.ladybug works with current install
    In the test: Demo file version 49 incompatible with installed ladybug storage version 43 – kg ask fails with Runtime exception
  • README: kg-workspace drain --apply lands proposals
    In the test: Without Ollama LLM/embedder, drain --apply and kg-ingest --apply fail with NodeNotFoundError; dry-run planning works offline

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.