The repository view
Every repository a code source indexes has a page of its own. It shows what the code host reports about the repository and what the index measured, draws the code as a graph of files, symbols and their relations, searches it, lists what uses a function or type, and answers questions from the repository’s own code. Open it from a source’s repositories on the Codebase knowledge tab, or from a security finding’s Show in the repository’s graph.
Who can do what
Section titled “Who can do what”| Role | What they can do |
|---|---|
| Admin | Everything below, and Refresh details, Sync source and Edit source. |
| Builder | Read the page, search it, use What uses this and Ask. |
| Auditor | Read the page and the graph. Searching and asking are for the roles that use the Code Assistant; the page says so where they would be. |
| End user, Reviewer | Cannot open the page. |
What you see
Section titled “What you see”The header names the repository, links to it on its host, and shows when its source last synced, or Last sync failed. Below are three tabs.
Overview
Section titled “Overview”- About: description, Visibility, Default branch, Indexed from (the branch and commit the index holds), License, Created, Last push, Latest release, Latest tags, Website, Size, Commits, First indexed and Details as of.
- Repository in figures: stars, forks, open issues and open merge or pull requests, as the host reports them.
- Languages: the share of each language in the index. Files in languages the index does not parse are counted as Other (not parsed).
- Symbols: functions, methods, classes, types, interfaces, structs and enums, counted.
- Relations: calls, imports, and inheritance and implementations, each split into explicit and inferred; imports of outside code; calls too ambiguous to draw; references not found.
- Recent commits and Contributors.
- Largest parts of the index: chunks per folder and the longest files.
- What the last sync skipped (too large, binary or empty) and how many files had secrets removed before indexing.
Each figure says where it comes from: Reported by the host, Measured by our index, or both.
Graph and search
Section titled “Graph and search”The graph draws the repository, its folders and files, and the symbols each file defines, joined by four kinds of relation:
| Relation | Links |
|---|---|
| Structure | A folder contains a file; a file defines a function, method, class or type. |
| Imports | A file imports another file or folder. |
| Calls | A function or method calls another. |
| Inheritance | A type inherits from, or implements, another. |
A relation is explicit when it is written in the code or resolved exactly, and inferred when it was resolved by name. The console marks every inferred relation.
A repository of more than 5,000 nodes opens on its groups rather than every node: open a group to see its nodes. Select a node to see its details: Parents and Children, Calls and Called by, Imports and Imported by, Inherits from and Inherited by, Implements and Implemented by.
Search the code finds the functions, types and files that best match what you type: a symbol name, an error message, or a plain description such as “where are refunds validated?”. Under What to search, choose This repository, or a team, to see what that team’s editors find across every source mapped to it. Each match shows its lines, a score, its first 20 lines and how many places use it.
What uses this
Section titled “What uses this”From a selected node, What uses this walks the graph:
- Under Which way, choose Used by (what calls, imports or inherits it) or Uses (what it uses).
- Under How far, choose Directly, Up to 2 steps or Up to 3 steps.
The list is grouped by file, with each use’s line and the relation that links it, and counts what was Found, the Files and how many are Inferred only. Copy the list as Markdown copies it for a merge request or a ticket. Developers’ editors reach the same walk with the find_usages tool; see Connect your editor.
Ask answers questions about the repository, such as “What does this repository do?”, “Where are the HTTP routes defined?” or “How are errors handled?”. Each answer is written by the Code Assistant’s chat model from the best-matching excerpts of the repository’s code, and cites them by number. Sources of the answer lists the cited excerpts, each with Show in graph.
Each question carries the turns before it, up to 12. The question is checked by the tenant’s guardrail policy before it is searched or sent, and its tokens are charged to the tenant like any chat.
What you can do
Section titled “What you can do”Refresh what the host reports
Section titled “Refresh what the host reports”Admins select Refresh details to read the host’s figures again. The host is asked at most once a minute per repository; Olympusx AI also refreshes them during syncs when they are more than 6 hours old.
Sync or edit the source
Section titled “Sync or edit the source”Sync source and Edit source act on the source the repository belongs to. See Code sources.
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Nodes drawn whole before the graph opens on groups | 5,000 |
| Steps in What uses this | 1 to 3 |
| Uses listed in one answer | 500. Above it, the page says Only the first N are listed; choose one of them to go further from it. |
| Links shown per listed use | 5 |
| Search query | 4,000 characters |
| Matches per search | 1 to 20; 8 by default |
| Lines shown per match | 20; the whole match is on the host |
| Excerpts one Ask answer is grounded on | 8 |
| Turns one Ask question carries | 12 |
| Refresh details | Once a minute |
Related
Section titled “Related”- Code sources
- Code tools
- Security findings, which open on the line in this graph