Tracker›Changelog›2026-10-17-minderheit-endpoint-backend-api-conversation-id

Persistent minority: endpoint /backend-api/conversation/{id} has appeared in a minority of runs for ≥ 3 consecutive days (today 2 of 33) — neither a one-off nor a majority switch

observedstructure · endpoint2026-10-17-minderheit-endpoint-backend-api-conversation-id

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

Evidence

After
{
  "element": "/backend-api/conversation/{id}",
  "anteil": 0.06
}
Breadth
2/33 prompts · local
Modes
instant
Measuring days
17 Oct 2026

Daily data of 17 Oct 2026 →

Context

endpoint/backend-api-conversation-id

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

17 Oct 2026observed

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?