Marketplace plugins unavailable when session working directory is a WSL path (Windows integration)

Title: Marketplace plugins unavailable when session working directory is a WSL path (Windows integration)

Body:

Environment

• Host integration: a Windows-based Claude Code client (product menu shows "Agregar carpeta", "Conectores", "Plugins" — appears to be a specific host/IDE integration, not the bare claude CLI). Not certain of the exact product name from inside the session.
• OS: Windows 10, with WSL2 available.
• A project repo located under a WSL path, containing custom project-level subagents/skills (.claude/agents/*.md, .claude/skills/*).

Observed behavior

1. When the session's working directory root is a native Windows path (e.g. C:\), marketplace plugins/connectors (Product Management, Engineering, Data categories — Slack, Notion, Linear, Asana, Datadog, GitHub, BigQuery, etc.) are visible and usable, but the Agent tool does not discover the project-level custom subagents defined under .claude/agents/*.md in the WSL repo (only built-in agent types are listed).
2. When the session's working directory root is instead set to the WSL path containing the project, the custom subagents from .claude/agents/*.md are discovered correctly — but the marketplace plugin connectors from point 1 no longer appear as available.

Why this looks like a bug rather than expected behavior

Per the Claude Code docs, project subagent discovery is directory-hierarchy-based (expected: needs the session root inside/under the project — this part works as documented). However, marketplace plugin/connector configuration is documented as user/account-level, which should make it independent of the working directory. Observing plugins disappear specifically when the working directory switches to a WSL path — with no corresponding documented limitation — suggests the plugin/connector list may be getting resolved relative to the working directory (or the Windows-vs-WSL filesystem boundary) in this integration, rather than purely from account-level config as documented.

Impact

Forces a choice between using project-specific custom subagents/skills (which need a WSL-rooted session) and marketplace connectors (which currently require a Windows-rooted session), with no documented way to have both in the same session — even though the underlying mechanisms are supposed to be orthogonal (project-level vs account-level).

Ask

Could you confirm whether this is expected/known, or a bug in how the working-directory root affects plugin/connector resolution when it's a WSL path vs a native Windows path?