ChatGPT
Overview
The ChatGPT provider enables chat completions, conversation continuity, projects with file context, file attachments, and audio transcription through connected ChatGPT accounts.
Capabilities
| Capability | Supported |
|---|---|
| Chat | Yes |
| Streaming | Yes (SSE) |
| Conversations | Yes |
| Projects | Yes |
| File Attachments | Yes |
| Transcription | Yes |
| Speech Generation | No |
Connection
ChatGPT connections require a session with an access_token. Currently, connections are established via admin session upload. Browser capture is coming soon.
Session Requirements
- Must contain a valid
access_tokenfield - Token must not be expired
- Session is encrypted at rest using Fernet
Session Expiry
ChatGPT sessions expire periodically. When a session expires:
- The connection status changes to
expired - An admin can reconnect by uploading a new session
- Requests to an expired connection return a 503 error
Conversation Behavior
- Continuity: Conversations are continued upstream using conversation IDs and parent message IDs
- Projects: Project conversations use
gizmo_interactionmode for file retrieval - Sticky binding: Conversations stay on the same account they started with
Known Limitations
- Session tokens expire and require periodic reconnection
- No self-service browser capture yet (admin session upload only)
- Rate limits are subject to ChatGPT’s own throttling
Next Steps
- Connecting AI Accounts — How to connect ChatGPT
- Chat Completions API — API reference
- Conversation Continuity — How conversations work