Function Health plugin installs, but connector record is missing and cannot be connected

What version of the Codex App are you using?

• ChatGPT/Codex Desktop: 26.901.51231 (build 8109)
• Bundled Codex runtime: 0.153.4

What platform is your computer?

macOS 26.6.2, arm64

What issue are you seeing?

The public Function Health plugin installs and appears enabled, but its underlying connector cannot be loaded or connected in either the macOS desktop app or ChatGPT on the web.

The desktop UI shows:

• Couldn't load connector
• Could not load this app's connection details. Continue in browser.
• The raw connector identifier instead of the display name:
  asdk_app_6949b36d7c008191b61e56d4ada8cff2

Continuing in the browser does not complete the connection.

Steps to reproduce

1. Open the public Function Health plugin.
2. Select Install plugin.
3. Attempt to connect its required app/connector.
4. Observe that the connector details fail to load.
5. Select Open in browser and retry.
6. Observe that the browser flow also cannot connect.
7. Uninstall the plugin, restart the desktop app, reinstall it, and retry.
8. Observe the same failure.

Expected behavior

Installing Function Health should resolve its connector metadata, offer a working authorization flow, and expose its health/lab tools after connection.

The UI should clearly distinguish:

• plugin installed;
• connector available;
• account authorized;
• connector tools callable.

Actual behavior

• The plugin package is reported as installed and user-enabled.
• Its declared app dependency is reported as installed and user-enabled.
• The underlying app does not appear in the runtime app/installed list.
• app/read for asdk_app_6949b36d7c008191b61e56d4ada8cff2 returns:
  • apps: []
  • missingAppIds: ["asdk_app_6949b36d7c008191b61e56d4ada8cff2"]
• No Function Health or Health tools are exposed to Codex.
• The same connection attempt fails on ChatGPT web.

This looks like a catalog/access mismatch between the Function Health plugin entry and its underlying app record, rather than a local cache or restart issue.

Additional information

• Reinstalling and restarting did not help.
• An exact-issue search found no existing Function Health report.
• Screenshots, account identifiers, health information, session transcripts, and logs are intentionally omitted from this public issue. They can be provided privately to OpenAI staff if needed.

Start by tracing the app/installed and app/read entry points for dependency resolution and connector catalog access, using connector ID asdk_app_6949b36d7c008191b61e56d4ada8cff2. Compare the Function Health plugin dependency with the underlying app record; done means metadata loads, authorization completes in desktop and web flows, and the health tools are exposed.