Advanced Codebase Context prepares several connected views of a repository. Together, they help an investigation or coding agent choose where to start, follow the relevant code, and check the consequences of a change.
Five views of your codebase
| View | Question it helps answer | Context provided |
|---|---|---|
| Atlas | Which subsystem owns the behavior? | A thematic map of subsystems, their purpose, and the files that implement them. |
| Code map | Which files should the agent read? | Directories and files with their purpose, so the agent can narrow the source it reads. |
| Relationships | What other code is connected? | Dependencies, mirrored definitions, registration patterns, and files that change together. |
| Change impact | What could a fix affect? | Direct and indirect dependents of a symbol and candidate tests to check. |
| History | Which change explains the behavior? | Prepared changelogs and the changes relevant to the question. |
These are views into the same codebase. An agent might start from the Atlas, find the relevant files in the code map, follow a relationship to a caller, and use change impact to identify tests before reading the source.
Source and prepared context
Basic Codebase Context makes connected source available for discovery and search. Advanced prepares the additional views above. Source and generated context can have different preparation dates, so check the branch and revision when an answer depends on a recent change.
Connected repositories receive source updates through their code-host webhooks. Advanced context preparation and updates use account credits. Contact Driver support to enable Advanced with an upgrade. Use Codebase Settings to select the branches to update and the minimum refresh interval.
Which codebases an investigation can read
An agent’s machine identity limits the codebases it can access. Its connected Jira projects limit the ticket context available to it. Review source permissions under Settings > Access Control and configure Jira projects under Settings > Integrations > Jira Cloud > Project Scopes.
See Access control for the relationship between people, teams, and machine access.