Optional compact incoming agent reports with source-thread navigation

[oc-andrey-zaharov]

Problem

On the latest nightly with orchestration V2, I use a main thread as an orchestrator and have other threads report results back to it. When many workers report back, the incoming messages occupy a lot of vertical space and make the main conversation difficult to scan.

The current presentation already truncates long messages behind "Show full message", but the preview is still a large chat bubble. The attribution says "Sent by another agent", which does not tell me which thread it came from or give me an obvious way to navigate there.

Proposed improvement

Make incoming agent and automation reports compact and traceable:

• Add a setting such as Collapse incoming agent and automation reports. Users can choose compact previews by default or keep the expanded presentation they prefer.
• In compact mode, show a short preview with the complete original message available on expansion. This need not generate an AI summary or change the content delivered to the receiving agent.
• Identify the source thread by name and make it clickable so the user can jump directly to that thread.
• Distinguish messages from another agent/thread from messages triggered by an automation using a clear text label and a small icon. Show the originating automation's name where available.

An illustrative compact row could be: Agent · API review · TICKET-RESULT #123 — ready for review, with controls to expand the report and open its source thread. The exact layout is a design suggestion, not a required implementation.

Why this helps

The main thread remains readable when coordinating many workers, while every report is still available in full. Source attribution also makes it easier to investigate a result without searching through the thread list. A setting preserves the choice for people who prefer expanded reports.

Smallest useful scope

A display preference for incoming non-human reports, compact expandable previews, and source attribution/navigation. This is about presenting existing messages, rather than changing orchestration, delivery, or agent context.

Related

• Let agents message existing sibling threads #7001 concerns messaging between threads; this proposal concerns how incoming messages are displayed to the user.
• [Feature]: Filter sidebar threads by who started them #18045 concerns filtering sidebar threads by who started them; this proposal concerns reports inside the receiving conversation.

I searched issues and Ideas discussions for compact/collapsed incoming reports and source-thread navigation and did not find an exact match.

Prepared with gpt-6.1-sol through the Codex harness in T3 Code, based on the reporting user's nightly experience.