feat: scheduled tasks can run in one thread with a fresh session each run#30326

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Scheduled tasks now support a new thread per run, a continuing conversation in one thread, or a fresh session in one thread. The change adds persistence and execution behavior, MCP scheduling fields, and capability-gated controls in mobile and web settings.

Changes: Scheduled-task thread modes

Layer / File(s)	Summary
Thread-mode contracts and capability packages/contracts/src/scheduledTask.ts, packages/contracts/src/orchestratorMcp.ts, packages/contracts/src/environment.ts, apps/server/src/environment/ServerEnvironment.ts	Contracts define new_thread, continue, and fresh_session. MCP inputs and results include freshSession, and the server advertises thread-mode support.
Persistence and run behavior apps/server/src/persistence/Migrations/079_ScheduledTaskThreadMode.ts, apps/server/src/persistence/Migrations.ts, apps/server/src/persistence/reconcileV2PreviewMigration.test.ts, apps/server/src/scheduledTasks/ScheduledTaskService.ts, apps/server/src/scheduledTasks/ScheduledTaskService.test.ts, apps/server/src/orchestration-v2/runtimeLayer.test.ts	Migration 79 adds thread_mode and assigns continue to rows with a thread. The service persists modes, binds launched threads except in new_thread mode, and sends freshContext for fresh_session runs. Tests cover binding, mode preservation, and task replacement during thread launch.
MCP scheduling behavior apps/server/src/mcp/OrchestratorMcpService.ts, apps/server/src/mcp/OrchestratorMcpService.test.ts, evals/mcp-tool-use/cases/pull-requests.ndjson, apps/server/src/provider/agentContextBudget.json	MCP task creation and updates map freshSession and thread binding to thread modes, and task summaries report fresh-session use. Eval cases cover fresh-session scheduling. The configured MCP tool-list size increases.
Settings controls and draft state apps/mobile/src/features/settings/SettingsScheduledTasksRouteScreen.tsx, apps/mobile/src/features/settings/scheduledTaskDraft.ts, apps/web/src/components/settings/ScheduledTasksSettings.tsx, apps/web/src/components/settings/scheduledTasksSettings.logic.ts, docs/user/project-settings.md	Mobile and web settings show the three destination modes when the server supports them and include threadMode in supported upserts. Drafts default to new_thread or resolve the mode from an existing task. Documentation describes the destination choices.

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Feature

Sequence Diagram(s)

mermaid

1	sequenceDiagram
2	participant Settings as Settings editor
3	participant ScheduledTaskService
4	participant Storage as scheduled_tasks
5	participant Launcher as Thread launcher
6	Settings->>ScheduledTaskService: Upsert with fresh_session mode
7	ScheduledTaskService->>Storage: Save thread mode
8	ScheduledTaskService->>Launcher: Launch thread on first run
9	Launcher-->>ScheduledTaskService: Return thread ID
10	ScheduledTaskService->>Storage: Bind thread ID
11	ScheduledTaskService->>Storage: Read task for next run
12	ScheduledTaskService->>Launcher: Send to bound thread with freshContext true

Possibly related issues

• pingdotgg/t3code#29049 — The settings editor adds a destination picker that can change or clear the scheduled task’s thread binding.
• pingdotgg/t3code#26641 — The settings editor adds destination choices and descriptions for how later runs use a thread.

Suggested reviewers: t3dotgg, maria-rcks

Some scheduled-task destination changes can still produce a different thread behavior than requested. Resolve these transitions before merging unless that risk is explicitly accepted.

Check name	Status	Explanation
Title check	Passed	The title clearly and concisely describes the main change: scheduled tasks can reuse one thread while starting a fresh session for each run.
Description check	Passed	The description clearly explains the problem and implementation, including compatibility behavior, migration details, UI changes, tests, documentation, and a UI screenshot. It does not explicitly prov…
Linked Issues check	Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	Passed	Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description clearly explains the problem and implementation, including compatibility behavior, migration details, UI changes, tests, documentation, and a UI screenshot. It does not explicitly provide scope or approval evidence, and verification details do not state the observed results of focused tests, but the description is mostly complete.

Generate docstrings

• Commit to this branch
• Create a new PR

Generate unit tests (beta)

• Commit to this branch
• Create a new PR