[Feature]: Add model options and custom recurrence to Scheduled Tasks

[yoonpooh]

Problem or use case

When creating a Scheduled Task, I can select a model, but I cannot configure its additional options, such as fast mode or reasoning effort.

I would also like to define a custom recurring schedule. For example, I want a single task to run twice every day, at 09:00 and 19:00.

Proposed solution

1. Support model-specific options

   • Expose options such as fast mode and reasoning effort when supported by the selected provider and model.
   • Save these options with the task and apply them to every scheduled run.

2. Support custom recurrence

   • Allow multiple daily run times within a single task.
   • For example: every day at 09:00 and 19:00.
   • Clearly display the time zone used by the schedule.

Why this would help

These improvements would let users control the speed and reasoning effort of scheduled runs and manage recurring workflows without creating separate tasks for each run time.

Thank you for considering these improvements!

[X2Borgo]

+1 on the custom recurrence half of this. I hit the same limit today: I want one scheduled task to run at 00:00, 06:00, 12:00 and 18:00. Today a fixed-time task takes a single timeOfDay, so I had to create four tasks that all use the same prompt. An interval of 6 hours is close, but it counts from when the task was created or updated, so it can't be pinned to those clock times.

Smallest change that would cover this and the 09:00 and 19:00 example: let a fixed-time schedule take a list of times of day (timeOfDay: string | string[]), with the existing optional weekdays applying to all of them. Existing single-time tasks would stay valid as they are.

[phev8]

I would also use this: one scheduled task running every day at 09:00, 12:00, and 18:00, with one prompt to maintain and one task to pause or edit. Those uneven gaps cannot be expressed with a single interval.

Building on the multiple-times suggestion above, would maintainers approve a contribution limited to this scope?

• Extend the existing fixed-time schedule to accept multiple times of day, preserving existing single-time tasks.
• Let users add and remove times in the web/desktop and mobile task editors, with the existing weekday selection applying to all times.
• Expose the same configuration through MCP and show all configured times in the schedule summary.
• Keep the existing fixed-time timezone, missed-run, and overlap policies; make the timezone clear in the editor.

The PR would include focused checks for next-occurrence calculation across the configured times and day/week boundaries, duplicate-time validation, daylight-saving behavior, and editing existing single-time tasks, plus before/after UI evidence.

Cron/RRULE support, model options, and changes to scheduler execution policies would stay outside this proposal. The goal is just several explicit daily times on one task.

I would be happy to prepare that focused PR after approval of the direction and scope, as requested by CONTRIBUTING.md. Would this fit the intended scheduling UX, or would you prefer a different approach?

[Post was made by GPT 6.1 Sol in my behalf from T3 code - it captures the essence of what I wanted to say well]