AxiContext

AxiContext is an open source project context controller for AI coding agents.

It reads a local repository, writes a reviewable PROJECT_CONTEXT.md, stores structured context in a SQLite graph under .axicontext/, and exposes a local Agent Read API for tools that prefer JSON over Markdown.

The goal is simple: give agents a truthful project memory that can be regenerated, reviewed, queried, and checked for drift. The OSS build does not phone home to LatticeAG.

Project specs

• SPEC.md defines AxiContext OSS behavior.
• SPEC-BUILD.md defines the build phases and package layout.
• SPEC-AxiFence.md defines the AxiFence companion CLI.

What works in this repository

• axictx init creates .axicontext/config.toml and a starter PROJECT_CONTEXT.md.
• axictx sync ingests local repo signals, writes .axicontext/manifest.json, creates the SQLite graph, and regenerates PROJECT_CONTEXT.md.
• axictx drift compares the current repo against the saved manifest and can fail CI.
• axictx query returns keyword-ranked context excerpts with provenance.
• axictx serve starts the local HTTP Agent Read API, defaulting to 127.0.0.1:8787.
• @latticeag/axicontext-sdk provides a thin TypeScript client path for in-process and HTTP use.

AxiContext currently performs a full sync. Incremental sync, cloud sync, hosted dashboards, embeddings, and MCP are not claimed for v0.1. AxiFence is specified in this monorepo and is built as sibling packages in the later Fence phase.

Quickstart for users

Install from npm once packages are published:

npm install -g @latticeag/axicontext

Or run the CLI without a global install:

npx @latticeag/axicontext init

Use it inside a repository:

cd your-repo
axictx init
axictx sync
axictx drift
axictx query "how does authentication work?" --json
axictx serve

For CI:

axictx drift --ci --fail-on-drift

Quickstart for contributors

This repo uses Node.js 22 and pnpm.

corepack enable
pnpm install
pnpm build
pnpm test
pnpm typecheck

Run the local CLI after build:

pnpm --filter @latticeag/axicontext start -- init
pnpm --filter @latticeag/axicontext start -- sync
pnpm --filter @latticeag/axicontext start -- drift

Commands

Command	Description
axictx init	Scaffold .axicontext/config.toml and PROJECT_CONTEXT.md.
axictx doctor	Validate Node and local config.
axictx sync	Run the local adapters, update the manifest, write the SQLite graph, and regenerate PROJECT_CONTEXT.md.
axictx drift	Report context drift, with CI annotations when --ci is passed.
axictx query "..."	Search generated context excerpts and return matching provenance.
axictx serve	Start the loopback Agent Read API.
axictx status	Print manifest and context summary data.

How it fits together

flowchart LR
  Repo[Local repository] --> Sync[axictx sync]
  Sync --> Adapter[Git adapter]
  Adapter --> Graph[SQLite Context Graph]
  Graph --> Context[PROJECT_CONTEXT.md]
  Graph --> API[Agent Read API]
  Repo --> Drift[axictx drift]
  Drift --> Manifest[.axicontext/manifest.json]
  Agent[Agent or editor] --> Context
  Agent --> API

Loading

PROJECT_CONTEXT.md is for agents and editors that read files. The SQLite graph is the source for structured slices, query, and drift. The manifest records the generated state that CI can compare against later.

Agent integration

Point an agent at PROJECT_CONTEXT.md, or query the local API:

curl "http://127.0.0.1:8787/v1/context/slice?topic=authentication&max_tokens=2000"

For keyword query:

curl -X POST "http://127.0.0.1:8787/v1/context/query" \
  -H "content-type: application/json" \
  -d '{"question":"how does authentication work?","max_tokens":2000}'

See docs/agent-integration.md.

Monorepo layout

/
|-- packages/
|   |-- cli/            # @latticeag/axicontext, bin axictx
|   |-- core/           # config, sync, graph, drift, query
|   |-- sdk/            # TypeScript SDK
|   |-- server/         # local Agent Read API
|   |-- adapters-git/   # Git and filesystem source adapter
|   |-- parsers/        # shared repo analysis package, per SPEC-BUILD
|   |-- fence-core/     # AxiFence inference core, per SPEC-AxiFence
|   `-- fence/          # @latticeag/axi-fence CLI, per SPEC-AxiFence
|-- docs/
|-- testdata/
|   `-- fixtures/
|       `-- minimal-node-repo/
|-- SPEC.md
|-- SPEC-BUILD.md
`-- SPEC-AxiFence.md

Some package directories in the target layout may be introduced by later phase work. pnpm-workspace.yaml tracks the intended workspace entries so package creation does not require another metadata pass.

Documentation

• Install
• Config
• Agent integration
• CI
• AxiFence
• Security
• Schema

License

MIT. See LICENSE.