Fix findings with your coding agent

Copy or download a scoped repair prompt, work locally, and return to verify the changed revision.

3 sections2 min read

Fix with your AI turns the findings you choose into a prompt for Codex, Claude Code, or another coding agent with your repository open. Copying or downloading the prompt does not start a Cefense scan, generate a hosted patch, or change a finding's status.

Choose the scope first

  1. 1
    Review coverage and the scanned revision

    Check the selected repository, branch, commit and coverage notice. An incomplete scan contains only the findings its finished checks reported. Missing revision metadata is shown as not recorded.

  2. 2
    Filter or select findings

    Without a selection, the queue prompt covers the full filtered result across pages. With a selection, it covers those selected findings. A finding detail starts with that finding; where a group contains more findings, the prompt preview offers the whole group explicitly.

  3. 3
    Preview, copy or download

    Open Preview prompt to inspect the scope and revision. Use Complete selection, or divide the work by package or category, or severity. Choose the current batch, then copy its prompt or download it as a text file. If clipboard access fails, copy from the selected prompt text or use the download.

  4. 4
    Work in the matching local repository

    Give the prompt to your coding agent with the intended repository open. It should check the current revision, preserve existing work, inspect each reported location, make the smallest appropriate repair and run the project's relevant checks.

  5. 5
    Return to Cefense for verification

    Review the local diff and test results. After you authorize publishing the changed code, select that branch in Cefense and start a scan of its changed revision. Check coverage and each finding's recorded result. Run a proof separately when you need evidence about a generated patch.

What the prompt contains

Each selected batch includes every finding ID in that batch, severity, category, location, available dependency and advisory details, verification state and reachability. Unknown information stays unknown. Raw code, evidence snippets and credential descriptions are omitted; the coding agent must inspect the local files.

The batch checklist records your review within the current preview session. It is a work aid, not evidence that a repair passed. A removed credential still needs revocation or rotation at its provider; never paste its value into the prompt or the chat.

Read-only command names

The existing CLI documentation uses cf status for repository and scan state, cf reproduced for the finding queue, cf reproduced show for one finding, and cf matched for findings with research. These names are retained across the handoff guide. Consult your installed CLI's command schema before using an alias or adding a flag. A command suggestion describes an available action; it does not grant permission to spend allowance or change a repository.

Have a correction or need help?

Email the docs team