feat(automation): schedule recurring agent tasks

[coygeek]

Summary

Allow users to schedule a saved prompt to run against a selected project and execution environment, with visible run history and controls to pause, edit, and delete the schedule.

Problem to solve

T3 Code can run agents locally or remotely and retain threads, but there is no user-visible way to run a maintenance prompt on a cadence without manually opening a thread and sending it.

Proposed behavior

Provide a schedule editor reachable from the project and thread surfaces. A schedule stores its prompt, project, cadence, execution target, and notification preference; each run creates or updates a clearly linked thread activity record and reports success or failure.

Acceptance criteria

• A user can create, view, edit, pause, resume, run-now, and delete a schedule.
• The editor validates cadence and execution target before saving.
• Runs do not overlap unintentionally; each run exposes start time, terminal state, and a link to its thread output.
• Schedules identify the execution environment and its availability requirements, including whether its T3 Code server must remain running; client disconnection does not imply that execution stopped.
• Web, desktop, and mobile clients show the same schedule state when connected to one server.

Affected area

Server persistence and queue/reactor lifecycle, WebSocket contracts, project and thread settings UI, desktop notifications, and mobile schedule management.

Non-goals

This does not require a hosted multi-tenant scheduler or arbitrary external event triggers in the first version.

Alternatives considered

Documenting shell cron commands leaves schedules disconnected from T3 Code threads, permissions, and run history.

Supporting context

Official OpenAI automation guidance describes scheduled tasks with a project, prompt, cadence, execution environment, notifications, and a Scheduled inbox: https://learn.chatgpt.com/docs/automations. T3 Code already has queue-backed reactors and thread persistence; no schedule editor or schedule contract was found in apps/web/src or apps/server/src at the inspected revision.

Related upstream work: Scheduled Prompts discussion #6748 and recurring runs discussion #11654. Scheduling work also exists in proposed changes such as PR #10706; its existence does not establish availability in the inspected main-branch revision.

Analysis basis: source inspection of T3 Code revision 9d4bb550a658. Statements about missing UI or contracts refer to that revision, not every provider-native capability or unmerged branch. This is a feature proposal based on source review, not a runtime bug reproduction.

[juliusmarminge]

Duplicate of #6748 — that Ideas thread is the canonical tracker for scheduled / recurring prompts and agent tasks (create/edit/pause/run history, cadence, execution environment). Please +1 / comment there so asks stay in one place.

Also see closed duplicate #11654.