Tracker›Changelog›2026-09-25-conversations-endpoint

Conversation retrieval switches from ? (messages) to /backend-api/conversation/{id} (mapping)

revertedstructure · endpoint2026-09-25-conversations-endpoint

Instrument state: Schema 25 · v2 · Bookmarklet 2.7 · measure · gpt-5-6

Evidence

Before
{
  "path": null,
  "format": "messages"
}
After
{
  "path": "/backend-api/conversation/{id}",
  "format": "mapping",
  "metadata_keys_added": []
}
Breadth
33/33 prompts · global
Modes
instant + thinking
Measuring days
25 Sept 2026 → 26 Sept 2026 · 67 field diffs in events.jsonl
Raw data excerpt (K1-01__instant, 2026-09-25)
{
  "run.conversation_format": "messages"
}

Daily data of 25 Sept 2026 →

Context

endpoint/backend-api-conversation-id field/run-conversation-format

Impact

For tools: Back since 25 Sep 2026: the client calls it FIRST on every load and keeps polling it (replacing stream_status). WARNING for bookmarklets and third-party tools: the mapping does NOT carry the web.run tool message — whoever reads this path sees no search_model_queries. Always prefer the messages version (conversations/{id}).

For visibility: Indirect: tools reading this version falsely report »no search queries« — the search happened, this version just omits it.

Status history

25 Sept 2026observed
26 Sept 2026reverted

Open

Why is the (non-hidden) web.run tool message missing from the mapping — a filter, or a different materialisation date?

Does the singular polling remain the permanent stream_status replacement?