Set up
Skills are installed by placing their folder where your agent loads skills.
The download comes from github.com/CodexOperator/AGI itself, not from our server, so what you get is exactly what its author published.
Install instructions come from the README
README
synced Oct 26, 2026agi — Advanced Graph Interface
A unified repository housing graph algorithms and the research loop harness that operates on them. The loop dogfoods by treating the agi codebase itself as graph nodes — researching, mapping, and incrementally evolving its own algorithms and harness.
What's inside
| Path | Purpose |
|---|---|
extensions/agi/ | Research loop engine — driver, bin/ scripts (snapshot, render, dispatch, heal, zoom, cli), hooks, lib, src/, tests |
extensions/agi/src/graph_core/ | Graph framework — node, edge, types, persistence (filesystem + sqlite), loader, db_loader, cache |
extensions/agi/src/agi_algos/ | Graph algorithms — graph_builder, query_engine, benchmark, pi_tree_adapter, asciirender |
extensions/agi/src/renderers/ | Renderers — ascii (project graph), mermaid, git_diff, representation |
extensions/agi/src/embeddings/ | Embedding stack — node2vec, projection, similarity (gensim + UMAP) |
extensions/agi/src/schema_registry/ | Schema governance — fingerprint, active_set, cascade, validation, dsl, meta_nodes, loader |
extensions/agi-bridge/ | TypeScript pi extension — hooks before_agent_start, refreshes INJECTION.md per agent turn |
skills/agi/SKILL.md | The Claude/agent skill that drives loop iterations |
TODO.md | Persistent register of deferred work (DB-only state migration, ASCII renderer unification, metric overhaul, …) |
QUICKSTART.md | Start here on a new machine. Bootstrap from zero: clone, deps, CLI/skill/hook install, the safety rail, one iteration of the loop. |
HANDOFF.md | The current session's state and next action — one section, always current. Replaced wholesale each session; earlier ones are in the grid. |
GOALS.md | What the project is committed to. Rendered from .agi/nodes/goal/ — edit the goal node, never this file. The project tracker. |
⚠️ Before running the loop in any project, read
QUICKSTART.md§1. A stale project-local.agi/bin/snapshot-build-site.pycan silently delete that project's entire node corpus — confirmed, 29,264 files. That section has the one-line check.
TODO.mdis retired (build:TODO.mdisstatus: deprecated); it is an archive of how defects were found and closed, not a work queue.
The working rule
Every change starts as a node in the graph and is built back into the engine. The graph is the sequence of decisions; this repo is what falls out of it. A fix applied only as a file edit carries no reasoning, no parent, and nothing a later reader can argue with — so find the node first, write one if the reasoning is new, and let the code follow.
Two rules that make that workable, and both are easy to get wrong:
- A version is a grid commit, not a second node file. Update a node in place; the git grid records one version per change on
refs/grid/node/<mint-id>. Never mint a@v2file or asupersedes:pair — that duplicates history the grid already has. - Two identifiers, two jobs. A node's mint id is assigned once and never changes; it is what grid refs and provenance key on. Its address is derived and expected to change whenever the node is retagged or regrouped. Never key durable history on the address.
Layout
The graph lives outside the engine, one level inside the project, with the engine clone underneath it — <project>/<project>-tree/agi:
fantasia/
fantasia-tree/ the graph repo (GOALS.md, agi-tree.config.json, nodes/)
agi/ gitignored clone of this repo
An engine checkout therefore never contains a graph, which is why this repo needs no tree-related gitignore. The one exception is this repo's own pair, where both hops are symlinks so agi/agi-tree/agi resolves back here — an engine edit made from inside the tree has to land in the real checkout, not a copy nobody ships.
Companion repositories
CodexOperator/agi-tree— graph data: a live research project instance whose nodes correspond to actual files and functions in this repo.
Pi extension auto-discovery
This repo declares pi extensions and skills in the top-level package.json (pi.extensions: ["./extensions"], pi.skills: ["./skills"]). Pi auto-discovers extensions/agi/ and extensions/agi-bridge/ when run from any directory rooted under this repo.
CLI
agi on PATH is a symlink to extensions/agi/driver.sh. Run it from anywhere inside a project — it walks up for agi-tree.config.json to find the graph repo.