@devries-cameron20 / t3code-1 / commits / e93f2a5181
Fork 0

The best way to control Claude Code, Codex and more from any computer or phone

fix(server): schedule_task no longer tells agents bindToCurrentThread always defaults to true (#34950)

Co-authored-by: Julius Marminge <julius0216@outlook.com>

Phon committed Nov 12, 2026 at 16:41 UTC e93f2a51816b73109564a197760016d38aa2624d
2 files changed +4 -3
apps/server/src/provider/agentContextBudget.json
+1 -1
@@ -1,5 +1,5 @@
1 {
2 "claudeSystemAppendBytes": 5597,
3 "codexAdditionalContextBytes": 7327,
4 - "mcpToolListJsonBytes": 48130
4 + "mcpToolListJsonBytes": 48126
5 }
packages/contracts/src/orchestratorMcp.ts
+3 -2
@@ -679,13 +679,14 @@ export const OrchestratorMcpScheduleTaskInput = Schema.Struct({
679 enabled: Schema.optional(Schema.Boolean.annotate({ description: "Default true." })),
680 bindToCurrentThread: Schema.optional(
681 Schema.Boolean.annotate({
682 - description: "Default true: runs post in this thread. False: new thread per run.",
682 + description:
683 + "Post here, else new thread per run. Unset: true in own project, else false; updates keep it.",
684 }),
685 ),
686 freshSession: Schema.optional(
687 Schema.Boolean.annotate({
688 description:
688 - "Runs share one thread but each starts a fresh session without earlier runs' context. Unbound: the first run makes the thread.",
689 + "Runs share one thread but each starts a fresh session. Unbound: the first run makes the thread.",
690 }),
691 ),
692 clientRequestId: Schema.optional(OrchestratorMcpClientRequestId),