Guide your agents with your standards and architecture context
Agents generate code from patterns. They don’t know your module boundaries, security standards, or architectural intent. Sonar’s Guide stage injects all of it as structured, queryable context at the start of every agentic session — delivered by Sonar Vortex. Sonar is the only tool that tells your agent both where your architecture is today and where it’s supposed to go.
Context before code. Every time.
When an agent starts a new task, it has no knowledge of your architecture, your module boundaries, or your team’s coding standards. Left to its own patterns, it will create dependencies you didn’t intend, bypass structural boundaries, and generate code that technically works but silently erodes your architecture.
The Guide stage solves this by injecting structured context before the agent writes anything. Via the SonarQube MCP Server, the agent can query what is the current architecture, what is the intended architecture, and what coding standards apply. It then generates code that respects boundaries instead of violating them.
Current architecture the actual state of module dependencies and boundaries in your codebase today
Intended architecture where your architecture is supposed to be, what the team has agreed on
Active guidelines coding standards, security rules, and quality policies that apply to this repo
Context injection: dynamic and embedded
Sonar Vortex
Delivers project-specific context and constraints to your agent before it writes a line of code. Architecture, coding standards, and quality rules — retrieved via semantic navigation (ASTs, control flow), not keyword matching, and injected through SonarQube CLI or MCP Server.
SonarSweep
Context files that live inside the repo and travel with the codebase. Every agent that touches the repo picks them up automatically.