Documentation
How it works
Sengpt automates the rendered ChatGPT interface while keeping authentication in Chromium.
A real browser session
Sengpt starts Chromium with a dedicated persistent profile, opens ChatGPT, enters prompts into the visible composer, waits for generation to finish, and copies Markdown from the completed assistant turn.
Authentication stays in Chromium
The original Sengpt client used copied session cookies and private ChatGPT endpoints. This fork keeps sign-in and session data inside the browser profile instead.
Tradeoffs
Browser automation depends on the rendered interface. ChatGPT selector changes, browser challenges, or account limits can interrupt a workflow. For supported application integrations, prefer the official OpenAI API.