anyray-connect 0.11.119 → 0.11.126

package/README.md

@@ -126,6 +126,21 @@ share the same managed-tool record. `desktop disconnect` performs an ownership-s
 Use the existing `anyray-connect migrate` command when you want to run the local-history copy
 immediately; setup otherwise queues it automatically.
 
+On a user-facing macOS setup, Connect also points the administrator to Claude Desktop's supported
+**Developer → Configure Third-Party Inference** window. The Anyray connection is already selected
+there. Use **Connectors & extensions** to add and test approved remote MCP URLs, and **Plugins &
+skills** to add approved Git marketplaces. **Apply locally** tests one machine. For Jamf, replace
+the per-user credential-helper path with the stable helper path packaged by IT, then use Claude's
+**Export → .mobileconfig** action. No connector JSON or plist editing is required. The window is
+read-only on an MDM-managed machine, so author and export on an unmanaged staging Mac.
+
+Connector URLs come from Claude's connector directory, the connector vendor, or the customer's
+internal remote MCP service. OAuth client registration comes from that vendor or the customer's
+IdP. Plugin marketplaces come from approved Git repositories; skills come from those plugins or the
+system `org-plugins` deployment. A claude.ai organization connector grant, OAuth token, or account
+session cannot be exported or copied into the third-party profile. Each user authorizes the rebuilt
+connector normally.
+
 The adapters do **not** install a certificate authority, change DNS/NAT, or modify the
 operating-system proxy.
 When a first-party client has no supported endpoint seam, Connect leaves it
@@ -167,9 +182,13 @@ configuration-profile metadata are ignored, matching Claude's reader. On Claude
 and newer, Windows treats an active HKLM policy as the whole configuration and does not merge HKCU
 into it.
 
-The generated fleet artifacts configure inference only; they do not currently install Anyray's
-retrieval MCP through Claude's `managedMcpServers` policy. Treat retrieval coverage as partial unless
-the organization deploys that managed MCP configuration separately.
+The generated fleet artifacts configure inference only. For a complete static macOS policy, use
+Claude Desktop's configuration window to add managed MCP connectors and plugin marketplaces, test
+them, and export the `.mobileconfig`. The local Anyray retrieval registration lives in the user's
+third-party app config and is not automatically included in that export. Treat managed retrieval as
+partial unless the exported policy contains an equivalent tested `managedMcpServers` entry. The CLI
+artifact remains useful for inference-only automation, but it is not a connector catalogue or a
+replacement for Claude's policy editor.
 
 ### Static credential-helper policy