Give every agent the whole system.
UIGraph turns your architecture into context agents can query: services, owners, APIs, dependencies, artifacts, and the boundaries between them.
Agent context contract
System knowledge
Available inside
Artifacts agent
Keeps declared docs current
Impact agent
Reviews change against architecture
Assist
Answers system questions in-app
MCP + Skills
Reaches the coding agent you use
Guarded automation
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. init onboards a repo; fix repairs a failed run.
Writes documentation artifacts. Never source code.
$ 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
Impact agent
Review the blast radius before merge.
uigraph-agents impact analyzes a commit range and reports affected services, APIs, and artifacts. Put it in a pull request job so architecture impact arrives with the review.
Reads and reports. Writes nothing unless you pass --artifacts.
Context where work happens
One graph. Three ways in.
The same system knowledge is available to someone in UIGraph and to an agent inside the editor. No separate architecture story to maintain.
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/skillsContext stays attached to the repo.
The agent sees the same graph your team updates through normal development work.
Your repo defines the system.
.uigraph.yaml names the services, artifacts, and relationships that matter.
The CLI refreshes the graph.
A configured CI sync keeps architecture context aligned with each push.
Every AI surface reads it.
Agents, Assist, MCP clients, and Skills work from the same system knowledge.
Your provider. Your boundary.
Bring a supported AI provider through AI_PROVIDER_*. Your code and graph go to the provider you choose, not to UIGraph.
Give the agent current context.
Sync the source, explore the system, then measure the work.
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.