Summary

In Mission Control, clicking on a cron job card does nothing — no detail view opens, no error appears in the console, no network request fires. Cron cards appear non-interactive even though hover states suggest they should be clickable.

Environment

• Version: OpenClaw 2026.5.27 (commit 27ae826)
• Platform: macOS 26.5 (Build 25F71), Apple Silicon
• Gateway: running on 127.0.0.1:18789, loopback
• Surface: Mission Control web UI in desktop browser

Steps to reproduce

1. Open Mission Control at http://127.0.0.1:18789/
2. Navigate to the Cron section (jobs list visible)
3. Click on any cron job card

Expected

The card opens a detail view showing the full job config (schedule, payload, recent runs, etc.) and exposes management actions (run now, enable/disable, edit, remove).

Actual

Nothing happens. The card does not navigate, expand, or open a modal. No console errors.

Reproducibility

• Reproduces for every cron job in the list, not specific to one job.
• Persists after:
  • Hard refresh (⌘+Shift+R)
  • openclaw gateway restart
• All cron jobs themselves work correctly end-to-end via the gateway API — this is purely a UI interaction bug.

Workaround

Cron jobs can still be managed via the cron tool / CLI / API. Mission Control only fails to surface the detail view.

Notes

• All four jobs in the list are affected: a daily memory log, two report-related jobs, and an AI digest delivery.
• Gateway logs show no errors related to UI requests; the click never hits the network.
• Suggests the click handler on CronCard (or equivalent) isn't wired, or a recent route change orphaned the detail-view route.