ToolResultBlock should be part of UserMessage

[cvbhjkl]

Currently in types.py, ToolResultBlock is part of AssistantMessage, but according to the stream-json format output of claude-code version 1.0.25, ToolResultBlock is part of UserMessage, which causes the current ToolResult to not be parsed correctly.

[gohanlon]

I ran into this today, too.

The current definition is:

# Message types
@dataclass
class UserMessage:
    """User message."""

    content: str

In addition to hitting this when using the live SDK, in test_subprocess_buffering.py (lines 190-202), there's a test that expects UserMessage with non-string content:

json_obj = {
    "type": "user",
    "message": {
        "role": "user",
        "content": [
            {
                "tool_use_id": "toolu_016fed1NhiaMLqnEvrj5NUaj",
                "type": "tool_result",
                "content": json.dumps(large_data),
            }
        ],
    },
}

The test then accesses this as a list: messages[0]["message"]["content"][0]["tool_use_id"] (line 230-231).

This indicates that:

1. The CLI can output UserMessage with list content containing tool_result objects
2. The current parser in client.py line 50 may fail when encountering this format
3. The type definition might need to be updated to match the actual CLI behavior

Based on the above referenced test, UserMessage could be:

@dataclass
class UserMessage:
    """User message."""

    content: str | list[ToolResultBlock]

[gohanlon]

This appears to have been fixed in #101 and included in releases since v0.0.18.