Claude Code auto-inserts session links into every c…

Summary

Developers flagged that Claude Code appends a Claude session URL by default to the bottom of every commit message and PR description it creates
There's no opt-in consent step or onboarding notice at all, so developers reportedly only found out after the links were already public on GitHub
The community proposed three fixes: one-time onboarding consent, exposure with opt-out at the first commit, or removing the feature entirely

An unfamiliar link showed up under commit messages

On the left, Claude Code radiates light in all directions, and that light travels along a solid line to a pile of stacked ovals on the right — the commit history. This represents the session link being automatically inserted into every single commit, without exception. From the commit history, a dashed line continues on to a scattered cluster of dots representing developers, showing that they only notice this by chance, and belatedly, after the pile has already built up.

A developer working with Claude Code spotted something odd on GitHub. Every commit message and PR description they'd written had a link at the bottom in the form https://claude.ai/code/session_.... According to a issue raised on GitHub, this session URL gets inserted by default for every user, with no opt-in consent request and no mention during onboarding. The issue drew more than 200 upvotes on Hacker News, catching the attention of the developer community.

The timing is what makes it a problem. The developer only noticed the session links had been tagging along after they'd already made the commits, opened the PRs, and had teammates or open-source contributors see them. By that point, as the issue author points out, the links were already baked into public repository history that can't be undone.

What's the problem, and why does it matter

The session URL itself is a link that reopens the context of a conversation with Claude. The problem is that it keeps accumulating in a project's public commit history, without the user's consent. The issue author explained that having teammates and open-source contributors see this link at the bottom of every commit and PR looks unprofessional and clutters up the history. Whether it's a company repository or an open-source project, a commit log is both a record of the code and a record of collaboration — and not many teams would welcome a personal session link automatically getting inserted into that record.

Three fixes the open-source community is asking for

The issue lays out three concrete alternatives. The first is a full switch to opt-in. The issue author suggested it would be ideal to ask once during onboarding, with something like: "Include a link back to this Claude session in commit messages?" The second option keeps the current default-on (opt-out) behavior, but makes it clearly visible at the time of the first commit and adds a "don't add this again" button. The third would remove the session URL entirely and rely solely on the Co-Authored-By: Claude trailer that Claude Code already adds to commits as the way to mark contribution.

All three proposals share the same core idea: instead of the current silent insertion, let users know the link is being added and give them a choice.

What Claude Code is right now

Claude Code, built by Anthropic, is a coding agent tool that runs in the terminal and in IDEs. This session URL issue is just one item on that list, but because the tool is so widely used, even a single change to default behavior ends up leaving a trace across a huge number of developers' repositories.

It hasn't been officially confirmed how Anthropic will respond to this issue, or whether and when any changes will be made.

Editor's take

This isn't really about a single feature — it's about who owns the output that AI coding tools produce. Commit messages are a permanent record that lives alongside the code, and having an external service link slip into that record without the user's knowledge effectively means the tool is leaving its own fingerprint on the user's work. Anthropic might see this as an attention (user acquisition) channel, but from a developer's perspective, it can't help but feel like their repository has been turned into a billboard.

We've seen a similar pattern before. As AI coding tools spread, contribution trailers like Co-Authored-By: Claude became something of an industry norm — but that was accepted, at least in part, because it's explicitly visible within the commit itself and follows a standardized format. A session URL is different in that it's a personalized link, and clicking it takes you to a specific conversation session, which raises privacy and security concerns on top of everything else. For an internal codebase, that also means internal discussion context could end up exposed through an external link.

For any team in Korea using Claude Code, there's something worth doing right now: go back through recent commit logs and check whether session URLs have already been slipped in — this matters especially if the repository is public and open source. Internal codebases at least have room to clean up history through a rebase, but commits in open-source repos that have already been forked or cloned are much harder to walk back.

An issue that's drawn over 200 upvotes and made it to Hacker News is too big to quietly ignore, and it seems likely we'll see at least some action along the lines of "stronger opt-out visibility," one of the three proposed fixes. That said, adding an onboarding consent step looks like the more realistic path forward, more so than removing the feature outright.