BugBot

Set up a review or diagnosis

Select a project in Neurion Code and choose BugBot. Identify the files, change, or failure to investigate. Describe the expected behavior and include a reproducible example or error when available.

Review and diagnosis are read-only operations. They inspect the permitted source and report findings; selecting BugBot does not itself authorize file edits. Verification also requires the applicable task scope.

1. For a review, identify the relevant files or change and what the code must preserve.
2. For a failure, provide the trigger, expected outcome, actual result, and relevant error.
3. Specify compatibility, performance, security boundaries, or files that must not change.
4. Ask for evidence tied to the current source and distinguish confirmed issues from open questions.

Evaluate each finding

A useful finding identifies the affected code, a concrete trigger, and the resulting impact. Check that it applies to the current version and is supported by the code or a relevant reproduction.

• Read the affected file and location.
• Check the conditions needed to trigger the problem.
• Distinguish a demonstrated defect from an assumption or style preference.
• Review the proposed correction and the validation needed to establish that it works.

A finding is not a completed fix. A clean review means the performed review did not establish a reportable issue; it is not a guarantee that the code contains no defects.

Authorize a repair and retest it

When you want a repair, request it explicitly and provide the required write and command authority. BugBot uses a separate repair handoff for the selected project. The read-only review does not silently become permission to change files.

1. Choose the finding or failure you want fixed.
2. Confirm the intended behavior and the files or project the repair can change.
3. Review any required implementation or command permissions.
4. Inspect the resulting diff and the checks performed.
5. Retest the original trigger and review any remaining uncertainty.

For an investigation of a website or API, use CyberBot with its own authorized target scope. A code review does not authorize testing a live service.

CyberBot workflows

Review task permissions

• Previous Ultra mode
• Next CyberBot