[feat] Present agent revisions as a single history and hide deployment for agents

[ashrafchowdury]

Context

Agents use one linear revision history, but the playground exposed the branching variant and deployment UI used by prompt applications. This let users create variants, view environment badges, and access deployment actions that do not belong in the agent workflow.

Changes

Agent playgrounds now present revisions through a compact History picker. The picker removes the variant grouping, search field, deployment badges, and unused tree indentation while keeping the standard branching selector unchanged for other workflow types.

Before:

• Revisions appeared under a persisted variant.
• The commit modal allowed saving as a new variant.
• Deployment actions appeared in the header and commit flow.
• Registry appeared in the agent navigation.

After:

• Revisions appear as one flat v1, v2, v3 timeline.
• Agent commits always append a new version, including when a stale branching mode is supplied.
• Agent commit and header actions no longer expose deployment.
• Registry remains available for prompt applications but is hidden for agents.

The shared selector defaults to branching behavior, so prompt applications and evaluators keep their existing revision and deployment flows.

What to QA

• Open an agent playground with multiple revisions. The header shows History, and the dropdown displays a compact flat revision list without variant names, search, environment badges, or excessive side spacing.
• Edit an agent and commit the change. The modal identifies the agent, offers only a new version, and does not show deployment options.
• Confirm the agent configuration header has no Deploy action and the agent navigation has no Registry entry.
• Regression: open a prompt application playground. Variant grouping, search, deployment badges, deployment actions, and Registry navigation should behave as before.

Previews

Featuring the default variant as history

No deployment options as it has no use for now

No create as new variant option

Note: The word history was my creative choice for the product, we can change it

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agenta-documentation	Ready	Preview, Comment	Jul 13, 2026 12:01pm

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch reframe-variant-as-history-and-hide-deoloyment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ashrafchowdury]

I think we can show the commit message in a tooltip, or somehow; it would be nice to have it

[ardaerzin]

@ashrafchowdury we can make list items 2 line, and leave the bottom line for a more meaningful commit message. other than that 👍

[ashrafchowdury]

fixed

[ashrafchowdury]

@mmabrouk, if this chagnes make sense to you, let's ship this

It makes sense to me, not having variants and showing the base variant as linear type history

[mmabrouk]

@ashrafchowdury the idea make sense, but we need to think about it holistically, this fixes the playground while keeping the registry view the same. This is not consistent. We need a solution that is consistent.