Knowledge base›Fields›run.conversation_format (mapping | messages)

run.conversation_format (mapping | messages) field/run-conversation-format

Fieldsactive first seen 20 Aug 2026 last seen 6 Oct 2026Occurrence 33 of 33 runs on 6 Oct 2026 · instant + thinking

What it is

A field the extractor sets on ingest: mapping if the conversation came as a node tree from /backend-api/conversation/{id}, messages if it came as a flat array from /backend-api/conversations/{id}. Measured: mapping on 20 Aug 2026, messages on all 33 runs from 21 Aug. The switch is the tracker's first confirmed structure event.

For visibility

No proven effect. The field describes how the client fetches the finished conversation, not how ChatGPT searches or cites. It is the hinge between the two endpoint object pages and the fastest way to detect a format switch.

Structure

{
  "wert": "messages"
}

External sources

mohanadasan-2026-07-14

Change history

22 Aug 2026confirmedConversation retrieval switches from /backend-api/conversation/{id} (mapping) to /backend-api/conversations/{id} (messages)
26 Sept 2026revertedConversation retrieval switches from ? (messages) to /backend-api/conversation/{id} (mapping)
30 Sept 2026confirmedDouble fetch since 25 Sep: the client loads every conversation via BOTH paths — conversation/{id} (mapping, first + polling replacing stream_status) and conversations/{id} (messages). The mapping does NOT carry the web.run tool message with search_model_queries.

Open

Related

/backend-api/conversations/{id} /backend-api/conversation/{id} (mapping — back since 25 Sep) grouped_webpages / search_result_groups