Describe the bug
Error messages from model API requests (e.g., authentication failures, rate limit errors, provider errors) are being written to rollout/signal files that are intended for session replay and persistence.
Current behavior
When a model request fails, the error details (including potentially sensitive info like API keys in error messages or provider error details) get serialized into the rollout JSONL file. These errors should only be displayed to the user in the UI, not persisted in the session history.
Expected behavior
Model request error messages should be filtered out of the rollout stream. They are transient diagnostic information and should not be part of the permanent session record.
Where to look
crates/core/src/query.rs — model query flow where errors occurcrates/core/src/conversation/records.rs — rollout record types- Signal/event dispatching logic in the execution pipeline
Describe the bug
Error messages from model API requests (e.g., authentication failures, rate limit errors, provider errors) are being written to rollout/signal files that are intended for session replay and persistence.
Current behavior
When a model request fails, the error details (including potentially sensitive info like API keys in error messages or provider error details) get serialized into the rollout JSONL file. These errors should only be displayed to the user in the UI, not persisted in the session history.
Expected behavior
Model request error messages should be filtered out of the rollout stream. They are transient diagnostic information and should not be part of the permanent session record.
Where to look
crates/core/src/query.rs— model query flow where errors occurcrates/core/src/conversation/records.rs— rollout record types