Eric Zhu 7615c7b83b

Rename to use BaseChatMessage and BaseAgentEvent. Bring back union types. (#6144) ...

Rename the `ChatMessage` and `AgentEvent` base classes to `BaseChatMessage` and `BaseAgentEvent`. 

Bring back the `ChatMessage` and `AgentEvent` as union of built-in concrete types to avoid breaking existing applications that depends on Pydantic serialization. 

Why?

Many existing code uses containers like this:

```python
class AppMessage(BaseModel):
   name: str
   message: ChatMessage 

# Serialization is this:
m = AppMessage(...)
m.model_dump_json()

# Fields like HandoffMessage.target will be lost because it is now treated as a base class without content or target fields.
```

The assumption on `ChatMessage` or `AgentEvent` to be a union of concrete types could be in many existing code bases. So this PR brings back the union types, while keep method type hints such as those on `on_messages` to use the `BaseChatMessage` and `BaseAgentEvent` base classes for flexibility.

2025-03-30 09:34:40 -07:00

..

__init__.py

Add Human Input Mode in AGS (#4210)

2024-11-15 14:51:57 -08:00

connection.py

Rename to use BaseChatMessage and BaseAgentEvent. Bring back union types. (#6144)

2025-03-30 09:34:40 -07:00