Problem
When running debug.py in interactive debug mode, log messages from background tasks (e.g. httpx, memory queue) are printed directly to the terminal, interleaving with the conversation display. This makes it hard to follow the dialogue between the user and the agent.
Additionally, langgraph internally creates an unparameterised Runtime(), which triggers a Pydantic serializer warning that adds further noise to the terminal output.
Expected Behavior
The interactive terminal should only display user input and agent responses. Diagnostic logs and framework-level warnings should be kept separate from the conversation view.
Problem
When running
debug.pyin interactive debug mode, log messages from background tasks (e.g. httpx, memory queue) are printed directly to the terminal, interleaving with the conversation display. This makes it hard to follow the dialogue between the user and the agent.Additionally, langgraph internally creates an unparameterised
Runtime(), which triggers a Pydantic serializer warning that adds further noise to the terminal output.Expected Behavior
The interactive terminal should only display user input and agent responses. Diagnostic logs and framework-level warnings should be kept separate from the conversation view.