Hi OpenAI team,
I’m building a local-first browser extension that helps organize ChatGPT conversations into a custom project tree: client → project → subproject → chat. The extension is intended to run locally in the browser and does not need access to message contents through an API.
The main missing piece is a stable read-only way to know basic conversation status, without relying on fragile DOM scraping.
The useful minimal API/events would be something like:
- conversation_id
- last_activity_at
- generation_started
- generation_completed
- has_unread_update
- current_visible_conversation_id
- conversation_updated event
Use case:
A developer or power user can maintain their own local ChatGPT project organizer, link conversations to local project contexts, and see whether a chat is active, updated, or waiting for a response. This would make browser extensions and local productivity tools much more reliable and privacy-friendly.
Why DOM scraping is not ideal:
- ChatGPT UI changes can break extensions.
- It is hard to reliably detect when generation starts or finishes.
- Extensions may need to observe too much page structure just to infer simple status.
- A small read-only status API would be safer, more stable, and easier to build around.
This request is not about reading private message contents via API. The goal is only basic conversation metadata/status, so local organizers and browser extensions can avoid unreliable UI scraping.
I attached a small demo screenshot showing how this kind of organizer could look and where the missing status API would help.
