Feature · Knowledge
Code Lens
See how the fast agent finds code in a repository.
How it works
What it shows
Code Lens has three views: Ask, Map and Index.
- Index: the build, step by step. Each worker lane shows the file it reads now.
- Map: a short summary of every area, folder, file and symbol.
- Ask: type what you want to change. The files to change come back in milliseconds, with the score each search method gave, the exact lines a model would read, and the timing of each step. Pick a component to see its chain to the APIs, handlers and tables.
Where the work happens
The platform streams the repository's code files from GitHub to your browser. Your browser builds the index and answers the searches. Large data files and build output are not sent. The index stays in your browser for the next visit.
Limits
- A repository must be connected through GitHub, and your browser needs about 2 GB of free memory for a repository of 7,000 files.
- Git history is not sent, so the "recently changed" signal is off here.
Who can do what
Members can open Code Lens. Each download of a repository's code is recorded in the audit log.
From the help article Code Lens, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
MemberlistLensRepositoriesA member's read of the org's GitHub repositories.
Types:
Record<string, never>returnsListLensRepositoriesResult
ViewerlistConnectOptionsLists connect options.
Types:
EmptyRequestreturnsListResponse<ConnectOptionDto>
AdminNo API tokensconnectStartConnects the start.
Types:
ConnectStartRequestreturnsConnectStartResponse
AdmingetConnectGets the connect.
Types:
ConnectIdRequestreturnsConnectSessionDto
AdminNo API tokenscompleteConnectCompletes the connect.
Types:
CompleteConnectRequestreturnsConnectSessionDto
ViewerlistMembersLists members.
Types:
EmptyRequestreturnsListMembersResponse
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Data exported
- Integration changed
- Integration connect failed
- Integration connect started
- Integration connected