Before starting an investigation
You need a permitted staff role, an eligible account/plan, and enough credits in the project's owning account. Clients and guests do not receive developer fix actions just because they reported the issue.
Connect the correct repository through Settings → Version Control and grant access to the relevant source. Verify the report's version and supply useful reproduction steps. Screenshot, request, source, and backend context depend on the capture setup; missing evidence can limit the result.
Check Billing for the current credit balance and backend evidence if the problem is in a server request.
Start or retry an investigation
Open the annotation's AI analysis section and choose Start AI Investigation.
Wait for the result, then read its explanation and affected files
A suggestion is not proof that the diagnosis or fix is correct.
If the investigation fails or important context changes, use its retry action and inspect the new result/status
Reopening the issue is a workflow action, not the command for retrying the investigation.
If the action is disabled, check the account credits, effective role, connected source, active plan, and any in-progress investigation before retrying.
Apply changes in a local checkout
Use the CLI to authenticate, link the correct project, review the diff, pass its preflight checks, and explicitly confirm application. Check the source version and preserve unrelated local work.
Applying a patch locally does not commit, deploy, or merge it. Run the application's tests/checks and review the final diff before committing.
Create a pull request instead
Confirm the Git provider connection can write to the target repository and create branches/pull requests
Read-only repository access is not sufficient.
Choose Raise Pull Request from the suggestion
Review the offered branch, title, description, and draft option before confirming.
Open the created request in the provider and verify the target repository, base version, and diff
Creating a request does not mean it has been reviewed or merged.
Run the repository's required checks and complete your normal code review before merging and deploying.
Test the deployed outcome
Make a new build/deployment with the accepted change, repeat the report's steps, and request human verification against that target. Reject or revise a suggestion that does not fix the issue.
A resolved status, successful patch application, or generated confidence value is not a substitute for testing the intended result.