AI & Agent Dev Bug Sandbox Back to Radar

Merge_message_runs Raises For ChatMessage Roles And FunctionMessage Names That Differ

The merge_message_runs utility attempts to merge consecutive ChatMessage or FunctionMessage objects based solely on message class, leading to ValueError when their identifying fields (role or name) differ. This violates expected behavior and breaks common message processing pipelines.

highConfidence 92%LangChain Affected Vlangchain-Core 1.6.1

Origin Analysis

merge_message_runs checks only the message type (and special-cases ToolMessage.tool_call_id) but does not verify the identity fields ChatMessage.role and FunctionMessage.name before calling __add__, which rejects merging of chunks with different roles/names.

Run the following Python code: ```python from langchain_core.messages import ChatMessage, FunctionMessage, merge_message_runs chat_messages = [ ChatMessage(role="human", content="first"), ChatMessage(role="assistant", content="second"), ] print(merge_message_runs(chat_messages)) function_messages = [ FunctionMessage(name="search", content="first"), FunctionMessage(name="lookup", content="second"), ] print(merge_message_runs(function_messages)) ``` Both calls raise ValueError.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This change may alter the output structure for users who expected the previous (broken) behavior of raising an error; now it silently separates runs. Regression risk is low, but custom subclasses of BaseMessage with additional required identity fields may still be incorrectly merged. Rollback: if unexpected merging issues appear in other message types, revert this change and extend the field-checking logic to cover those types.