I’d like to suggest exposing the current conversation’s own identity to the ChatGPT runtime.
At the moment, a ChatGPT conversation can obviously be reopened through a URL such as https://chatgpt.com/c/``<conversation-id>, but the conversation itself does not appear to have access to its own conversation_id or canonical private URL.
In other words, the chat is not self-aware of its own address.
From a developer perspective, it would be useful if the runtime exposed something like conversation_id and canonical_url as session metadata available to the model, or through a first-party action such as get_current_conversation_metadata().
The canonical_url should be the normal authenticated private URL of the conversation, not a public /share/ link.
This would enable very simple and useful workflows without exposing the conversation publicly.
My own use case is personal knowledge management with Obsidian. I often develop essays, research threads and project ideas across many separate ChatGPT conversations. I would like to ask ChatGPT:
“Summarize this conversation as an Obsidian note and include a link back to the original chat.”
The model can already summarize, classify and tag the conversation, but it cannot include a reliable link back to its own source because it does not know its own canonical URL.
This limitation becomes especially noticeable on mobile, where manually retrieving and copying the browser URL is not practical and the Android app only exposes public shared links.
More generally, exposing private conversation metadata would allow:
- knowledge-management integrations;
- provenance links between generated notes and source conversations;
- personal automation workflows;
- references between conversations;
- external indexing without duplicating full conversation content.
The important distinction is that this should not create or expose a public shared link. It should simply make the conversation’s existing private identifier and authenticated canonical URL available to the conversation itself and, optionally, to connected tools.
The underlying conversation id already exists. The request is essentially to expose that identity as first-party metadata.