Ground analysis in the repo where definitions live.
Connect Vuon to code context so agents can understand metric logic, data model changes, and implementation details.
Authorize repo context
Link the repositories that contain definitions and data model logic.
Use relevant files during analysis
Vuon brings the right code context into the agent run.
Show what shaped the answer
The final output can point technical reviewers to source context.
Context type
Repo-aware analysis
Code is data context
Important business logic often lives in repositories, not BI tools. Vuon can use that context when answering data questions.
Definition discovery
Surface relevant metric logic, transforms, and configuration when the agent plans work.
Change awareness
Explain analysis shifts that came from code or data model changes.
Reviewable links
Point technical users back to the files that shaped an answer.
Less context copying
Analysts should not have to paste code snippets into every prompt. Repo context lets Vuon retrieve what matters.
Approved source
Use the same definitions developers and analytics engineers maintain.
Agent planning
Give the agent enough context to choose the right tables, functions, and filters.
Documentation loop
Turn repeated code-derived context into clearer documentation over time.
How it works
A clear path from context to action.
The same operating rhythm runs through the product: gather trusted context, show the work, then ship an output that can be reviewed.
Authorize repo context
Link the repositories that contain definitions and data model logic.
Use relevant files during analysis
Vuon brings the right code context into the agent run.
Show what shaped the answer
The final output can point technical reviewers to source context.
Next step