New fields: continuation_message_id, is_merged_message, logical_answer_prefix_activity, source_message_ids

Evidence

After

{
  "messages_only_keys": [
    "continuation_message_id",
    "is_merged_message",
    "logical_answer_prefix_activity",
    "source_message_ids"
  ]
}

Breadth

1/33 prompts · local

Modes

instant

Measuring days

11 Oct 2026 · 1 field diffs in events.jsonl

{
  "schema_fingerprint.messages_only_keys": [
    "continuation_message_id",
    "exclusive_key",
    "genui_components",
    "has_versions",
    "is_merged_message",
    "logical_answer_prefix_activity",
    "rebase_developer_message",
    "search_model_queries",
    "source_message_ids"
  ]
}

Daily data of 11 Oct 2026 →

Context

field/continuation-message-id field/is-merged-message field/logical-answer-prefix-activity field/source-message-ids

Impact

For tools: Counters like "n messages" must know about the merge: the answer arrived as several messages (source_message_ids) and was merged server-side into ONE. Bookmarklet and app show a notice for it.

For visibility: No direct visibility effect — but evidence that long DIL answers are produced in parts (continuation_message_id).

Status history