Claude Desktop 1.52386.6 ignores applied 3p gateway profile (deploymentMode 1p, zero gateway requests)

[JLDynamics]

Setup

• opencodex 2.54.0 (main @ 9f7397e, PR [WRONG BRANCH] release: promote verified 2.54.0 product tree to main #4540)
• macOS arm64, Claude Desktop 1.52386.6
• Proxy healthy on 127.0.0.1:10100; providers openai (default), openrouter, opencode-zen

What was done (per docs)

• Integrations → Claude Desktop toggle ON; dashboard + ocx claude desktop apply
• Profile content verified: 7 routes incl. openrouter/meta/muse-spark-1.3-contributor → claude-opus-4-8-20260202 (Sonnet default), gateway baseUrl http://127.0.0.1:10100
• Fully quit Desktop (Cmd+Q, verified relaunch, PIDs fresh) multiple times

Result

• ocx claude desktop status: applied=true, activeProfile=true, drift=false, policy ok — but health requestCount: 0, lastRequestAt: null
• Desktop process flags show deploymentMode: 1p
• Model picker shows stock native models only (Fable/Opus/Sonnet/Haiku); no gateway labels (e.g. no 'Meta/muse Spark 1.3 Contributor (openrouter)')
• Dashboard reports: 'Integration is on, but Desktop is not using the gateway profile'

Suspected cause

Docs conflict with code on the config path:

• Guide (docs-site/.../guides/claude-code.md 'Claude Desktop profile') says Apply writes to ~/Library/Application Support/Claude/configLibrary and calls Claude-3p legacy / not read. That dir does not exist on this machine.
• Code (src/claude/desktop-3p-paths.ts, ADR-0046) ports the shipped bundle logic (Claude + -3p, app.asar v1.18286.0) and treats Claude-3p as correct — which is where apply actually writes.
• Desktop 1.52386.6 appears to never consult the 3p library (1p mode), so the applied+active profile is dead config on this version.

Ask

1. Which Claude Desktop versions honor the 3p gateway profile? Is 1.52386.6 known-bad?
2. If newer Desktop moved/renamed the profile location or requires a different activation (beyond in-app Save/Apply, which does not exist in this version's Settings), please document it.
3. Consider reconciling the guide's 'legacy 3p' note with the resolver behavior, or detecting at apply-time that the running Desktop will ignore the profile (e.g. warn when deploymentMode is 1p).

Happy to provide full status --json, profile JSON, and Desktop process flags.

[github-actions]

Issue closed: use an issue template

Thanks for taking the time to submit this issue. It was closed automatically because it was not opened with a recognized issue template (Bug report, Feature request, Documentation, or Provider compatibility). Freeform and API-opened issues cannot skip this check.

• This issue does not use a recognized issue template.

Please edit the issue to add:

• Open a new issue with the Bug report, Feature request, Documentation, or Provider compatibility template.
• Or edit this issue so the body uses the template section headings for the kind of report you are filing.

See the Contributing guide for details.

Once the report passes the automated checks, it will be reopened automatically unless a maintainer has changed its state.