Code Lens
Code Lens shows how the fast agent finds code in a connected GitHub repository: the index builds in your browser, and each search shows every step that ranked the files.
What it showsLink to 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 happensLink to 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.
LimitsLink to 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 whatLink to Who can do what
Members can open Code Lens. Each download of a repository's code is recorded in the audit log.
Checked against the product on 2026-10-05.
Was this helpful?
Related articles
- Repository AtlasThe Atlas shows the stack, infrastructure, rules and architecture of each repository, measured from its files and Git history. No model writes these facts.
- GitHub and GitLabConnect GitHub or GitLab and choose the repositories Crewshal may use. Workers then read the code, change it and open pull requests or merge requests.
- Live docsThe live docs describe every feature of Crewshal from its code: the screens, the operations behind them, the API reference and the MCP tools. Each release builds them again.