Skip to content

feat(cos): rename per-app overrides to per-app options and clarify the enable toggle - #6116

Merged
atomantic merged 2 commits into
mainfrom
cos/task-mtlyrg04/agent-059ce1e6
Sep 3, 2026
Merged

feat(cos): rename per-app overrides to per-app options and clarify the enable toggle#6116
atomantic merged 2 commits into
mainfrom
cos/task-mtlyrg04/agent-059ce1e6

Conversation

@atomantic

Copy link
Copy Markdown
Owner

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)

  • "Per-app overrides" → "Per-app options" across the task drawer tab, the PerAppOverrideList heading, the Workflow timeline expander + panel label, and the app-tasks section blurb.
    • The drawer tab id stays overrides, so existing ?taskTab=overrides deep links keep resolving — only the label changed.
  • Each row's switch now carries a visible "Enabled" label plus an accessible name and tooltip naming the task, the app, and the current state (feature-ideas enabled for Acme: off"feature-ideas does not run for Acme. Turn on to schedule it for this app."). It previously read Enable feature-ideas for Acme, with no visible label at all.
  • The section subtitle now states the rule outright: an app stays off until you switch it on here, and everything else is optional (Inherit follows the global defaults).
  • Bulk button widened from Enable AllEnable for all apps, with a tooltip.

Edit App → Automation

Same data, viewed per task, so it gets the same treatment:

  • "Task Type Overrides" → "Scheduled Task Options", with a subtitle explaining the toggle.
  • The per-task switch — which previously had no accessible name whatsoever — gains the Enabled label, an accessible name, and a tooltip.
  • Labelled Enabled rather than Run, deliberately: that row already has a Run (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 / taskTypeOverrides keys are untouched on the wire.

Test plan

  • New AppOverrideRow — enabled toggle tests pin the accessible name across both the mobile and desktop render slots (asserted per-slot via getAllByRole, not by index) and verify the toggle enables the task while preserving the app's interval override.
  • Existing TaskConfigDrawer, WorkflowTab, and AutomationTab tests updated to the new labels.
  • npm run lint clean; full client suite green — 10210 passed, 2 skipped, 834 files.

https://claude.ai/code/session_01VNAXigngmBpiD2HJzMWRiz

…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
@atomantic
atomantic merged commit 8b51a1c into main Sep 3, 2026
7 checks passed
@atomantic
atomantic deleted the cos/task-mtlyrg04/agent-059ce1e6 branch September 3, 2026 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant