| title | OAI Chat |
|---|---|
| emoji | 🤖 |
| colorFrom | yellow |
| colorTo | gray |
| sdk | gradio |
| sdk_version | 6.14.0 |
| python_version | 3.12 |
| app_file | app.py |
| pinned | false |
| license | mit |
Chat interface based on OpenAI transformer models.
Features:
- Image upload (support for vision via gpt-4-vision)
- Word file (DOCX) upload
- PDF file support (via image rendering & GPT-4V)
- Plaintext file upload
- chat history download
- file download
- example: download an ICS calendar file the model has created for you
- streaming chat
- image generation (via gpt-image-1, aka "ImageGen")
- MCP server support (both remote and local) via configurable registry
- optional UnrestrictedPython execution when
CODE_EXEC_UNRESTRICTED_PYTHON=1
The MCP registry is looked up in the following order:
$OAI_CHAT_MCP_REGISTRYif setmcp_registry.jsonin this repository~/.oai_chat/mcp_registry.json
See mcp_registry.sample.json for an example configuration.
Headers and query parameters may reference environment variables using the env: prefix.
Use "allowed_tools": ["*"] to permit all tools from a server.
For local MCP servers, use the command and args fields to specify how to launch the server. Environment variables can be passed via the env field. For example:
{
"name": "exa_local",
"command": "npx",
"args": ["-y", "exa-mcp-server"],
"env": {
"EXA_API_KEY": "env:EXA_API_KEY"
},
"allowed_tools": ["*"]
}When an MCP tool requires approval, the assistant will notify you in chat.
Reply with y to approve or n to deny the request, optionally adding a comment after the y or n.