[BUG] Organization custom desktop extensions no longer appear in the Connectors Directory (browse, search, or detail page)

Summary

Since approximately 2026-08-11, custom desktop extensions uploaded by an organization (Team/Enterprise) no longer appear in the Connectors Directory for that organization's members. Browsing and searching the Directory only returns public connectors, and the extension's own detail page (claude.ai/directory/<extension-id>) renders "This connector doesn't exist or is no longer available." This affects both the Directory inside the Claude Desktop app and claude.ai in a regular browser.

The extension itself is healthy: it is still listed in the organization admin console, previously installed copies keep working, and the org-scoped API still returns it. Only Directory visibility is broken, which removes the discovery/install path for members who don't already have the extension.

Environment

• Claude Desktop 1.28929.0 (macOS) and claude.ai web (Chrome), same behavior on both
• Claude for Work (Enterprise) organization
• Custom desktop extension (.mcpb) uploaded via Organization settings > Connectors > Add > Desktop extension
• Desktop extension allowlist toggle: disabled (default)

Steps to reproduce

1. As an org admin, upload a custom desktop extension in admin settings > Connectors (or use one uploaded earlier). Confirm it shows in the admin Connectors list.
2. As a member of the same organization, open the Connectors Directory (Desktop app: Settings > Connectors > Browse, or claude.ai/directory).
3. Search for the extension by name.
4. Open the extension's direct Directory URL: https://claude.ai/directory/<extension-id>.

Expected

• The org's custom desktop extension appears in Directory browse/search for org members (as it did until ~2026-08-11).
• The direct Directory URL renders the extension's detail page with an install option.

Actual

• Directory search returns only public connectors; the org extension is absent.
• The direct URL shows: "This connector doesn't exist or is no longer available. This may be a custom connector you don't have."

Evidence

• GET https://claude.ai/api/organizations/<org-uuid>/dxt/extensions?limit=500 (as the same user) still returns the extension entry with is_allowlisted: true, is_blocklisted: false, is_internal: true — the backend record is intact.
• Watching network traffic during a full load of claude.ai/directory: the page only fetches the public feed https://api.anthropic.com/api/directory/servers?visibility=commercial,enterprise,gsuite-google... (~657 entries, type: remote and type: local, none org-internal). No org-scoped extensions request is made, so the client has no data source that could surface org-internal entries.
• The admin console page (claude.ai/admin-settings/connectors) does fetch the org feed and lists the extension normally.
• Two users in the same org independently noticed the disappearance within the same few days; the direct Directory link worked for one of them before that.
• Reproduced with a freshly uploaded extension as well: a brand-new minimal test extension uploaded on 2026-08-12/13 appears in the org feed (is_allowlisted: true, is_internal: true) but is equally absent from Directory search, and its detail URL shows the same error. The issue is not specific to one stored entry.

Impact

• Org members without the extension installed can no longer discover or install it from the Directory.
• The Directory appears to be the only documented member-facing discovery path for org custom extensions: the help center article on the desktop extension allowlist (https://support.claude.com/en/articles/12592343) covers only the admin upload/allowlist flow and documents no alternative member install surface. With the Directory not showing org extensions, the org distribution feature is effectively unusable for new installs.
• Workaround: distribute the .mcpb file out of band and drag-install via Settings > Extensions, which bypasses the org distribution flow.

Notes

• This is not a "desktop extensions don't belong in the web Directory" case: public desktop extensions (type: local entries in the public feed, e.g. Zscaler MCP Server) do render in Directory browse and search on both surfaces. Only organization-internal desktop extensions are missing.
• Previously installed copies keep running; this is a visibility/discovery regression, not a runtime one.
• No matching public issue found as of 2026-08-13.