Skip to content

CI: Claude answers as claude[bot] on our own threads and runs Fable; forks keep the job token - #1469

Merged
GLinnik21 merged 3 commits into
mainfrom
ci/claude-bot-fable
Nov 19, 2026
Merged

GLinnik21 merged 3 commits into
mainfrom
ci/claude-bot-fable

Conversation

@GLinnik21

@GLinnik21 GLinnik21 commented Nov 19, 2026 •

Copy link
Copy Markdown
Collaborator

Follow-up to #1468. Claude now comments as claude[bot] wherever that is safe, and runs Claude Fable through the fable alias.

The split: a small route job reads the pull request's head repository from GitHub. Then exactly one of two jobs runs:

  • own handles issues and PRs from this repository's own branches.
    • It uses the Claude GitHub App's token, so comments are signed claude[bot] and Claude can push a branch and open a PR again.
    • An issue's text can still come from an outsider, so project hooks stay off and git tag is denied.
  • fork handles PRs from forks and is unchanged from CI: answer @claude mentions, fork PRs included, on the maintainer's subscription #1468.
    • It keeps the read-only job token, which cannot push a branch or tag and has no OIDC token.
    • Skills, subagents and tools/ stay off, the network and /proc deny rules stay, and commands still run in the bubblewrap sandbox with credentials stripped.
    • Comments there are still signed github-actions[bot].

Splitting by job, not by step, matters here: job permissions can't be widened from inside a step. That keeps id-token: write and the App token out of a fork's run entirely.

Model: both jobs pass --model fable, which follows the newest Fable version. If the subscription doesn't offer Fable, the first run's log will say so.

Review style: both jobs pass --append-system-prompt, which asks for findings as inline review comments, with a suggestion block when the fix is small. The summary comment is meant to be a few casual lines: a one-line verdict and at most a few bullets.

Paired repository setting, not in this diff: a tag ruleset on refs/tags/v*. It lets only admins, GitHub Actions (release.yml and rc.yml push tags with github.token) and deploy keys create, move or delete release tags. With it, the App token in own can't cut a release however Claude is steered.

Checks

  • ci/test_ci_timeouts.py: OK.
  • ci/test_ci_workflows.py: 103 tests OK.

Build bench: not applicable. This is a mention-only workflow and no build input changed.

🤖 Generated with Claude Code

GLinnik21 and others added 3 commits November 19, 2026 06:04
…oken on forks, runs Fable

Split the job: `route` reads the pull request's head repository; `own` (issues
and this repository's branches) uses the Claude GitHub App's token, so comments
are signed claude[bot] and Claude can push a branch; `fork` keeps the
read-only job token and every fork guard. Both run claude-fable-5-2. Hooks and
`git tag` stay off in `own` too, since an issue's text can be an outsider's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@GLinnik21
GLinnik21 enabled auto-merge (squash) November 19, 2026 03:11
@GLinnik21
GLinnik21 merged commit e9924f0 into main Nov 19, 2026
7 checks passed
@GLinnik21
GLinnik21 deleted the ci/claude-bot-fable branch November 19, 2026 03:11
tiper added a commit to tiper/fin-native that referenced this pull request Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant