Thread-bound scheduled tasks should optionally use the thread’s current agent/model

[rohitgirdhar]

Problem or use case

I use recurring scheduled tasks attached to existing threads. A schedule
has its own saved agent/model selection, which can differ from the
thread's current selection.

When the schedule fires, it uses its saved selection. If I have switched
the thread to another agent/model, scheduled and manual turns keep
switching between them. I want the schedule to continue work with
whichever agent is currently selected for that thread.

Steps to reproduce

1. Create a recurring scheduled task for an existing thread using model A.
2. Switch the thread to model B and continue working.
3. Let the scheduled task fire.
4. It uses model A instead of following the thread's current selection.

Proposed behavior

Add a "Use thread's current agent/model" option for schedules targeting
an existing thread, ideally as the default for new thread-bound schedules.

Resolve the provider instance, model, and associated model settings when
each scheduled run starts, rather than copying them when the schedule
is created. The scheduled run should not override the thread's selection.

Keep an explicit fixed-agent/model option for users who want it.
Schedules that create new threads can continue requiring their own selection.

Expected result

After switching a thread from A to B, subsequent scheduled runs use B
without requiring me to edit every schedule attached to that thread.

Environment

Orchestrator v2, branch t3code/codex-turn-mapping.
Observed on revision 402205e, updated on 2026-09-27.
Local macOS desktop app connected to a Linux VM server.