Home / Blog / Why and how I use Assisted-by with Claude Code and not…
Tech News

Why and how I use Assisted-by with Claude Code and not Co-authored-by

Developers are replacing Claude Code automated co-author commit tags with Linux kernel Assisted-by trailers to track exact model versions across repositories.

By Dillip Chowdary • Nov 18, 2026 • Source: williamhuster.com

Why and how I use Assisted-by with Claude Code and not Co-authored-by
Image: williamhuster.com

At a glance

Early adoption
March 2025
Supported harnesses
Claude Code and opencode
Reference model
claude-opus-5
Trailer standard
Assisted-by
Git config key
trailer.assisted-by.ifExists addIfDifferent
Autonomous account
nimble-claude

Anthropic and the developer ecosystem continue refining automated assistant tooling as engineers seek cleaner version control attribution for generated software changes. Developer William Huster published a workflow for replacing default artificial intelligence co-author badges with standardized git metadata, according to williamhuster.com's report. The method eliminates automated marketing logos from commit histories while documenting exact model versions and toolchains directly in commit trailers.

This analysis details how engineering teams can disable automated co-author tags in settings files and deploy deterministic scripts for version control provenance. It serves software developers, engineering leads, and technical consultants using Claude Code or opencode who require clear auditability without inflating commit histories with synthetic co-authorship.

01Git commit metadata and settings toggles

Claude Code by default inserts a Co-authored-by trailer into git commit messages, which causes GitHub to display the assistant logo alongside human profile avatars. Early adopters using the command line interface since March 2025 have characterized this automated tagging as a promotional mechanism that over-anthropomorphizes artificial intelligence tools. Removing this default behavior prevents outside observers from misinterpreting client and proprietary project repositories as collections of unreviewed synthetic code.

Displaying automated tool badges across engineering commits creates an unintended signal of unreviewed code output for consulting agencies and individual software engineers. Software professionals retain ultimate responsibility for committed lines, making co-author designations inaccurate for tools operating under direct user guidance. Suppressing automated trailers preserves professional code standards while ensuring developers maintain full ownership over their published source trees.

Developers can disable the automated git metadata by updating the local user settings file located at ~/.claude/settings.json. Setting the commit and pull request keys within the attribution configuration block to empty string values silences the default behavior. This adjustment stops the client harness from attaching unapproved co-author tags across future commit messages.

02Driver seat responsibility and kernel trailers

Attributing artificial intelligence models as co-authors distorts engineering accountability because developers remain in the driver seat during every implementation session. Code authorship carries legal and operational responsibility, much like operating a vehicle on cruise control or driving a tractor. Software engineers historically cited StackOverflow snippets without naming the forum as a co-author, establishing that technical references remain tools rather than collaborating creators.

To maintain professional transparency without misrepresenting tool roles, engineers are adopting the Linux kernel standard for machine attribution. Appending an Assisted-by git trailer records the specific agent name, model version, and auxiliary tools utilized during the development session. This structured metadata format preserves precise provenance across developer workflows, recording entries like Assisted-by: claude-code:claude-opus-5 spekk or opencode:claude-opus-5 spekk.

| Attribution option | Git trailer format | Harness metadata | Commit badge | | Co-authored-by | Co-authored-by: Claude | Omitted | Vendor logo | | Assisted-by | Assisted-by: agent:model tools | Included | None | | Disabled | None | Omitted | None |

03Deterministic trailer scripts and repository configuration

Relying on system prompts to append attribution trailers often produces inconsistent formatting across varied coding sessions. Instructing agents to compose trailers manually increases the risk of malformed metadata or omitted tooling references. To ensure deterministic outputs, developers use a local shell script that reads session records directly from the active agent environment.

Setting up the automated trailer workflow requires a four-step terminal procedure to install and configure the helper utility:

Advertisement

Tech Pulse Daily

Get tomorrow's pulse first

Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.

  1. Create binary directory create the local user executable directory at ~/.local/bin.
  2. Download script fetch the raw assisted-by shell script from the GitHub gist into ~/.local/bin/assisted-by.
  3. Set permissions make the downloaded assisted-by script executable using chmod.
  4. Configure trailer handling set git config to prevent duplicate trailers during rebases and amends.

The helper script parses session logs from both Claude Code and opencode, generating a structured trailer flag when invoked during git commit operations. Developers can also enable automated pull request description trailers across specific repositories using git config assisted-by.pr true. Commits created manually by human engineers bypass the script entirely, leaving ordinary manual entries unencumbered by artificial intelligence metadata.

04Autonomous worker accounts and attribution tiers

A distinct exception to human commit authorship arises during fully asynchronous tasks executed by sandboxed artificial intelligence workers. For autonomous workflows, developers establish dedicated GitHub accounts such as nimble-claude to commit code without prior human review. Using a designated bot account signals to reviewers that incoming changes originated from an uninspected automated session requiring thorough examination before merging.

Software attribution policies established at organizations like ThinkNimble categorize development tasks into three operational tiers. Contributions fall into purely human work, fully autonomous machine generation, or hybrid assistance where human developers guide artificial intelligence execution. Hybrid assistance represents the prevailing industry standard, where teams assume the human programmer exercises responsible oversight and retains code accountability.

Note: When developers assume control over pull requests opened by autonomous agent accounts like nimble-claude, human contributions remain distinctly separated from earlier unattended bot commits. The developer becomes co-author on the overall pull request, preserving an explicit boundary between uninspected agent drafts and reviewed production revisions.

05Client setup commands and runtime switches

Managing attribution and model execution requires keeping developer environments aligned with official command line interface releases. Developers update their local installations using global package managers or native update utilities to ensure compatibility with configuration schemas. Maintaining current tooling ensures that local runtime settings properly suppress co-author tags while supporting session inspection scripts.

Command
claude update
npm install -g @anthropic-ai/claude-code
Command
/model claude-fable-5-1
/model fable
Command
claude --model fable
claude config set --global model fable
Command
mkdir -p ~/.local/bin
curl -fsSL https://gist.githubusercontent.com/whusterj/01be8cde934ed45ea5264c30163d9cf5/raw/assisted-by -o ~/.local/bin/assisted-by
chmod +x ~/.local/bin/assisted-by
git config --global trailer.assisted-by.ifExists addIfDifferent

Configuring ~/.claude/settings.json to disable default co-author injection prevents unapproved marketing badges across all repositories. Invoking the assisted-by script through commit trailer arguments guarantees deterministic provenance for both Claude Code and opencode environments. Combining user-level configuration with structured git trailers ensures full traceability while keeping human engineers in firm control of repository attribution.

Frequently asked questions

How do developers disable Claude Code co-author commits?

Users can set the commit and pr attribution values to empty strings within ~/.claude/settings.json. This configuration prevents Claude Code from adding co-author metadata or GitHub badges to commits.

What is the format for the Assisted-by git trailer?

The Assisted-by trailer format follows the Linux kernel convention as Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]. For example, a session might record Assisted-by: claude-code:claude-opus-5 spekk.

When is an artificial intelligence model permitted as a commit author?

Automated bots are assigned as commit authors during fully asynchronous sessions using sandboxed accounts like nimble-claude. This signals to engineers that the initial code was generated without human review.

How does the assisted-by script prevent duplicate trailers?

Setting git config --global trailer.assisted-by.ifExists addIfDifferent ensures that amends and rebases do not append duplicate trailers. The script reads session logs directly to produce consistent metadata.

Sources

Dillip Chowdary

Author

Dillip Chowdary

Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.

Related on Tech Bytes

Advertisement

5-min tech signal

Weekday briefing for engineers who skip the noise.

No spam · Unsubscribe anytime

Advertisement

✈️ CareerPilot

Your AI job-search copilot

Match your resume against live Ashby, Greenhouse & Lever openings — fit scores, job-specific resume optimization and email alerts.

Find matching jobs →

Free Tools

Browse all tools →