Response shape of /backend-api/conversations/{id} changed: +[context_truncation_continuation] −[]

Evidence

After

{
  "keys": [
    "context_truncation_continuation"
  ]
}

Breadth

33/33 prompts · global

Modes

instant + thinking

Measuring days

22 Aug 2026 · 14 field diffs in events.jsonl

{
  "platform.response_shapes./backend-api/conversations/{id}": [
    "async_status",
    "atlas_mode_enabled",
    "blocked_urls",
    "context_scopes",
    "context_truncation_continuation",
    "conversation_id",
    "conversation_origin",
    "conversation_template_id",
    "create_time",
    "current_node",
    "default_model_slug",
    "disabled_tool_ids",
    "gizmo_id",
    "gizmo_type",
    "is_archived",
    "is_do_not_remember",
    "is_read_only",
    "is_starred",
    "is_study_mode",
    "is_temporary_chat",
    "memory_scope",
    "messages",
    "moderation_results",
    "owner",
    "page_info",
    "pinned_time",
    "plugin_ids",
    "safe_urls",
    "sugar_item_id",
    "sugar_item_visible",
    "title",
    "update_time",
    "voice"
  ]
}

Daily data of 22 Aug 2026 →

Context

endpoint/backend-api-conversations-id field/conversations-id-context-truncation-continuation

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?