GraQle — give your AI a memory of how your organisation actually works

Turn the context your organisation already has — codebases, documents, policies, decisions and workflows — into a persistent typed knowledge graph, so Claude Code, Cursor, Copilot and other agents reason over architecture, dependencies, prior lessons and evidence instead of re-reading disconnected files every session.

Models change. Tools change. Your architecture and institutional knowledge should not.

Terminal

Copy

pip install graqle

Website · Quickstart · How it works · Governed autonomy · Regulated deployments · Changelog · VS Code Extension

Why GraQle exists

Your organisation already knows the answer. It just can't hand it to an AI.

The refund threshold lives in a policy document. The reason you retain records for seven years is in an ADR nobody re-reads. The incident that moved validation into the service layer is in someone's head. The dependency that makes payments fragile is in the code. Every one of those is real knowledge — and none of it is connected to any of the others, so no model can reason across it.

Each AI session starts from zero and rebuilds a partial picture from whatever files fit in the context window. Then the window closes and the picture is gone.

GraQle builds that connection once, keeps it, and grows it.

• Relationships, not files. Assistants see documents and files. GraQle sees how a policy, a decision and the code that implements it relate — and what breaks when one of them changes.
• Memory that compounds. Policies, decisions, lessons and architecture become durable graph nodes instead of disappearing with a chat session. Teach it once; every future session starts from there.
• Model independence. Swap models, providers or IDEs without rebuilding the intelligence layer.

90-second proof — no code required

Point GraQle at policies, ADRs, runbooks or specs. Nothing else needed — this works on a folder with no code in it at all.

pip install graqle

# 1. Turn a folder of organisational documents into a typed graph
graq scan docs ./policies
# → 3 files → 12 nodes: 3 Document + 9 Section, linked by SECTION_OF

# 2. Teach it a rule that lives in nobody's file
graq learn knowledge "vendor DPA must be signed before any data access" --domain policy
# → extracts the entity "DPA", then SEMANTICALLY_RELATED-links the rule to
#   the vendor-onboarding document AND to its "Due diligence" section

# 3. Ask across the whole body of knowledge
graq run "what approval is needed for a large refund?"
# → answer + confidence + evidence trail + the exact sections consulted

# 4. Audit what the organisation has taught it
graq learned

Step 2 is the one that compounds, and the one no amount of prompt engineering replaces: it needs a persistent typed graph as the substrate. GraQle found where that rule belonged on its own — you never told it which document to attach it to.

Markdown, text, reStructuredText and AsciiDoc parse with the base install. PDF, DOCX, PPTX and XLSX need pip install "graqle[docs]" — without it those files are skipped and reported, never silently dropped.

The same graph, for code

Where a codebase is part of the picture, it enters the same graph and connects to the documents that govern it:

graq scan repo .
# → functions, classes, modules, imports, calls — architecture mapped in seconds

graq run "what breaks if I change the payment module?"
# → traces cross-file call + import chains, activates the relevant subgraph

graq impact payments.py        # blast radius before you touch anything

Software architecture is the deepest-mapped domain today — typed down to the function — and for engineering teams it is usually the fastest way to see the value. It is a wedge, not the boundary.

The compounding advantage

The first time you run GraQle, it knows what you gave it. After a month, it knows your patterns. After a year, it holds the policies, decisions, architectural lessons and document context your organisation accumulated — and activates the relevant ones on the work that is about to repeat an old mistake.

This is the part that survives model churn. When you switch provider or IDE, the graph is unchanged. You are not re-teaching a new model what your organisation knows; you are pointing a different model at intelligence you already own.

Own the intelligence your models and agents create. Enterprises can own their data and still lose the reasoning state accumulated inside external AI tools — the decisions, the corrections, the hard-won context. The graph is a local file you control.

How it works

1. Scan → Documents, policies, ADRs and specs become Document and Section nodes. Codebases enter the same graph through AST + dependency analysis (functions, classes, modules, imports, calls). One substrate, whatever the source.
2. Connect → Relationships become first-class: SECTION_OF, SEMANTICALLY_RELATED, IMPORTS, CALLS, DEFINES. Taught knowledge is auto-linked to the documents and code it concerns. This is what makes reasoning across sources possible.
3. Activate → A pre-reasoning layer scores each node for relevance, confidence and risk before the LLM runs, so the model receives the relevant subgraph instead of the whole repository.
4. Reason → Multiple agents debate. Outputs carry confidence, graph_health, active_nodes and evidence pointers. Debate is a reasoning mechanism, not a proof of truth: agents sharing a model family, a prompt template or a source document are correlated, so their agreement is not independent confirmation.
5. Validate → Answers below the confidence floor are refused rather than guessed.
6. Learn → Lessons, decisions and documents become durable graph knowledge that activates on future work.
7. Govern & commit → When agents move from reading to writing, gates intercept write-class operations, and decisions can be cryptographically committed.

The pipeline runs through five named phases — ANCHOR → ACTIVATE → GENERATE → VALIDATE → COMMIT. Each phase is governance-gated, evidence-attached and audit-logged.

API defaults: confidence_threshold=0.65 (refusal floor), gate_threshold=0.60 (gate-status floor). Both configurable per call.

Works with the AI tools you already use

You don't need another UI. GraQle runs inside the tools your team already has.

// .mcp/config.json
{ "graqle": { "command": "graq", "args": ["mcp", "serve"] } }

85 MCP tools — every operation Claude Code, Cursor, VS Code Copilot or Windsurf needs, exposed as a governed tool with confidence scores, evidence pointers and audit-trail entries. No prompt engineering, no glue code. (Each tool is also aliased kogni_* for backward compatibility.)

graq init              # detects your IDE, wires the tools, writes the project constitution

graq init renders one rulebook for every client — Claude Code → CLAUDE.md, OpenAI Codex → AGENTS.md, Cursor → .cursorrules, Windsurf → .windsurfrules — so editing it once keeps them all in sync.

Model independence

Anthropic · OpenAI · AWS Bedrock · Ollama · Gemini · Groq · DeepSeek · Together · Mistral · OpenRouter · Fireworks · Cohere · llama.cpp — plus any custom HTTP endpoint.

# graqle.yaml — smart task routing
backends:
  reasoning:  anthropic/claude-sonnet-4-6   # quality work
  embedding:  bedrock/titan-v2              # cheap + fast
  summaries:  ollama/llama3                 # local + free

Runs fully offline with Ollama or llama.cpp. Route different task types to different providers, or race two providers and take the first useful answer. The graph is the constant; the model is a swappable input.

What teams use it for

Trusted answers

Every reasoning result carries the signals that make it inspectable rather than magical: