[FEATURE] Autofix pull requests: make the "๐Ÿค– Addressed by Claude Code" reply signature optional

Status Open
Maintainer reply None cached
Activity 0 comments ยท opened Aug 27, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

was requested before here but closed: https://github.com/anthropics/claude-code/issues/73511

Summary

The "Autofix pull requests" feature instructs Claude to append this trailing
line to every PR review-thread reply it posts:

_๐Ÿค– Addressed by Claude Code_

I'd like a per-user toggle in the desktop app to suppress that signature
while keeping the rest of the Autofix behavior.

Where it comes from

Each <ci-monitor-event> from Autofix currently includes:

End each reply with the line "_๐Ÿค– Addressed by [Claude Code](...)_" so reviewers can see it was automated.

It isn't something Claude generates unprompted โ€” the instruction is baked into
the event payload the desktop app sends, so today it can only be avoided by
turning Autofix off entirely or overriding it with a durable per-user
instruction (memory / CLAUDE.md).

What I'd like

A checkbox in the same section of the desktop-app settings where Autofix is
enabled โ€” something like:

  • [x] Autofix pull requests
  • [ ] Append "Addressed by Claude Code" signature to review replies

Off by default, or on-by-default with an easy way to turn it off โ€” either
works.

Why

Reviewers can already tell an automated push happened from commit metadata
and reply cadence; the signature adds visual noise to threads, especially on
active PRs where Claude posts several replies per round. Some teams also
prefer human-only-looking review threads for consistency with their existing
bot-suppression conventions.

Alternatives considered

  • Turn off Autofix entirely โ€” loses the whole feature.
  • Instruct Claude via memory / CLAUDE.md to skip the line โ€” works, but every

user of the feature has to figure that out independently, and the app's
event payload still asks Claude to include it, so the override is fragile
across sessions and projects.

Making it a first-class setting seems like the right

Proposed Solution

Ideal user experience

Where it lives. In Settings โ†’ Autofix pull requests (same panel as the
"Enable Autofix pull requests" toggle), so the signature control is
co-located with the feature it affects. A user who is looking at whether
Autofix is on can see, in the same glance, whether the signature is on.

The control itself. A single checkbox directly under the enable toggle:

[x] Enable Autofix pull requests
โ˜‘ Append attribution signature to review replies โ“˜

Preview: _๐Ÿค– Addressed by Claude Code_

  • Default: on (matches current behavior โ€” no regression for existing

users who like the signature).

  • Disabled and greyed out when Autofix itself is off.
  • A live preview of the exact rendered signature line sits directly under

the control, so what I'm toggling is unambiguous โ€” no reading the docs
to figure out what "attribution signature" means.

  • The โ“˜ info tooltip explains: "When on, Claude ends each PR review-thread

reply with a small attribution line so reviewers can tell the reply came
from Autofix. Turn off to leave replies unsigned."

How the change propagates. Takes effect on the next <ci-monitor-event>
Autofix sends โ€” no app restart, no re-enabling of Autofix. If Claude is
mid-reply on a thread when the toggle flips, the currently-in-flight reply
keeps its old signature (the instruction was already sent); the next reply
uses the new setting. That's mostly invisible to the user but worth
documenting.

Scope. User-level, like Autofix itself. If in the future teams want a
per-repo override (some teams prefer signed replies as a norm), that could
come as a follow-up โ€” for v1, user-scope is sufficient.

How I'd actually use it.

  1. Open the app's settings.
  2. Find "Autofix pull requests" โ€” the signature checkbox is right there under

the enable toggle, not buried in a submenu.

  1. Read the one-line preview to confirm what I'm turning off.
  2. Uncheck it.
  3. Close settings โ€” no restart, no confirmation modal.
  4. Next time Autofix wakes me on a PR comment, my reply lands on the thread

as a plain factual sentence with no trailing signature line.

Stretch (not required for v1). A text field lets me customize the
signature to my own convention โ€” e.g., _(via Claude Code)_ or an empty
string โ€” with the current default pre-filled. This subsumes the on/off
toggle (empty = off) and covers teams that want attribution but with
different phrasing. Nice-to-have; the on/off toggle alone is 90% of the
value.

Non-goals for this issue.

  • Retroactively editing signatures on already-posted replies.
  • Rewriting the signature language on old replies when the toggle flips.
  • Changing what Claude does OUTSIDE Autofix (e.g., replies I post via

direct gh commands without a ci-monitor-event); those are separately
governed by user instructions and CLAUDE.md, and should stay that way.

Alternative Solutions

  • Turn off Autofix entirely โ€” loses the whole feature.
  • Instruct Claude via memory / CLAUDE.md to skip the line โ€” works, but every

user of the feature has to figure that out independently, and the app's
event payload still asks Claude to include it, so the override is fragile
across sessions and projects.

Making it a first-class setting seems like the right level.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub โ†—