ThinkReview Now Has Repository-Level Access — Reviews Just Got a Lot More Powerful
ThinkReview Now Has Repository-Level Access — Reviews Just Got a Lot More Powerful
Code reviews that actually understand your project, not just the diff.
The Problem with Diff-Only Reviews
Until now, most AI code review tools — including ThinkReview — reviewed only what was visible in the diff. That's a fundamental limitation. A diff tells you what changed, but not why it matters, what it might break, or whether it fits the patterns already established in the codebase.
A reviewer that can only see the diff is like a colleague who joins a code review without ever having looked at the rest of the project. They can spot syntax issues and obvious bugs — but they'll miss the things that matter most.
What's New: Repository and Project-Level Context
ThinkReview now supports platform integrations for GitHub, GitLab, Azure DevOps, and Bitbucket. By connecting your account with a Personal Access Token, you give the AI the ability to reach beyond the diff and fetch the context it actually needs to give a meaningful review.
This works through LLM tool calling — the AI can now make targeted API calls to your platform during a review to pull in:
- Related files and modules referenced in the change
- Base branch file content to understand what's being replaced
- Linked issues or ticket descriptions for intent context
- Project structure to understand patterns, naming conventions, and architecture
The result is a review that understands your codebase, not just the isolated lines being changed.
Why This Makes Reviews More Accurate
Consider a PR that refactors a shared utility function. A diff-only review might approve it as clean and correct. But with repository access, the AI can see every file that imports that utility, spot that two of them rely on a side effect being removed, and flag the regression risk before it ships.
The same applies to security, architecture decisions, and consistency checks — all things that only make sense with full project context.
Your Tokens Are Safe
When you connect an integration, your PAT is encrypted at rest using industry-standard encryption. Encryption keys are derived server-side and never stored alongside your tokens — we cannot read your token in plaintext, and neither can anyone who accesses our database. Your token is only decrypted in memory at the moment it is needed to fetch context during a review, and is never logged.
You can review our Privacy FAQs for full details.
How to Connect Your Integration
- Open the ThinkReview web app at app.thinkreview.dev
- Go to Integrations in the sidebar
- Add a Personal Access Token for GitHub, GitLab, Azure DevOps, or Bitbucket
- Run your next review — the AI will automatically use the available context
You can store up to three credentials per platform and delete them at any time.
What This Means Going Forward
Repository-level context is the foundation for everything we want to build next — deeper codebase understanding, team-level review patterns, and reviews that get smarter the more your team uses them.
If you've been using ThinkReview for a while, now is a great time to connect an integration and see the difference. The reviews speak for themselves.
Install ThinkReview:
- Chrome / Edge / Brave: Chrome Web Store
- Firefox: Firefox Add-ons