[FEATURE] Make session URL attribution use a settings toggle

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

Preflight checklist

• [x] I searched existing issues and feature requests.

• [x] This is related to #66504, but the current workaround doesn't fix the usability problem

• [x] This is a single feature request.

Problem

Claude Code currently adds session URLs to commit messages and pull request content by default in applicable sessions.

You can disable it with:

{

"attribution": {

"sessionUrl": false

}

}

But the issue is that you have to manually add this configuration to repositories and don't have a simple toggle in Claude Code settings.

If I don't want session URLs to be added to my commits or pull requests, surely I should be able to open settings, disable it once and be done with it.

Session URL attribution should also be OFF BY DEFAULT.

A feature that modifies Git history and public GitHub content should not silently enable itself and wait for the user to discover the problem after the fact.

Previous issue

This was already brought up in #66504:

[FEATURE] Session URL appended to commit messages and PR descriptions by default — should be opt-in

Which was closed because attribution.sessionUrl: false exists.

But that doesn't solve the problem. The problem isn't that technically there's some way to disable this, it's that there's no reason or context for using it and users will end up finding out too late that session URLs were silently committed to Git history.

The discussion on that issue also touches on this exact point. The feature is hard to discover if you don't know about it, but can have lasting consequences if you find out after you've already pushed a commit.

Requested behavior

Please:

1. Add an easy session URL attribution toggle to Claude Code settings

1. Make session URL attribution OFF by default

1. Keep repository-level configuration as an optional override

Session URL attribution should be something that users deliberately enable and not find out about too late after it's been committed to Git history

Proposed Solution

Proposed solution

Add a normal Claude Code setting like:

Session URL attribution

Include links to Claude sessions in commits and pull requests

[ Off ]

That can be toggled on/off in the normal Claude Code settings interface and doesn't require editing JSON files or repositories for users to get rid of session URLs.

That setting should then apply to any future Claude Code work unless the user changes it again.

Repository-level configuration can still exist for people who want to override their normal preference for a particular project.

Make it off by default

The default value should be:

Session URL attribution: OFF

For people who want session links, they can go in and turn it on.

This is a safer default because session URLs affect persistent external content like commit messages.

If Anthropic doesn't want to disable session URLs by default, at minimum they should prompt the user with:

Include Claude session URLs in commits and pull requests?

• No

• Yes

But that shouldn't be the default behavior to silently enable it.

Why this matters

Commit messages are persistent.

If Claude added a session URL and pushes the commit, turning the setting off after-the-fact won't undo the fact that the URL was already published.

That's different than a harmless UI preference. The current workflow can be:

1. User starts working with Claude Code

1. Session URL attribution is already enabled

1. Claude creates commits or GitHub content with session URLs

1. User finds out later

1. User has to search for how to disable them

1. User discovers a JSON setting

1. User has to make sure it's present anywhere they don't want session URLs

1. User has to delete entire repo or contact Github Support which doesn't help for session URL's in PR's

That's backwards. The user should make the choice to include a session URL in their commits before Claude pushes anything.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_