Skip to content

Commit 31865b7

Browse files
test(server): drive configure continuation through the in-process MCP server
Main now requires the in-process MCP middleware to supply invocation context, and lint rejects issue numbers in comments. AI-assisted; verified with the tests and tools listed above. Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent f219b23 commit 31865b7

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎apps/server/src/orchestration-v2/SelectionRestart.integration.test.ts‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -303,7 +303,7 @@ function makeRestartAdapter(
303303

304304
// An agent that switches its own thread's model through MCP is the running
305305
// turn the switch interrupts, so the configure call must leave behind a
306-
// continuation of the unfinished request (#15300).
306+
// continuation of the unfinished request.
307307
it.live("t3_thread_configure from the running turn continues the user request", () =>
308308
Effect.scoped(
309309
Effect.gen(function* () {
@@ -460,7 +460,7 @@ it.live("t3_thread_configure from the running turn continues the user request",
460460
}).pipe(
461461
Effect.provide(
462462
McpHttpServer.layerThreadToolkit.pipe(
463-
Layer.provideMerge(McpServer.McpServer.layer),
463+
Layer.provideMerge(McpHttpServer.layerInProcessMcpServer),
464464
Layer.provide(NodeCrypto.layer),
465465
Layer.provide(Layer.mock(ThreadSearch.ThreadSearch)({})),
466466
Layer.provide(Layer.mock(ScheduledTaskService.ScheduledTaskService)({})),

0 commit comments

Comments
 (0)