Give every agentthe whole system.
Give AI agents the same engineering context your team explores in UIGraph. Make it available in your coding tools through MCP, or ask questions directly in UIGraph.
$ uigraph-agents artifacts sync
Scanning declared artifacts...
✗ api/openapi.yaml drifted — 2 endpoints undocumented
✗ docs/checkout.md drifted — references a removed field
Regenerating drifted artifacts...
✓ api/openapi.yaml updated
✓ docs/checkout.md updated
✓ 2 artifacts synced · 0 source files touched
Two agents. Clear authority for each.
Artifacts agent
Keep documentation true to the code.
uigraph-agents artifacts sync finds drift and updates the specs, diagrams, and docs declared in your UIGraph configuration.
Writes documentation artifacts. Never source code.
Impact agent
Review the blast radius before merge.
uigraph-agents impact analyzes a commit range and reports affected services, APIs, and artifacts.
Reads and reports. Writes nothing unless you pass --artifacts.
One graph. Three ways in.
Assist
In the app
Ask who owns a service, what a screen calls, or what a change touches without opening a terminal.
In the coding agent
Expose UIGraph to Cursor, Claude Code, Codex, opencode, or any client that speaks MCP over stdio.
Skills
In the workflow
Install uigraph-oss/skills once, then use /uigraph as part of the agent loop you already run.
npx skills add uigraph-oss/skillsYour provider. Your boundary.
Bring a supported AI provider through AI_PROVIDER_*. Your code and graph go to the provider you choose, not to UIGraph.
Frequently asked questions
Still have a question about UIGraph AI? The docs cover agents, MCP, providers, and setup in detail.
Read the docsStop letting agents guess the architecture.
Connect the graph once. Put current system knowledge inside every agent you run.