[feat] Hide the Deploy button in agent playgrounds

[mmabrouk]

Context

The agent playground showed two publish actions side by side: Commit and a labeled Deploy button. For agents, Deploy is not part of the workflow; Commit is the only publish action that matters there. Mahmoud decided to remove Deploy from the agent playground while keeping it for classic apps.

Changes

The Deploy button in the playground config header now renders only when the entity is not an agent. The check reuses isAgentEffective, the signal the same file already uses to switch the header into agent mode. Since Deploy no longer renders for agents, the agent-only label/type/size override on the button was dead code and is removed; classic apps keep the icon-only Deploy exactly as before. The Commit button is untouched in both modes.

Before: agent playground header shows Commit plus a labeled "Deploy" button.
After: agent playground header shows Commit only. Classic completion/chat playgrounds keep their Deploy button unchanged.

Other DeployVariantButton render sites were checked and left alone: the Registry variants table is not a playground surface, and the embedded drawer path already hides Deploy unconditionally.

Tests / notes

• tsc --noEmit on web/oss: clean apart from one pre-existing unrelated error in agenta-entities/src/session/api/api.ts.
• next lint --fix on the touched file: clean.
• Live-checked on the dev stack: two agent playgrounds show Commit only; the classic Completion playground still opens the Deploy modal.

What to QA

• Open any agent playground. The config header shows Commit but no Deploy button.
• Open a classic Completion or Chat app playground. The Deploy button is still there and opens the deploy modal.
• Regression to watch: the Commit button and the kebab menu in the agent header still work as before.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
agenta-documentation	Error		Aug 11, 2026 2:54pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: b0c8f4e1-8901-41ed-957f-d5314bc91691

📥 Commits

Reviewing files that changed from the base of the PR and between 57f2941 and ff9bd0f.

📒 Files selected for processing (1)

• web/oss/src/components/Playground/Components/PlaygroundVariantConfig/assets/PlaygroundVariantConfigHeader.tsx

🚧 Files skipped from review as they are similar to previous changes (1)

• web/oss/src/components/Playground/Components/PlaygroundVariantConfig/assets/PlaygroundVariantConfigHeader.tsx

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Removed the Deploy button from agent playgrounds.
  • Preserved the icon-only Deploy button for supported non-embedded workflows.

Walkthrough

The playground header no longer shows a Deploy button for agent playgrounds or while agent status loads. Eligible non-embedded, non-evaluator, non-agent workflows retain the icon-only Deploy button.

Changes

Agent playground deployment

Layer / File(s)	Summary
Deployment button visibility web/oss/src/components/Playground/Components/PlaygroundVariantConfig/assets/PlaygroundVariantConfigHeader.tsx	Agent playgrounds and unresolved agent statuses omit deployment controls. The previous agent-specific labeled Deploy configuration was removed. Other eligible workflows retain the icon-only Deploy button.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• Agenta-AI/agenta#4881: Introduced the agent-specific Deploy-button logic modified by this change.
• Agenta-AI/agenta#5251: Removed the agent-specific Deploy button in the same header component.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: hiding the Deploy button in agent playgrounds.
Description check	✅ Passed	The description directly explains the Deploy button change, preserved classic-app behavior, implementation, and validation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/agent-playground-no-deploy

---

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.}

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 66a7c9cb-f88c-43be-8bc9-f89ba792686d

📥 Commits

Reviewing files that changed from the base of the PR and between a9c18ac and 57f2941.

📒 Files selected for processing (1)

• web/oss/src/components/Playground/Components/PlaygroundVariantConfig/assets/PlaygroundVariantConfigHeader.tsx

[github-actions]

Railway Preview Environment

Status	Destroyed (PR closed)

Updated at 2026-08-11T20:07:32.160Z