[FEATURE] Web UI: No persistent user-level settings (e.g. attribution config) across sessions
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
Problem
Claude Code on the web (claude.ai/code) runs ephemeral containers. There is no
persistent user-level settings layer (~/.claude/settings.json equivalent) for
web sessions. Settings like attribution.commit, attribution.pr, and attribution.sessionUrl cannot be configured globally for web users.
The only workarounds are:
- Commit
.claude/settings.jsonto each repo (unacceptable for public repos) - Install the CLI/desktop app (defeats the purpose of the web UI)
Environment
- Claude Code on the web (claude.ai/code)
- No CLI installed
Proposed Solution
Expected behaviour
Web UI users should be able to configure persistent account-level settings
(at minimum attribution and basic behaviour flags) through the claude.ai
interface, equivalent to ~/.claude/settings.json on CLI/desktop.
Alternative Solutions
According to claude itself, there is no alternative solution apart from requesting it here.
This is from claude itself: "Bottom line: The attribution link suppression you want is only fully solvable on CLI/desktop today. The web UI has no equivalent persistent config layer — that's a gap Anthropic hasn't filled yet. If you want to flag it, their issue tracker is at github.com/anthropics/claude-code/issues."
Priority
High - Significant impact on productivity
Feature Category
Configuration and settings
Use Case Example
For example,
- i work on public git repositories
- i would like to tell code universally for all my sessions, to exclude the session link in all commits.
- Our session conversations should remain private and not be commited to public repositories!
Right now i have to remember to manually edit the environment for each new session and copy paste my rules to it, every time!
Additional Context
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗