ci: use haiku model for issue dedupe workflow
What the developer wrote
Authored by Elle Mouton
ci: use haiku model for issue dedupe workflow
Switch the claude-dedupe-issues workflow from the default (most
expensive) model to claude-haiku-4-5, which is significantly cheaper
and sufficient for issue duplicate detection.
What changed, and why it matters
This commit changes a GitHub automation workflow to use a cheaper AI model for detecting duplicate bug reports. It is a cost-saving configuration change with no security relevance.
No security action needed; this is a benign CI cost optimization.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch adds a single line to .github/workflows/claude-dedupe-issues.yml specifying model: claude-haiku-4-5-20251001 for the claude-dedupe-issues action. This switches the duplicate-issue detection workflow from a more expensive default model to a cheaper, lighter model. No code, secrets, permissions, or trust boundaries are modified.
Changed components
.github/workflows/claude-dedupe-issues.ymlInspect captured patch +1 / −0
diff --git a/.github/workflows/claude-dedupe-issues.yml b/.github/workflows/claude-dedupe-issues.yml
index 25b4696..5f73298 100644
--- a/.github/workflows/claude-dedupe-issues.yml
+++ b/.github/workflows/claude-dedupe-issues.yml
@@ -30,5 +30,6 @@ jobs:
with:
github_token: ${{ secrets.GITHUB_TOKEN }}
allowed_non_write_users: "*"
+ model: claude-haiku-4-5-20251001
prompt: "/dedupe ${{ github.repository }}/issues/${{ github.event.issue.number || inputs.issue_number }}"
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.