Install the ChatGPT communication channel with Builder CLI. Builder validates Runtime MCP and OAuth discovery, then leaves only ChatGPT-owned create (with logo), publish, and connect steps.
Users state a business goal in ChatGPT. AI Fabrix Role Assistants return a governed result, question, or completed outcome. ChatGPT does not execute enterprise work or grant authority. See Conversation-first work and Assistant channels.
Prerequisites
- Deliver assistant channels hub read
aifabrix loginand developer workstation ready- ChatGPT workspace admin or owner available
- External Access ChatGPT profile enabled (
miso-chatgpt) with CIMD activated - Runtime MCP reachable so ChatGPT can discover OAuth (CIMD preferred)
Where it lives
| Artifact | Location |
|---|---|
| OAuth2 profile | Controller External Access → OAuth2 profiles → ChatGPT |
| Stable profile URL | /miso/external-access/oauth2-profiles/miso-chatgpt |
| First-run output | Terminal values for the ChatGPT Apps form (Name, Server URL, OAuth) |
| Channel package | Builder output under dist/channels/chatgpt/ after channel add (INSTALL guide) |
| Secrets | OAuth discovered from Runtime — no static ChatGPT API key in the package |
ChatGPT uses the same governed tools as the portal — see External AI and Enterprise MCP. One ChatGPT channel install serves many Role Assistants.
How to set
aifabrix channel add chatgpt --name "Onni"
If Runtime or OAuth discovery is not ready, Builder reports Not ready and a blocker. Open the ChatGPT OAuth2 profile (/miso/external-access/oauth2-profiles/miso-chatgpt): enable it, set Client Registration Mode to CIMD, and confirm CIMD advertised is Yes. Then run the same command again. When ready, Builder prints:
- ChatGPT Apps URL:
https://chatgpt.com/admin/apps - Name
- Description
- Server URL
- Authentication: OAuth
Create the app in ChatGPT with those values. Add the logo during create. ChatGPT does not let you change the logo later. ChatGPT must discover protected-resource metadata, the authorization server, scopes, PKCE, and client registration (CIMD preferred, DCR as fallback). Do not paste a static API key. Do not fill Client ID and secret by hand when discovery advertises CIMD.
Remaining ChatGPT-owned steps:
- Create the app, including the logo.
- Publish and connect the app.
If ChatGPT shows a callback URL that is not already registered:
aifabrix channel configure chatgpt --callback-url "<callback-url>"
Then return to ChatGPT and finish publish and connect. Admin completes Connect assistant channels after the workspace app is live.
Defaults and examples
| Setting | Typical value |
|---|---|
| Target key | chatgpt |
--name |
Customer-visible brand (for example Onni) |
| Server URL | Runtime MCP URL from Builder |
| Authentication | OAuth discovered from Runtime — CIMD preferred; DCR fallback |
| OAuth2 profile | /miso/external-access/oauth2-profiles/miso-chatgpt (miso-chatgpt) |
| Logo | Required at create — cannot change later |
| Product law | One ChatGPT channel install per environment; many Role Assistants |
Do not paste a static API key or connector JSON. Builder prints the live values; copy them into ChatGPT Apps.
Validate
aifabrix channel add chatgpt --name "Onni" --probe
A successful AI Fabrix probe does not replace ChatGPT's own create, publish, and connect steps. If the probe reports not ready, fix Runtime MCP and the ChatGPT OAuth2 profile (enabled, CIMD, callback) before opening ChatGPT Apps.
Common mistakes
| Mistake | Fix |
|---|---|
| ChatGPT profile disabled | Enable ChatGPT at /miso/external-access/oauth2-profiles/miso-chatgpt |
| CIMD not activated | On that profile, set Client Registration Mode to CIMD and confirm CIMD advertised is Yes. Keep chatgpt.com / chat.openai.com on CIMD document hosts |
| ChatGPT callback missing | Register the URL ChatGPT shows: aifabrix channel configure chatgpt --callback-url, or add the Redirect URI on the same profile (seeded: https://chatgpt.com/connector/oauth/callback) |
| Pasting a static API key into ChatGPT | Use OAuth so ChatGPT discovers the authorization server |
| Filling Client ID and secret by hand | Activate CIMD so discovery advertises it (DCR is fallback) |
| One connector per Assistant | Single channel; many Assistants |
| Creating without a logo, then trying to change it | Add the logo when you create the app. ChatGPT does not allow a later logo change |
| Skipping publish / connect | Those remain ChatGPT-owned |
| Opening ChatGPT Apps while Runtime is not ready | Re-run channel add until Builder reports ready |
Limits
ChatGPT create (with logo), publish, and connect remain workspace-admin steps until OpenAI documents a provisioning API. The logo must be set at create time; ChatGPT does not let you change it later. Treat ChatGPT as another channel into the same Operational Trust boundary — not a bypass around Role Assistants.