Uh oh!
There was an error while loading. Please reload this page.
feat(studio): automation enable/disable switch + live status in the Automations rail - #2240
Merged
Merged
Conversation
…utomations rail The Automations pillar showed only icon+label per flow and no way to turn one on/off — you couldn't tell if an automation was live or stop it without deleting. - Live status dot per flow (green On / gray Off) from GET /automation/_status (engine runtime state: actually enabled + bound). Refetched after publish; degrades silently on older backends; no dot for never-published flows. - Enable/Disable switch in the flow header: flips the flow's `status` (active↔obsolete) + saves the draft; applied on publish (review-before-enable). Pairs with the framework engine gate (obsolete/invalid → not bound). - New engine.studio.auto.* i18n keys (en + zh). Unit-tested (FlowStatusDot) + verified in a live browser (green "On" on every showcase flow; header switch reads "Enabled"). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why (UX eval #6 — automation enable/disable entry + status)
The Automations pillar showed only an icon + label per flow, and no way to turn a flow on or off. So an author couldn't tell whether an automation was live, or stop one without deleting it — the header even said "Off by default · review before enabling", but nothing reflected or controlled it. Companion to framework #2597 (the engine-side status gate +
/automation/_status).What
GET /api/v1/automation/_status. Persistedstatusis intent; this is what's actually enabled + bound to its trigger. Refetched after a publish; degrades silently on an older backend; a never-published flow shows no dot (the amber "unpublished draft" chip covers that).status(active↔obsolete) and saves the draft immediately; the change goes live when the package is published — so "review before enabling" is preserved. Pairs with the framework engine gate (obsolete/invalid→ not bound).engine.studio.auto.*i18n keys (en + zh).Verification
Unit —
FlowStatusDot: enabled → green "On", disabled → "Off", no runtime state → renders nothing, bound-vs-unbound distinguished in the tooltip. app-shell type-check clean (29/29).Live browser — console proxied to a real #2597 backend. The Automations rail shows a green "● On" against every showcase flow, and the header switch reads "Enabled" (green). A flow authored + published as
status:activeshowsenabled:true, bound:truein/automation/_status.![proof: green On badges on every flow + Enabled switch]
🤖 Generated with Claude Code