[Bug]: Scheduled task editors don't expose all stored config (thread binding, runtime/interaction modes, model options)

[ImBIOS]

Problem

ScheduledTaskUpsertInput (packages/contracts/src/scheduledTask.ts:260-279) stores user-configurable fields that the Settings editors don't all expose:

• threadId (bound thread, MCP bindToCurrentThread / boundThreadId in packages/contracts/src/orchestratorMcp.ts:659-684, mapped in apps/server/src/mcp/OrchestratorMcpService.ts:262,1961-1984,2036-2056)
• modelSelection incl. options (reasoning/effort etc.)
• runtimeMode (approval-required / auto-accept-edits / auto / full-access)
• interactionMode (default / plan)
• workspaceStrategy, projectId, schedule, title/prompt/enabled (these are covered)

Web (apps/web/src/components/settings/ScheduledTasksSettings.tsx):

• Destination (threadId) is read-only display only (ScheduledTaskDestination:1135-1165, used at 1469-1471). Draft holds threadId:144 and saves it through (1348), but there is no control to bind/unbind/pick a thread.
• Draft holds runtimeMode:150 / interactionMode:151 and saves them (1351-1352), but there is no picker for either.
• Model picker (1569-1586) picks instance+model only; provider options (reasoning etc.) have no control on main.

Mobile (apps/mobile/src/features/settings/SettingsScheduledTasksRouteScreen.tsx, scheduledTaskDraft.ts:199-213, ScheduledTaskPickerScreens.tsx:91-101):

• No Destination display at all (only threadId: draft.task?.threadId ?? null:792 preserved on save). Web shows it, mobile doesn't.
• ScheduledTaskDraft has runtimeMode (editable via model-picker screen) but no interactionMode field; save preserves with draft.task?.interactionMode ?? "default":804. No UI for interactionMode anywhere.
• Webhook signature secret can be set on web but mobile only shows a note about desktop/web.
• Thread binding cannot be changed on either client (both preserve stored threadId).

So bindToCurrentThread/boundThreadId exist in MCP + server + contract, and the web UI displays the bound thread, but neither editor lets the user change the binding, and runtimeMode (web) / interactionMode (both) have no controls despite being stored and used at run time (apps/server/src/scheduledTasks/ScheduledTaskService.ts:909-911).

Steps to reproduce

1. Create a thread-bound scheduled task over MCP (schedule_task with bindToCurrentThread:true) or observe an existing bound task.
2. Open Settings / Scheduled tasks / Edit on web: Destination shows the thread (read-only), no way to unbind/rebind; no Permissions / Plan-mode control; model picker has no reasoning/options control.
3. Open the same task in the mobile editor: no Destination row at all; Model screen has Runtime but no Plan-mode / interaction control; saving preserves threadId/interactionMode silently.

Expected behavior

Every user-configurable field in ScheduledTaskUpsertInput is either editable in both Settings editors or explicitly display-only with a reason:

• thread binding: show bound thread on both clients, allow unbind (and ideally pick/rebind).
• runtimeMode: editable on web (mobile already has it via model picker).
• interactionMode: editable (or explicitly hidden with justification) on both.
• modelSelection.options: editable on web (mobile + MCP already have it).

Actual behavior

Fields are silently preserved: web threadId/runtimeMode/interactionMode round-trip without controls; mobile threadId/interactionMode round-trip without display/controls; web model options have no control on main.

Related

• [Bug]: schedule_task can't set model or reasoning effort, and silently ignores modelSelection #16833 (MCP can't set model/effort) + open PRs fix(server): agents can choose the model for a scheduled task #19143 / fix(server): scheduled tasks created over MCP can set their model and effort #23566 (MCP target) + feat(web): scheduled tasks can set a reasoning level #25864 (open, web reasoning via TraitsPicker — covers web model options).
• [Bug]: bindToCurrentThread is described to agents as always defaulting to true #16185 (bindToCurrentThread default wording), Disable thread-bound schedules when the destination is archived or deleted, and bound delivery retries #24519 / fix(server): pause scheduled tasks bound to archived threads #11635 (bound-task lifecycle).
• No open issue specifically tracks Settings UI parity for thread binding + runtime/interaction modes; filing this as the tracker.

Area

apps/web

Impact

Minor bug or occasional failure

Version or commit

main @ 37d7615

Environment

Source inspection + grep on worktree; no live repro beyond reading stored drafts.

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

[antropos17]

A useful regression case is opening an existing full-access task on mobile, changing only its title, and checking the saved runtime mode, thread binding and model options. Displaying an effective-permissions summary before save would also make silently retained authority visible while the editors gain parity. This is a proposed check, not a reproduced bug. AI-assisted feedback.