A new tab on the icon rail gives recurring agent work its own home. Every scheduled task across the
fleet is listed with its schedule, run mode, health, and history — the "cron dashboard" for Orq.
Inspired by Synara's automation modes and durable failure thresholds.
Screen 1 · Automations list + run history
orqosorq-vps3
SessionsActive 5Archived 31
Billing usage-plan migration
orq-os 2h
Flaky e2e triage
storefront 5h
Weekly burn report
automation 1d
Marketing copy refresh
storefront 3d
Sidecar lane sweep tuning
market-sidecar 4d
Automations
4 enabled · 1 disabled
Automation
Schedule
Mode 2
Runtime
Last run
Next run
Nightly dependency audit
repo · orq-os
Daily 03:30
30 3 * * *
Standalone
claude · fable-5
6h ago · 4m 12s
Tomorrow 03:30
PR babysitter
session · Billing usage-plan migration
Every 30 min
*/30 * * * *
Heartbeat
claude · fable-5
12m ago · 38s
in 18 min
Usage burn report
own thread · Weekly burn report
Weekdays 07:00
0 7 * * 1-5
Dedicated
omx · gpt-5.5
Yesterday 07:02 · 2m 51s
Mon 07:00
Preview env smoke check
repo · storefront
Hourly
0 * * * *
Standalone
codex · gpt-5.5
22m ago · failed
3 2 of 3 consecutive failures — disables after 1 more
in 38 min
Weekly changelog draft
own thread
Sun 18:00
0 18 * * 0
Dedicated
omx · gpt-5.5
Auto-disabled after 3 failures
—
4
Run history — PR babysitter
heartbeat → Billing usage-plan migration
Today 14:3038s12.4k tokChecks green on #412 — merged, closed the tracking itemview in session →
Today 13:0044s9.3k tokRe-requested review on #409 after force-push from CI botview in session →
1 New icon-rail tab — automations get the same standing as Sessions and Usage.
2 Three run modes borrowed from Synara: Standalone (fresh session per run), Heartbeat (runs inside an existing session you own), Dedicated (owns its own long-lived session).
3 Durable failure threshold — consecutive failures are tracked, the automation auto-disables at the limit, and re-enabling is an explicit human action.
4 Per-run history with duration, token cost, a one-line outcome, and a jump link into the session transcript that produced it.
Screen 2 · Create automation
New automation
Preview env smoke check
Hit the storefront preview URL, run orq-browser-check with the QA manifest, and file one summary message. If anything fails, include the failing request log.
Standalone
Fresh session per run. Clean context, repo checked out each time.
Heartbeat
Runs inside a session you pick. You keep the thread; runs appear as cards.
Dedicated
Creates and owns its session. History accumulates in one place.
0 * * * *
✓ Hourly, on the hour — next run 15:00 (your timezone)
storefront
Codex · gpt-5.5 · effort medium
− 3 consecutive failures +
☑ Push on failure☐ Push on every run☑ Weekly digest
1 Mode cards make the Synara trichotomy self-explanatory at creation time.
2 Cron input with live human-readable preview in the viewer's timezone.
3 Failure threshold is set up-front, mirroring Synara's durable consecutive-failure counter.