Follow a finding through the relevant files before deciding what to fix. Investigate is read-only and uses the selected review agent.
Investigate a finding
- Open a completed review and choose Investigate Finding.
- Start at the finding’s line. Each step explains the next file in the call path in one or two sentences.
- Use Next or the arrow keys to move through the walkthrough.
- Read the summary on the right: what is wrong, why it matters and how to fix it. Open the diagram when useful.
- Ask follow-up questions in the same window, or use Open in Cursor to hand the fix to your editor.
CodeCrab’s investigation does not edit your repository. Opening the editor is a separate handoff; any edits you make there are your decision. File views mark added lines in green and removed lines in red.
Prepared deep dives
After a review finishes, CodeCrab prepares Critical and Required deep dives in the background, two at a time. They are often ready when you open them, but preparation time depends on the review and agent.
Disable background preparation in Settings → Models if desired. Optional and Nit findings are analyzed when you open them.
Review the PR’s own code
For Team PRs, reviews and deep dives use a read-only copy of the PR’s code, not your currently checked-out branch. Copies live under ~/.codecrab/worktrees; your branches and uncommitted work remain untouched.
GitLab merge requests use the same isolated-copy workflow. A copy is automatically removed after its PR or MR is closed.
If preparing the PR code fails
| Attempt | What CodeCrab does |
|---|---|
| 1. Clone remote | Fetches through your local clone’s remote. |
| 2. HTTPS | Retries using the authenticated gh or glab session. |
| 3. Source archive | Downloads a plain copy of the PR source, without git history. |
| 4. Local clone fallback | Only if all preparation attempts fail, logs a [WARN] and reads your clone’s current branch. |
For a GitHub project, verify authentication after an SSH Permission denied (publickey) message.
gh auth statusFor GitLab.com, check the corresponding session instead.
glab auth status --hostname gitlab.comInvestigate reviewer feedback
In My PRs, use Investigate comment to understand a reviewer’s request and get a fix plan. Follow-up answers use your active AI agent. Switching agents preserves existing review context and deep dives.
Open in GitHub or the corresponding GitLab link takes you back to the hosting service. Open {KEY} opens a Jira ticket when the PR links one. CodeCrab never posts the reply or comment for you.