feat(cos): rename per-app overrides to per-app options and clarify the enable toggle - #6116
Merged
Merged
Conversation
…e run toggle
The per-app section of a scheduled task read as "overrides," which made its
toggle look like an "apply my overrides" flag rather than what it is: the
switch that decides whether the task runs for that app at all. Every other
control on the row is inert until it is on.
- Rename the surface to "Per-app options" — the task drawer tab, the
PerAppOverrideList heading, the Workflow timeline expander and panel
label, and the app-tasks section blurb. The drawer tab id stays
`overrides` so existing ?taskTab= deep links keep resolving.
- Label the row switch "Run" and give it an accessible name and tooltip
naming the task, the app, and the current state ("Run feature-ideas for
Acme: off"), replacing the ambiguous "Enable feature-ideas for Acme".
- Spell the toggle's meaning out in the section subtitle, and widen the
bulk button from "Enable All" to "Enable for all apps".
- Apply the same treatment to Edit App -> Automation, which shows the same
data per task: "Task Type Overrides" becomes "Scheduled Task Options"
with a subtitle, and its previously unlabelled per-task switch gains the
same "Run" label, accessible name, and tooltip.
Claude-Session: https://claude.ai/code/session_01VNAXigngmBpiD2HJzMWRiz
The app-side Automation row already has a Run button that triggers the task now, so labelling the on/off switch beside it Run put two controls with opposite meanings under one word. Enabled names the state the switch actually holds, and the tooltip still spells out what turning it on or off does to the schedule. Claude-Session: https://claude.ai/code/session_01VNAXigngmBpiD2HJzMWRiz
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 free
to 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.
Summary
The per-app section of a scheduled task was called "Per-app overrides", which made its toggle read like an "apply my overrides" flag. It is not — it is the switch that decides whether the task runs for that app at all, and every other control on the row is inert until it is on.
This renames the surface and makes the toggle say what it does.
Per-app options (CoS → Schedule / Workflow)
PerAppOverrideListheading, the Workflow timeline expander + panel label, and the app-tasks section blurb.overrides, so existing?taskTab=overridesdeep links keep resolving — only the label changed.feature-ideas enabled for Acme: off→ "feature-ideas does not run for Acme. Turn on to schedule it for this app."). It previously readEnable feature-ideas for Acme, with no visible label at all.Inheritfollows the global defaults).Enable All→Enable for all apps, with a tooltip.Edit App → Automation
Same data, viewed per task, so it gets the same treatment:
Enabledlabel, an accessible name, and a tooltip.Enabledrather thanRun, deliberately: that row already has aRun(trigger-now) button, and two controls under one word with opposite meanings is worse than the ambiguity being fixed. A comment at the site records why.No behavior, data-shape, or API change — the persisted
appOverrides/taskTypeOverrideskeys are untouched on the wire.Test plan
AppOverrideRow — enabled toggletests pin the accessible name across both the mobile and desktop render slots (asserted per-slot viagetAllByRole, not by index) and verify the toggle enables the task while preserving the app's interval override.TaskConfigDrawer,WorkflowTab, andAutomationTabtests updated to the new labels.npm run lintclean; full client suite green — 10210 passed, 2 skipped, 834 files.https://claude.ai/code/session_01VNAXigngmBpiD2HJzMWRiz