Repository navigation
feat(schedules): one Schedules page for every routine, automation schedule and the backup - #535
Conversation
…edule and the backup Lens's crontab: GET/PATCH /api/v1/schedules and POST /run, MCP tools schedules, set_schedule and run_schedule, and an Automate > Schedules page to switch, re-time and run anything on a clock. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
…s before The clicks check found Admin one swipe further down on a phone with a new nav row. Schedules now has Routines' row (the Routines page and New routine open from its top), the routine-create journey goes through it, and isActive marks Schedules on /routines pages. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
|
Clicks and keystrokes per feature is red on the phone run: The fix is ready and validated (jest, tsc, lint, requirements): Schedules takes the row Routines had, the Routines page and New routine open from the top of Schedules (so Generated by Claude Code |
An empty Schedules page had New routine twice (the header and the empty state), which made the routine-create clicks journey's link ambiguous. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
# Conflicts: # fastapi_backend/app/api/mcp_tools.py
# Conflicts: # fastapi_backend/app/api/v1/router.py # nextjs-frontend/app/openapi-client/index.ts # nextjs-frontend/app/openapi-client/sdk.gen.ts
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
… built #400 shipped in v0.15.0, so its In progress line failed make requirements on main. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
|
Clicks and keystrokes per feature failed on b76d632 because of a single journey: This is not caused by this PR, which doesn't touch chat. The same failure, an answer timing out after 60s, hit Generated by Claude Code |
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NwZdhpvjjidN5Y45CLSi8m
Requested by Adeel · project thread
Description
Before: anything that ran on a clock lived on its own page. Routines had their schedule on the Routines page (admins only), an automation's schedule and at triggers were only readable over the API, MCP and chat, and the backup's schedule was in Settings › Backups. There was no one place to see what Lens would do next, or when something last ran.
After: a Schedules page (Automate › Schedules) is Lens's crontab. One list, soonest first, with every routine, every automation schedule or at trigger (one row per trigger) and the backup, each saying when it runs in words and as cron with its time zone, when it runs next, how and when it last ran, and whether it's on. From the row: a switch, "Change when it runs" (presets or a cron of your own, any time zone, the next five times shown before saving, Enter saves; an at trigger takes a new date and time) and Run now (a routine over budget asks first). Someone who isn't an admin sees the schedules of the automations they manage.
Agents get the same list and the same changes:
GET /api/v1/schedules,GET /api/v1/schedules/{id},PATCH /api/v1/schedules/{id}(cron,at,timezone,enabled),POST /api/v1/schedules/{id}/run, and the MCP toolsschedules,set_scheduleandrun_schedule.Motivation and Context
Adeel asked for a "crontab manager": a single view to see and manage every scheduled workflow and routine.
Nothing new is stored: the list is read from the routines, the automations' timers and the backup setting each time, and every change goes through the routine's, the automation's or the setting's own route, so their checks (schedule that never runs, unknown zone, who may change it) and audit log are reused.
Types of changes
!in the title)Checklist:
make hookschecks it on commit).docs/accordingly.## UnreleasedinCHANGELOG.md. (n/a: the title says it; the changelog is generated from titles.)Done questions (AGENTS.md)
ci/local-ci.sh) passed all six jobs; merged on green./api/v1/schedulesand the MCP toolsschedules,set_schedule,run_schedule(test_agents_list_change_and_run_schedules_over_mcp).tests/api/test_schedules.py,schedules-page.test.tsx,schedules-model.test.ts, navigation test), docs (docs/schedules.md, mcp.md, api.md, automations.md, processing.md, requirements.md, README) and the OpenAPI client regenerated withmake openapi/pnpm generate-client.timers.clock_state,backups.schedule_state, the routine schedule preview and presets, and the existing routes for every change.Generated by Claude Code