Use the claude model name from an env variable

[elisescu]

Modify the .github/workflows/claude.yml action to read the model name from an environment variable called CLAUDE_MODEL_NAME

[elisescu]

@claude implement this

[claude]

Claude finished @elisescu's task in 1m 7s —— View job

---

Task: read the Claude model name from CLAUDE_MODEL_NAME

• Gather context (read .github/workflows/claude.yml)
• Understand the request
• Write the change locally
• Push the change — blocked, see below

Result

I'm unable to push this change because it modifies .github/workflows/claude.yml, and the GitHub App I run under is not permitted to create or update workflow files (403 Resource not accessible by integration). More detail and workarounds are in the FAQ.

The change itself is two lines. Here is the patch to apply manually:

--- a/.github/workflows/claude.yml
+++ b/.github/workflows/claude.yml
@@ -17,6 +17,12 @@ concurrency:
   group: claude-${{ github.event.issue.number || github.event.pull_request.number }}
   cancel-in-progress: false
   queue: max
 
+# Model passed to `--model` below. Override without editing this file by setting the
+# CLAUDE_MODEL_NAME repository (or organization) variable; the fallback keeps runs
+# working when that variable is unset.
+env:
+  CLAUDE_MODEL_NAME: ${{ vars.CLAUDE_MODEL_NAME || 'claude-opus-5' }}
+
 jobs:
   claude:
@@ -85,5 +91,5 @@
           claude_args: |
-            --model claude-opus-5
+            --model ${{ env.CLAUDE_MODEL_NAME }}
             --allowedTools "Bash(bun ci:*),..."

Notes on the approach

• The env var is defined at workflow level (env: above jobs:), so it is in scope for the Run Claude Code step's with: block — the env context is available to steps.*.with expressions.
• It is sourced from vars.CLAUDE_MODEL_NAME, i.e. a repository or organization Actions variable (Settings → Secrets and variables → Actions → Variables). That's what makes it configurable without editing the workflow, which is the point of the issue. Set it there to switch models.
• || 'claude-opus-5' keeps the current behaviour as the fallback when the variable isn't set, so nothing breaks the moment this lands. If you'd rather the workflow fail loudly on a missing variable, drop the fallback and use ${{ vars.CLAUDE_MODEL_NAME }} — but note an empty --model flag would then be passed through to the action.
• If you intended a literal env var set elsewhere (e.g. exported by an earlier step) rather than an Actions variable, say so and I'll adjust — but Actions variables are the only mechanism that survives across runs without a file edit.

Nothing was committed, so there is no branch or PR link for this one; the change needs a human with workflows permission to commit it.