Review a workspace,not only a snippet
On New Review, paste and/or upload multiple files, mark each as To review or Context only, and add an optional title and description. Helpers stay visible to the model without flooding findings on every utility file.
Scope each file
Mark production paths To review. Mark fixtures, generated stubs, or neighbor modules Context only so the model has types and callers without grading every line.
Describe intent
Optional title and description anchor the review the same way a good PR description does - what changed and what is out of scope.
Same engine as GitHub
Findings, Policy findings, and Applied policy match paste-from-API and PR flows - this page is about the multi-file authoring UX, not a different analyzer.
Author checklist before you click Review
A clean workspace beats dumping the whole monorepo into one job.
- Include every file the model must judge - not only the one you edited last.
- Mark pure helpers Context only when you need them for types or imports.
- Drop lockfiles and vendor trees unless they are the change under review.
- Pick a policy profile on Pro/Enterprise when this project is not your account default.
Workflow
How teams wire it
- 1
Open New Review
From the dashboard, create a review instead of pasting into a one-off marketing demo.
- 2
Add files or paste buffers
Upload multiple paths or paste per-file content; set language when auto-detect needs help.
- 3
Mark review vs context
Toggle To review / Context only per file, then add description if intent is non-obvious.
- 4
Read findings with context list
Results show issues and which context paths were attached for that run.
Overview
When online paste is not enough
The online code review tool page is the fast single-buffer story. Multi-file workspace is for changes that span modules: a service plus its test, a route plus a form, a migration plus a model.
For huge trees, prefer GitHub PR review or shrink the set - combined payloads have size limits. Selection-sized scopes in the VS Code extension remain best for microscopic hunks.
Checklist
- Credits Multi-file reviews consume plan credits like other web reviews - check usage on the dashboard.
- Paths matter for policy Excluded paths and test-path rules work better when files carry real paths from upload.
FAQ
Common questions
From the blog
Open a multi-file review
Start free, upload the files that changed plus one or two context helpers, and compare findings to a single-snippet run.