gonuUnderstand a repository
Explore project structure, relevant files and important execution paths before making changes.
WHEN IT HELPS
Put it to work.
Get oriented in an unfamiliar codebase, locate an error path or prepare onboarding material from actual files.
Before you begin
- An authorized local repository open in Worker, CLI or the extension.
- Consent to share relevant excerpts with your selected model.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Select the project root with its manifest, source and tests. Start with Ask and identify which part of the project you want explained.
Ask where a request starts, which modules it passes through and where related tests live. Review file references instead of relying on a broad architecture claim.
Open the referenced files. Ask a follow-up about a missing module or turn the explanation into a Plan task with explicit acceptance criteria.
Example repository / File explorer
A REQUEST TO START WITH
Trace sign-in from the entry point to session storage. Cite relevant files and tests. Identify missing context and do not edit anything.
THE USEFUL RESULT
What you should leave with.
A repository explanation grounded in inspected files, with a narrower next task.
Know the boundaries.
- Local indexing is bounded and respects ignore/secret exclusions; it is not a complete semantic model of every language.
- Selected excerpts may be sent to the model. Web Knowledge can explain selected imported files but does not browse the entire local repository.
IF SOMETHING DOESN’T WORK
A symbol or file is missing.
Check the selected root and ignore rules. Explicitly select a safe related file or narrow the search; do not remove secret exclusions to improve results.
Contact support