Problem
Gateway replies can include a background auxiliary warning after the main response has completed, for example:
⚠ Auxiliary title generation failed: HTTP 401: User not found.
This happened when the non-blocking auto-title generation side task failed in Slack. The title generation failure is not actionable to the end user in the thread and should not be delivered as a chat response.
Expected
Gateway auto-title failures should remain logged for operators/developers, but should not be surfaced as user-visible Slack/gateway messages.
Notes
The CLI can still surface auxiliary title-generation failures if desired; the issue is specifically gateway fire-and-forget title generation after a completed response.
Problem
Gateway replies can include a background auxiliary warning after the main response has completed, for example:
⚠ Auxiliary title generation failed: HTTP 401: User not found.This happened when the non-blocking auto-title generation side task failed in Slack. The title generation failure is not actionable to the end user in the thread and should not be delivered as a chat response.
Expected
Gateway auto-title failures should remain logged for operators/developers, but should not be surfaced as user-visible Slack/gateway messages.
Notes
The CLI can still surface auxiliary title-generation failures if desired; the issue is specifically gateway fire-and-forget title generation after a completed response.