Introduction
Start here with OpenGPT0's Browser/ChatGPT workflow and local permission model.
OpenGPT0 brings a visible ChatGPT browser session into a local coding workflow. The browser page can reason and answer, but local evidence, edits, shell commands, verification, and Git operations stay inside OpenGPT0’s permissioned tool boundary.
The Product Route
The default route is browser/chatgpt. Sign in to ChatGPT in the dedicated
browser profile, then use OpenGPT0 from the desktop app, terminal, or local web
surface. If Browser/ChatGPT is unavailable, OpenGPT0 should show that state
instead of silently falling back to a different provider.
Local Work Stays Explicit
OpenGPT0 separates local work by intent:
- Repository search and file evidence use read-only tools.
- Edits, shell commands, verification commands, and Git operations use coding tools with approval and audit.
- Real choices are asked directly in the UI.
That separation keeps ChatGPT as an untrusted model source while OpenGPT0 owns the local execution path.