Omniscio

Rename a cron group header

How to override the label a group of cron jobs shows in the Cron Jobs view and its sidebar without renaming the project itself — the pencil on the group header, the 80-character limit, what the override does not touch, and how orphaned labels are cleaned up.

On this page

What it is

The Cron Jobs view groups jobs two ways — By Project (each group header shows the project's name) or By Frequency (each group header shows the cadence: hourly, daily, every-6-hours, etc.). In project mode, the group header label can feel wrong: a project called "My Company Reporting" shows up as a long sidebar header, you may want it to read "Reporting" or "Omniscio" inside the cron view without renaming the project everywhere else, and orphan UUIDs from soft-deleted projects sometimes briefly surface as group headers before the next prune sweep cleans them up.

Group rename lets you override the label that the cron view uses for any project group without touching the project's real name. The override is local to your install (lives in settings.cronGroupLabels), applies in both the Cron Jobs view (CronDashboard.tsx) and the Cron Jobs sidebar (CronJobsSidebar.tsx), and is automatically reset back to the canonical project name when you clear it. Frequency-mode headers are not renameable — those labels are derived from the cron expression itself and renaming hourly to "every hour" would just confuse the next reader.

Where to find it

The control lives in the Cron Jobs view — Omniscio's Cron Jobs virtual project in the sidebar — and in the smaller cron sidebar attached to a session that owns cron jobs. In both places the jobs are grouped either By Project or By Frequency, and the rename affordance appears only in the By Project grouping, as a small pencil at the right edge of a group header when you hover it.

How it behaves

How to use it

  1. Open the Cron Jobs view or sidebar. Either the Cron Jobs virtual project in the Omniscio sidebar, or the cron sidebar attached to a session that has cron jobs.
  2. Switch to By Project mode. The segmented By Project / By Frequency control at the top of either surface controls grouping. Rename only appears in By Project.
  3. Hover the group header. A small pencil icon fades in at the right edge of the row when you hover. The icon is also focus-revealed for keyboard users — Tab to the group header's row, then Tab again to the rename trigger.
  4. Click the pencil. The header label is replaced by an inline text input pre-filled with the current label (the project name or whatever you previously renamed it to). The input auto-focuses and selects the existing text, so just type to overwrite.
  5. Save with Enter (or click outside). Pressing Enter, or blurring the input by clicking elsewhere, commits the new label. Pressing Esc cancels without saving.
  6. Reset by saving an empty value. To go back to the canonical project name, open the rename input, clear it (or just press Enter on whitespace), and commit. The override is removed and the header reverts to project.name. Saving the same value as the live label also resets — there's no way to "save the current value as an override".

The label is clamped to 80 characters and trimmed before save. Anything longer is silently truncated. The "Unassigned" group (jobs whose project no longer exists) is also renameable using the same flow, in case you want to label your orphan jobs as "To triage" or similar.

What it doesn't do

  • Doesn't rename the project itself. Other Omniscio views — the sessions sidebar, project switcher, breadcrumbs, settings — all keep showing the real project.name. To rename the project everywhere, use the project's three-dot menu → Edit → Name.
  • Doesn't sync across machines. Overrides are per-install. If you use Omniscio on a desktop and a laptop, you'll need to rename groups on each.
  • Doesn't apply in By Frequency mode. Frequency labels (hourly, daily, weekly, etc.) are derived and never overrideable. The pencil icon is hidden in frequency mode by design.
  • Doesn't survive project deletion. When you delete a project (three-dot → Delete), Omniscio drops any cron group label override keyed by that project id as part of the cascade — so the override map stays in lockstep with the live project set. There's no "ghost label" left behind for an undelete to recover.

How cron jobs are created and edited in the first place is on the create a cron job with AI page. What happens when one of them fails is on the cron failure alerts page, and the session Omniscio can start to repair a broken job automatically is on the cron self-healing page.

Last verified 2026-09-23