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

Evidence

Before

{
  "path": "/backend-api/conversation/{id}",
  "format": "mapping"
}

After

{
  "path": "/backend-api/conversations/{id}",
  "format": "messages",
  "metadata_keys_added": [
    "is_visually_hidden_from_conversation",
    "rebase_developer_message",
    "story_events"
  ]
}

Breadth

33/33 prompts · global

Modes

instant + thinking

Measuring days

21 Aug 2026 → 22 Aug 2026 · 28 field diffs in events.jsonl

{
  "run.conversation_format": "messages"
}

Daily data of 21 Aug 2026 →

Context

endpoint/backend-api-conversations-id endpoint/backend-api-conversation-id field/run-conversation-format field/metadata-is-visually-hidden-from-conversation field/metadata-rebase-developer-message field/metadata-story-events

Impact

For tools: The retrieval path for a conversation. Since 21 Aug 2026 the valid path; it responds with a paginated messages array instead of the mapping tree of /backend-api/conversation/{id}. Bookmarklets and HAR parsers that check for mapping or the old path get nothing. Pagination via page_info.start_cursor and the before parameter; num_turns max 100 (500 → HTTP 422).

For visibility: No proven effect. Affects tools that read conversations, not a website's discoverability.

Status history

Open

Does the old path /backend-api/conversation/{id} still answer for some accounts? On 20 Aug it was active for us, from 21 Aug no longer. The Lovable quick fix keeps both paths as a fallback.

The messages objects themselves are unchanged (author, content, metadata); only the tree is gone. Will the tree structure ever return?