Skip to main content

How It Works

Mention the ZeroPath bot in a pull request or merge request comment. It processes the command and reports the result in the same thread.
1

Mention the bot

Start your comment with @ZeroPath (the legacy alias @zeropath-ai also works), or @<your-bot-username> (the exact username configured for your GitHub App or GitLab integration). Environment-specific bot usernames only match that exact integration.
2

Type a command

Use one of the structured commands below, or ask a natural-language question. Targets like issue 2 are matched against the issues ZeroPath has reported on this PR.
3

Read the reply

For Assistant questions, the bot updates its acknowledgment with the answer when it is ready. Structured commands report the action’s outcome. An acknowledgment means the bot received your comment. Wait for the result before repeating a request.
Bot commands are supported on GitHub, GitLab, and Azure DevOps. Bitbucket Cloud and Data Center are supported in releases containing ZP-7560; on-premises installations need a published distribution containing that update.
On Bitbucket, post a new, unedited comment. Explanations run asynchronously and replace the initial reply; triage and rescan commands reply with their result. Replies to tracked finding comments target that finding. Top-level commands on partitioned repositories target the latest tracked PR scan within the connection, so scan the PR first. Bitbucket does not support branch modification or check bypass commands. retriage queues an investigation and replies with its status; read the completed investigation in ZeroPath.
Bare @ZeroPath with no command makes the bot reply with a hint: I'm here. Try: @ZeroPath fp issue 2 because …

Command Reference

Most categories accept the same target syntax (see Targets) and many accept an optional because <reason> suffix (see The because Modifier for which commands persist the reason).

Triage Status

Mark a finding’s correctness verdict. These commands change the issue’s triage state and trigger a vulnerability status changed notification through your configured channels.

Workflow Status

Move a finding through your team’s review workflow. These do not change the correctness verdict — use Triage Status for that. fixed in records the commit as the reason for the resolution, but only after the bot checks that the commit is one of this PR’s commits. It accepts a commit SHA (7 to 40 hexadecimal characters), a SHA in backticks, or a link to the commit. Without a <target>, it applies to the finding whose thread you are replying in. If the commit is not on the PR, matches more than one commit, or the PR has more commits than the bot can check, the bot says so and changes nothing.
fixed in (the command above and the reply without a mention) and the Accepted risk reply without a mention are available while the PR-bot finding-reply resolution setting is on. The setting is on by default and ZeroPath manages it. On ZeroPath-hosted deployments ZeroPath can turn it off, and the bot then treats these messages like any other message. The self-hosted chart does not expose the setting in this release, so self-hosted installations always have it on.

Assignment

Assign the linked Jira or Linear ticket for a finding to a teammate. Requires that the finding has an associated Jira/Linear issue (see Jira or Linear). If a target has no linked Jira/Linear ticket, the bot reports assignment isn't possible (no linked Jira/Linear ticket) for that issue and continues with the rest.

Auto-Fix Patches

Trigger ZeroPath’s patch generation pipeline for a specific finding. See Auto-Fix for the full feature.

GitHub Patch PR Changes

On GitHub, when ZeroPath opens an auto-fix patch PR, reviewers can request follow-up code changes directly from the PR conversation. Start a new PR comment with @ZeroPath, then describe the change you want.
PR comment
For these requests, ZeroPath:
  1. Checks that the PR is a GitHub patch PR created by ZeroPath.
  2. Verifies that the current PR head branch is the same patch branch ZeroPath created.
  3. Applies only the requested change.
  4. Commits the change to the existing PR branch.
  5. Replies with a summary and commit reference.
Direct patch PR branch changes are currently GitHub-only. GitLab bot commands still support triage, assignment, patch generation, rescans, retriage, and natural-language questions, but not direct follow-up commits to an existing patch PR branch.
ZeroPath refuses to push when the PR branch cannot be verified as a ZeroPath-created patch branch, the branch has moved while the bot was working, the PR comes from a fork, or the request is unsafe, ambiguous, impossible, or would make unrelated changes.

Scan Operations

When the bot can’t run a rescan, it explains why with one of: A scan for the current commit already exists. Use \rescan force` to bypass the cache., Cannot rescan a closed pull request.`, or a service-specific reason.

Supply Chain Intel Check Exceptions

See the Supply Chain Intel check for setup and supported lockfiles. On GitHub, ask for an exception to the ZeroPath Supply Chain Intel check for one package version it flagged on this pull request. There is no bypass for the Supply Chain Intel check; an exception is the way through. because <text> works in place of reason: <text>, and a reason is required. The command covers the Block and Warn hits that the latest Supply Chain Intel check of the PR’s current head recorded on that version. Your GitHub account must be linked to a ZeroPath user. Depending on the rules’ exception settings and your role, the bot either creates the exception, says until when it applies and re-evaluates the check, or requests it and names the approvers; the check re-runs once one of them approves. A rule that does not allow exceptions is named in the reply. On GitLab, Bitbucket and Azure DevOps the bot replies that @ZeroPath allow is not available on that code host yet.

Re-Triage (Deeper Investigation)

Re-run AI validation on findings using a more thorough investigation than the default PR scan. When the PR description references vulnerabilities by ZP-ID tag or dashboard URL (see Fix Verification), retriage re-runs fix verification instead. The retriage reply, posted in-place over the acknowledgment comment, lists each issue with a verdict (Confirmed or Disconfirmed), a security assessment, and a link to the issue in the ZeroPath dashboard.

Natural-Language Questions

Anything that doesn’t match a structured command or a GitHub patch PR change request is treated as a question to the bot. On GitHub, the bot replies with an AI-generated answer in the same comment thread, posting a Thinking... placeholder and editing it in-place with the full answer once ready.
PR comment
What the bot does with a message that isn’t a structured command depends on whether the ZeroPath Assistant is enabled for your organization. An organization admin can enable the Assistant.Assistant enabled: an unrecognized message gets an Assistant answer. Question-shaped messages (those classified as questions by the LLM) get a free-form AI answer on both GitHub and GitLab. The platforms diverge only when the classifier can’t recognize the message at all: GitLab returns a static reply listing the supported command examples (I couldn't understand that command. Examples: ...), where GitHub falls back to a free-form Assistant answer. If you’re on GitLab and the bot replies with the static command list, rephrase as a clear question or use one of the structured commands above.Assistant disabled: the bot has nothing to answer with. It posts the list of supported commands once per thread and stays silent in that thread afterwards. On GitHub the list includes @ZeroPath allow, which the other code hosts do not run. The bot’s acknowledgment of your comment still shows that it received it: an eyes reaction on GitHub and GitLab, a like on Azure DevOps. Bitbucket has no acknowledgment.Structured commands such as @ZeroPath fp issue 2 because … work in both cases.
Comments that look like prompt-injection attempts are blocked automatically. If you receive a rejection message, rephrase the question as a direct inquiry about a specific reported finding.

Replying Under a Finding Without a Mention

On GitHub and Azure DevOps, two replies under a finding’s comment are recognized without @ZeroPath. The reply has to start with these words, and it applies to the finding whose thread you are replying in.
PR reply under a finding
The bot answers with the same confirmation as the matching command, followed by I recorded this from your reply in this thread. To undo it, reopen the issue in ZeroPath. Nothing is recorded silently. To reverse it, reopen the finding: reply @ZeroPath in-progress or @ZeroPath status pending_review in its thread, or reopen the issue in ZeroPath.
  • Anything else you write under a finding is treated as a question, as described in Natural-Language Questions. Accepted risk assessment is wrong and Not fixed in abc1234 are not recognized as these replies.
  • Text after the commit or after Accepted risk never changes which finding is affected. To act on another finding, use a command with a target.
  • Only the thread that ZeroPath’s comment for a finding started counts. In any other thread, such as the Azure DevOps summary thread that links every finding, these replies are treated as questions and change nothing.
  • The same permissions apply as for the commands: Mark Issues as Open for Fixed in and Archive Issues for Accepted risk. With access control enabled, your account must be linked to a ZeroPath identity.
  • These replies are handled even when the ZeroPath Assistant is not enabled for your organization.
  • If the finding is no longer reported by the latest scan of the PR, the bot says so and changes nothing.
  • A reason longer than 2000 characters is not recorded; the bot tells you and you can post a shorter one.
  • Both replies, like fixed in, are available while the PR-bot finding-reply resolution setting is on (the default); see the note under Workflow Status. With it off, they go to the Assistant as before.

Targets

A target specifies which issue(s) the command applies to. The parser accepts: The implicit form is the easiest path: open an inline finding comment, reply to it with @ZeroPath fp because not reachable from input, and the bot applies the command to that finding without you having to name an issue number. Every inline finding comment includes a quick-tips footer with example reply commands, so you can see the syntax without leaving your PR. A bare retriage with no target defaults to all issues in this PR.
Use commas, not the word and, to separate multiple issue numbers. The parser only recognizes comma-separated lists — issues 1 and 4 silently targets issue #1 only, dropping and 4. Always write issues 1, 4.

The because Modifier

Every triage, workflow-status, and retriage command accepts an optional because <reason> suffix. The text after because is captured by the parser as the user’s reason for the action.
PR comment
How the reason is used depends on the command:

Worked Examples

Permissions

When access control is enabled for your organization, the bot verifies that the VCS user who posted the comment is linked to a ZeroPath identity, and that the linked user has the right repository permission for the action. For Bitbucket, link the contributor account for the correct instance under Teams. Permissions below use the exact display names from the Teams settings page, so an admin can find each one as a checkbox in the team-permissions UI.
These are distinct permissions. A user with Mark as False Positive but not Archive Issues can run fp but will be denied on accepted-risk, even though both are “triage” actions in casual usage. Likewise, non-exploitable is gated by Mark as True Positive, not False Positive — both commands assert a vulnerability classification, so they share the True Positive permission.
If a user lacks the required permission, the bot replies with Permission denied (missing <PERMISSION_CONSTANT>). For example, ISSUE_EDIT_OPEN maps to Mark Issues as Open, PATCH_CREATE maps to Generate Patches, and PATCH_ISSUE maps to Create Pull Requests. If the comment author has no linked ZeroPath identity on GitHub, the bot replies:
I can’t verify your ZeroPath identity for this organization. Your GitHub account isn’t linked to a ZeroPath user yet. To link it, set your GitHub public email (Settings > Public profile) to match your ZeroPath account email, then comment again. The link is saved on our side, so you can switch the email back to private afterward. This should fix the issue most of the time. On GitHub Enterprise Server, ask your org admin to link your account under Teams instead: ZeroPath does not match accounts by email there, because the server may not verify emails.
On GitLab the bot replies:
I can’t verify your ZeroPath identity for this organization (no linked ZeroPath user). Please contact your org admin to link your account.
See Teams & Permissions for how to link VCS users and configure RBAC.

Platform Support

Supply Chain Intel check exceptions (@ZeroPath allow) are GitHub-only.

Troubleshooting

The bot replies “I couldn’t understand that command.” The parser fell through to neither an explicit keyword nor a question. Use one of the worked examples as a template, or paste a dashboard URL as the target. The bot replies “I didn’t run that command. …” The command was recognized, but one of its parts is invalid, so the bot ran none of it. The reply says which part. The usual cause is a reason after because longer than 2000 characters (for retriage, the context after because can be up to 20000 characters). The other causes are an assignee that is not an email address or an @handle of at most 100 characters, and an issue link or ID that is not a valid ZeroPath issue ID. Fix that part and post the command again. The bot replies “I didn’t record a fix: …” The bot checks every fixed in claim against the commits of the pull request, and it records nothing when it cannot confirm the commit. The reply says why: the commit is not on this PR, the SHA matches more than one commit (use a longer SHA), or the PR has more commits than the bot can check (use @ZeroPath closed because fixed in <sha> instead). When the bot cannot load the PR’s commits at all, it replies with the generic internal-error message; try again in a few minutes. The bot posted the command list once and then stopped answering The Assistant is disabled for your organization, so the bot can’t answer free-form messages. It posts the command list once per thread (“The ZeroPath Assistant isn’t enabled for this organization…”; on GitHub it includes @ZeroPath allow) and stays silent in that thread afterwards. The bot’s acknowledgment of your comment still shows that it received your message: an eyes reaction on GitHub and GitLab, a like on Azure DevOps. Bitbucket has no acknowledgment. Structured commands such as @ZeroPath fp issue 2 because … keep working. To get answers to free-form questions, ask an organization admin to enable the Assistant. The bot replies “No matching issues found for that target.” The issue number you used doesn’t correspond to a finding ZeroPath has reported on this PR. Check the PR summary comment for the list of reported issues, or use all issues in this pr. The bot replies “I can’t verify your ZeroPath identity…” Your VCS account isn’t linked to a ZeroPath user. On GitHub, the fastest fix is to set your GitHub public email (Settings > Public profile) to match your ZeroPath account email, then re-comment — ZeroPath will auto-link the accounts via email correlation. You can switch the email back to private afterward; the link persists. On GitHub Enterprise Server, ZeroPath does not match accounts by email, because the server may not verify emails; ask your org admin to link your account under Teams. On GitLab the email-correlation fallback isn’t implemented yet, so contact your org admin to link accounts under Teams, or run the action from the ZeroPath dashboard. assign reports “no linked Jira/Linear ticket” The target finding has not been pushed to Jira or Linear yet. Configure the Jira or Linear integration with auto-ticketing, or create the ticket from the dashboard first. The bot rejected my comment as prompt-injection content Rephrase as a direct question about a specific reported finding, without instructions framed as bot commands embedded inside it. The bot refused to modify a GitHub patch PR The bot only commits directly to PR branches that ZeroPath created for patch PRs. It refuses when it cannot verify the branch, the PR comes from a fork, the branch moved while the request was being prepared, or the requested change is unsafe, ambiguous, impossible, unrelated to the patch, or produces no file changes.
See PR Scanning for the surrounding feature (check statuses, inline comments, summary comments) and Auto-Fix for what generate patch and approve patch actually produce.