Discover task context
AIPI searches local workspace files, AST symbols, K Map contracts, findings, and runtime evidence—then traces the smallest relevant chain.
caller → route → handler → schema → testAIPI gives coding agents the exact implementation chain, bounded context, and verification loop they need to change APIs without guessing.
userId: numbercallerpatient_id: stringhandlerFrontend calls, backend handlers, schemas, and tests live in different places.
Logs say what failed. They rarely identify the responsible contract and code path.
“Looks fixed” is not a revision-linked replay, diff, or proof receipt.
AIPI is the evidence layer beside your agent—not another editor, chat, or giant context window.
AIPI searches local workspace files, AST symbols, K Map contracts, findings, and runtime evidence—then traces the smallest relevant chain.
caller → route → handler → schema → testThe agent receives a compact, revision-aware context pack instead of an unbounded repository dump. You keep the coding agent you already use.
620 / 2,400 tokensAIPI runs the saved replay, contract diff, and linked checks, then records an immutable proof receipt against the active Git revision.
verified @ 8f3a1cK Maps connect every API contract to the code and evidence around it. Open a source reference in your IDE, inspect a schema drift, or jump straight into a replay.
Keep the AIPI workspace open as a toggleable side panel. Discover, hand off, and verify in the same task.
A narrow, native side-panel for task context, K Maps, agent handoff, and verification.
Installation guideThe same tool contract works without the UI. Your editor remains the control plane.
Browse MCP toolsThe companion binds to loopback, redacts sensitive evidence, and serves MCP over local stdio. Cloud sync is opt-in and designed for shared contract metadata—not captured payload bodies.
Read the data boundaryAIPI detects your project structure, writes project-local MCP configuration, and starts or reuses the local companion.
# Run inside the repository you want AIPI to understand
$ npx @vmise/aipi-companion@latest initInstall the local companion and connect your first repository.
Understand callers, routes, schemas, tests, and evidence as one graph.
Use AIPI from Codex, Cursor, VS Code, or another MCP client.
Learn exactly what stays local and what team sync can store.
Create a cloud account to follow team sync, shared environments, CI receipts, and governance features as they become available. Local AIPI stays usable without an account.