[Feature]: Show newest direct agents first in the Agents panel

[amitray007]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/web

Problem or use case

The right-side Agents panel keeps direct subagents in first-seen order, so every newly spawned agent is appended to the bottom of the Direct spawns list.

In a long-lived thread with many subagents, the newest and usually most relevant agent can land below the visible area. I have to scroll past older agents whenever a new one starts, and it is easy to miss the new row entirely.

Proposed solution

Show direct agents in reverse creation order: newest first.

A newly spawned direct agent should appear at the top of the Direct spawns list. Existing rows should otherwise remain stable as their status and activity change; an older agent receiving a progress update should not jump above a newer agent.

Workflow groups and the ordering of members inside workflows should remain unchanged.

Why this matters

The Agents panel is primarily a live observability surface. Putting the newest spawn first keeps current work visible without requiring the user to follow the bottom of a growing historical list.

This is especially helpful for long-running threads that repeatedly delegate work to new subagents.

Smallest useful scope

Reverse the first-seen ordering of direct agents in the web/desktop Agents panel and add a focused regression test.

No new setting, server change, persistence change, workflow reordering, or mobile work is needed.

Alternatives considered

• Sort by latest activity. This would keep active work near the top, but rows could move repeatedly while agents report progress.
• Automatically scroll to the bottom. This would reveal a new agent but can move the user away from the row they are currently inspecting.
• Clear inactive agents. Issue [Feature]: Let the Agents panel clear settled and idle agents #5918 addresses accumulated inactive history, but clearing is a separate action and does not make a newly spawned row immediately visible.

Risks or tradeoffs

This reverses the established visual order, which may surprise users accustomed to oldest-first ordering. Keeping the sort based only on the initial spawn time avoids ongoing row churn after insertion.

Examples or references

• feat: native subagent & workflow observability #5219 introduced the Agents right-panel surface.
• [Feature]: Let the Agents panel clear settled and idle agents #5918 describes live agents becoming buried under older history, though it proposes clearing inactive agents rather than newest-first ordering.

Contribution

• I would be open to helping implement this.