Interop · Para: dev

Teams want to reuse the index in other tools and CI, but a code graph trapped in one tool cannot be exported or imported.

Export to SCIP/LSIF for interop or to the native full-fidelity AIndex Graph (.aig), and import external indexes back.

$ aindex graph export --out graph.aig --json && aindex scip export --out index.scip --json

scip_export
aig_export
import_summary

Comando

Code Graph Export

Export the code graph as SCIP/LSIF or native full-fidelity AIndex Graph (.aig).

CLI

aindex graph export --out graph.aig --json && aindex scip export --out index.scip --json

MCP

status detail=features

Example output

Lo que el Cerebro hace automáticamente

The customer can see what problem this workflow solves and how to prove it.

On demand

This workflow is not auto-triggered by the Brain yet; run it explicitly with the command above or its MCP action.

Not measuredPrueba

No medidoNo public benchmark covers this workflow yet — the proof is the live command output above, not a positioning claim.

Source—

AvailableRuntime feature status · 0 evidence item(s). Metadata-only; no raw source included.

Tier requerido

Exports the index as SCIP/LSIF or native .aig so the code graph is reusable in other tools and CI.

Free · €0

Visible as a product workflow and pilot proof target; do not treat as fully shipped enterprise automation yet.

Buyer grade

Names the parity workflow and proof path without claiming full Sourcegraph-class depth.

Visible in

This workflow stays discoverable across setup, CLI, MCP status, docs, dashboard and pricing — never a hidden command.

Feature visibility checklist

This keeps grouped product names discoverable without claiming a separate maturity level from the underlying workflow.

Code Graph ExportFoundation

SCIP/LSIF interop and native full-fidelity .aig export/import keep the graph portable.

Interop

SCIP + native .aig