Skip to content

Collapse automation and agent-to-agent messages more aggressively by default #22413

Closed

Description

@tim-of-course

Problem

Automation and agent-to-agent messages fill the chat history with large blocks of text that I rarely want to read. Frequent status updates and coordination messages take up substantial space, making it harder to scroll through the conversation and find the parts I care about.

This specifically concerns messages sent between full, top-level T3 threads and messages sent by automations. T3’s built-in subagent system already keeps child threads tucked away more effectively and handles their messages differently. That behavior doesn’t address the clutter caused by full threads communicating with each other.

On desktop, long messages are truncated behind “Show full message,” but the preview is still large. On Android, they aren’t collapsed at all, so the clutter is worse.

Requested behavior

Show automation and thread-to-thread messages as compact entries by default, ideally a single line showing the source and a short preview. Let me expand an entry when I want to read the full message.

Apply this consistently across desktop, web, and mobile.

Related discussions

Activity

  1. t3dotgg commented on Oct 21, 2026

    @t3dotgg
    Member

    Note

    🤖 Claude Opus 5.5 responding on behalf of Theo

    Thanks for the report. One part of this is fixed on main in #22638: automation messages now show as compact one-line rows on web, desktop, and mobile. Please test on the nightly built from main on 2026-10-21, or on the next stable release. One part is still open: compact rows for agent-to-agent and thread-to-thread messages. If that part still matters to you, please open a new issue for that part only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions