claude-code - 💡(How to fix) Fix [FEATURE] Claude Desktop user preferences don't apply to Claude Code

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

User preferences set in the Claude Desktop app's settings UI do not apply to Claude Code sessions, even when Claude Code is launched from within the same desktop app on the same machine. This forces users to maintain duplicate preferences in two surfaces.

Root Cause

Expected behavior

Preferences set in Claude Desktop (tone, explanation style, memory-consent rules, collaboration patterns) should automatically apply to Claude Code sessions on the same machine, because from a user's perspective both products live inside the same desktop app.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Summary

User preferences set in the Claude Desktop app's settings UI do not apply to Claude Code sessions, even when Claude Code is launched from within the same desktop app on the same machine. This forces users to maintain duplicate preferences in two surfaces.

Expected behavior

Preferences set in Claude Desktop (tone, explanation style, memory-consent rules, collaboration patterns) should automatically apply to Claude Code sessions on the same machine, because from a user's perspective both products live inside the same desktop app.

Actual behavior

Claude Code reads only its own files (~/.claude/CLAUDE.md, project-level CLAUDE.md, project memory). Desktop UI preferences are stored separately and never reach the Claude Code system prompt. A user's stated preferences (e.g. "always ask before writing to memory", "lead with concept-first explanations") have no effect on Claude Code behavior unless duplicated manually into ~/.claude/CLAUDE.md.

Impact

  • Confusing UX: same brand, same desktop app, two memories.
  • Preferences drift over time as users update one surface and forget the other.
  • New users assume preferences are universal and are surprised when Claude Code ignores them.

Suggested fixes (any one would help)

  1. Claude Code reads Claude Desktop's user preferences automatically when running on the same machine.
  2. The Desktop preferences UI offers a one-click "Apply to Claude Code" / "Export to ~/.claude/CLAUDE.md" action.
  3. At minimum: surface the gap clearly in the Desktop preferences UI ("These preferences apply to chat only — Claude Code uses ~/.claude/CLAUDE.md").

Environment

  • macOS, Claude Desktop app, Claude Code CLI.

Proposed Solution

Suggested fixes (any one would help)

  1. Claude Code reads Claude Desktop's user preferences automatically when running on the same machine.
  2. The Desktop preferences UI offers a one-click "Apply to Claude Code" / "Export to ~/.claude/CLAUDE.md" action.
  3. At minimum: surface the gap clearly in the Desktop preferences UI ("These preferences apply to chat only — Claude Code uses ~/.claude/CLAUDE.md").

Alternative Solutions

No response

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

No response

Additional Context

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Preferences set in Claude Desktop (tone, explanation style, memory-consent rules, collaboration patterns) should automatically apply to Claude Code sessions on the same machine, because from a user's perspective both products live inside the same desktop app.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING