This project provides a pure JavaScript, single-file HTML interface for interacting with OpenAI's ChatGPT API. It's designed for users who want a self-hosted, customizable ChatGPT client without complex backend setups, offering features like conversation management, voice input/output, and extensive configuration options.

How It Works

The application is a client-side implementation, meaning all logic runs within the user's browser. It leverages standard web technologies (HTML, JavaScript) to interact directly with the OpenAI API. Key advantages include its simplicity of deployment (a single HTML file) and its extensive client-side customization, allowing users to tailor the interface and behavior without server-side modifications.

Quick Start & Requirements

• Install/Run: Deploy the index.html file using any HTTP server.
• Prerequisites: A web browser (Chrome-based recommended for voice input), an OpenAI API key, and potentially a reverse proxy for the OpenAI API if direct access is not available or desired.
• Setup: Minimal setup, primarily configuring API keys and endpoints within the web interface or via environment variables.
• Docs: Demo (Note: This link is to the official OpenAI demo, not the project's demo, as the project README does not provide a direct link to its own demo).

Highlighted Details

• Supports conversation search, renaming, deletion, and folder organization.
• Features dark/light mode, PWA support, and API usage display.
• Includes voice input/output (Bing, Azure, system voices) and speech recognition customization.
• Offers optional HTML file encryption for basic security.

Maintenance & Community

The project is maintained by xqdoo00o. The README does not provide links to community channels, roadmaps, or specific contributor information.

Licensing & Compatibility

The project is released under the MIT License. This license is permissive and generally allows for commercial use and integration into closed-source projects.

Limitations & Caveats

The project relies on client-side JavaScript, meaning API keys are exposed in the browser, necessitating secure handling (e.g., using reverse proxies with HTTPS). The README warns against transmitting API keys over HTTP. PWA updates require manual synchronization of the service worker script.