The pull request explainer now runs inside claude-code-action

Version 1.9.0 moves the pull request explainer into the Claude Code step you already run. The maintainers put it this way: it runs inside claude-code-action, on the Claude plan the repository already uses.

The setup needs one secret. It's the Claude Code OAuth token, the one a repository already has when it runs claude-code-action on a Claude plan. You don't need a Bisque account.

Claude's session inside claude-code-action can't publish, because that action takes away the means to mint the run's GitHub identity. So the work splits in two. In the first job, Claude writes the explainer, checks it and narrates it, so it can still fix a word the voice gets wrong. A second job only publishes that folder, audio included, and comments the watch link.

Publishing takes one new input, called presentation. Here is the second job. Only this job asks for the permission to publish. It downloads the folder the first job uploaded. Then presenter publishes that folder. No model runs in this job, and nothing is narrated again.

publish:
  needs: write
  permissions:
    id-token: write
  steps:
    - uses: actions/download-artifact@v4
      with: { name: explainer, path: explainer }
    - uses: bisque-cloud/presenter@v1
      with:
        source: pull-request
        presentation: explainer

The present skill gains a command, narrate. It narrates every slide without signing in. It reports each slide's length and any pronunciation warnings, so Claude can mark a word and run it again. And publish now reuses that audio instead of narrating again.

Nothing you run today has to change. The new input defaults to an empty string, and the steps that already existed run only when you leave it empty. The release notes list no breaking changes, so there's no migration to do.

Inside claude-code-action, publish stops with an error, so end your prompt after narrate and leave the audio folder in place. And the publishing job uses the voice and speed that audio was made in. It narrates only the slides that have no audio.

To upgrade, copy the example workflow into your repository. One limit: pull requests from forks run without secrets, so the explainer covers branches in your own repository. Claude writes in the first job, a second job publishes, and the full notes are on the release page.