From c0a88a2529c9c10a7c08088dee8f36045f761846 Mon Sep 17 00:00:00 2001 From: nullStack65 <112618179+nullStack65@users.noreply.github.com> Date: Wed, 18 Nov 2026 10:50:36 +0000 Subject: [PATCH 1/3] feat(settings): ship Closura fleet defaults for linking and provider updates Closura machines link to each other and pin their provider CLIs, but every new install started with Linked environments off, so links and link cards were refused, and with stock provider update checks on. Fleet machines had both set by hand. Make them built-in defaults: Linked environments on, provider update checks off. A machine that already stored a value keeps it. Two tests that relied on the old defaults now set them explicitly. Model: claude-opus-5-5 Task: implementation Agent: Builder Co-Authored-By: Claude Opus 5.5 --- apps/server/src/mcp/McpHttpServer.test.ts | 4 +++- apps/server/src/provider/ModelManifest.test.ts | 5 ++++- docs/user/outside-agents.md | 2 +- docs/user/remote-access.md | 10 +++++----- packages/contracts/src/settings.ts | 10 +++++++--- 5 files changed, 20 insertions(+), 11 deletions(-) diff --git a/apps/server/src/mcp/McpHttpServer.test.ts b/apps/server/src/mcp/McpHttpServer.test.ts index 5801a210ba6c..3c1a9ea49780 100644 --- a/apps/server/src/mcp/McpHttpServer.test.ts +++ b/apps/server/src/mcp/McpHttpServer.test.ts @@ -1604,7 +1604,9 @@ it.effect("hides tools for links and refuses another environment while the beta failureMode: "return", }), ); - const settingsContext = yield* Layer.build(ServerSettings.layerTest()); + const settingsContext = yield* Layer.build( + ServerSettings.layerTest({ linkedEnvironmentsEnabled: false }), + ); const settings = Context.get(settingsContext, ServerSettings.ServerSettingsService); const serverLayer = McpHttpServer.layerMcpTransport( McpHttpServer.toolkitRegistration( diff --git a/apps/server/src/provider/ModelManifest.test.ts b/apps/server/src/provider/ModelManifest.test.ts index 0b4c4c062dca..96220d533ae5 100644 --- a/apps/server/src/provider/ModelManifest.test.ts +++ b/apps/server/src/provider/ModelManifest.test.ts @@ -261,7 +261,10 @@ const layerService = (input: { }) => ServerConfig.layerTest(process.cwd(), { prefix: input.prefix }).pipe( Layer.provideMerge(NodeServices.layer), - Layer.provideMerge(ServerSettings.layerTest(input.settings ?? {})), + // Fetching follows provider update checks, which Closura builds turn off by default. + Layer.provideMerge( + ServerSettings.layerTest({ enableProviderUpdateChecks: true, ...input.settings }), + ), Layer.provideMerge(layerHttpClient(input.response)), ); diff --git a/docs/user/outside-agents.md b/docs/user/outside-agents.md index 84d00cc98b16..96f3f3fcb1f1 100644 --- a/docs/user/outside-agents.md +++ b/docs/user/outside-agents.md @@ -13,7 +13,7 @@ app (MCP)**, or use the button in **Settings → Sharing & access**. Pick the app and follow the step for that app. Assistants like Poke and Claude run in the cloud, so the wizard first asks you to sign in to T3 Connect and turn it on for the environment. To reach your other machines through -the same connection, turn on **Linked environments** in Labs and +the same connection, keep **Linked environments** on in Labs and [link them](./remote-access.md#link-another-environment). When the app opens the sign-in page, choose what it may do and approve with your diff --git a/docs/user/remote-access.md b/docs/user/remote-access.md index 29b7650d4190..c963e22b8d6a 100644 --- a/docs/user/remote-access.md +++ b/docs/user/remote-access.md @@ -357,11 +357,11 @@ Link two machines, such as your laptop and a VPS, and agents on one can work on the other: launch, message, wait on and stop its threads, answer their questions, and manage its queues, projects and scheduled tasks. -Linked environments is a beta. Turn it on for both machines in **Settings → -Labs**; on mobile, **Settings → Labs** lists each connected machine. While it is -off on either machine, agents start nothing over a link between them. A task -already running on the other machine still finishes, and if that machine has it -off, its result arrives once it is back on. +Linked environments is a beta, on by default in Closura builds. It needs to be on +for both machines in **Settings → Labs**; on mobile, **Settings → Labs** lists +each connected machine. While it is off on either machine, agents start nothing +over a link between them. A task already running on the other machine still +finishes, and if that machine has it off, its result arrives once it is back on. On the machine you will work from, open **Settings → Environments → Linked environments**, choose **Link**, and pick the other machine or enter its address. The list diff --git a/packages/contracts/src/settings.ts b/packages/contracts/src/settings.ts index a80361cb12ec..18a2c02a9477 100644 --- a/packages/contracts/src/settings.ts +++ b/packages/contracts/src/settings.ts @@ -1383,7 +1383,10 @@ export const ServerSettings = Schema.Struct({ responseStreamingMode: ResponseStreamingMode.pipe( Schema.withDecodingDefault(Effect.succeed("paragraph" as const)), ), - enableProviderUpdateChecks: Schema.Boolean.pipe(Schema.withDecodingDefault(Effect.succeed(true))), + // Closura: provider CLIs are pinned by the fleet, so stock update checks only add noise. + enableProviderUpdateChecks: Schema.Boolean.pipe( + Schema.withDecodingDefault(Effect.succeed(false)), + ), continueThreadsAfterServerUpdate: Schema.Boolean.pipe( Schema.withDecodingDefault(Effect.succeed(true)), ), @@ -1480,9 +1483,10 @@ export const ServerSettings = Schema.Struct({ guestSharingEnabled: Schema.Boolean.pipe(Schema.withDecodingDefault(Effect.succeed(false))), /** * Beta: links to the user's other machines, both ways. Off refuses new links, calls over links - * and tasks on another machine; tasks already running there finish. + * and tasks on another machine; tasks already running there finish. On by default in Closura + * builds: every fleet machine links to the others. */ - linkedEnvironmentsEnabled: Schema.Boolean.pipe(Schema.withDecodingDefault(Effect.succeed(false))), + linkedEnvironmentsEnabled: Schema.Boolean.pipe(Schema.withDecodingDefault(Effect.succeed(true))), /** Beta: Claude and Codex predict the next prompt after completed turns. Codex follows a change at once; open Claude threads after they restart. */ promptSuggestionsEnabled: Schema.Boolean.pipe(Schema.withDecodingDefault(Effect.succeed(false))), sidebarAutoSettleKeepPullRequests: Schema.Boolean.pipe( From 9a98a654192b569dcaadb120bacf2c7755104bc3 Mon Sep 17 00:00:00 2001 From: nullStack65 <112618179+nullStack65@users.noreply.github.com> Date: Wed, 18 Nov 2026 11:21:35 +0000 Subject: [PATCH 2/3] test(server): follow the Linked environments default in session reload tests These tests flip Linked environments to show that a change reloads tools; with the setting on by default they now flip it off. Model: claude-opus-5-5 Task: fix Agent: Builder Co-Authored-By: Claude Opus 5.5 --- .../src/orchestration-v2/ProviderSessionManager.test.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/server/src/orchestration-v2/ProviderSessionManager.test.ts b/apps/server/src/orchestration-v2/ProviderSessionManager.test.ts index 69375c34a2a6..aa702dc52ed6 100644 --- a/apps/server/src/orchestration-v2/ProviderSessionManager.test.ts +++ b/apps/server/src/orchestration-v2/ProviderSessionManager.test.ts @@ -4817,7 +4817,7 @@ it.effect.each([ yield* resumeSecondThread; assert.equal((yield* Ref.get(state)).resumeCount, ++resumeCount); // regression: #26722 a Linked environments change reloads only the idle thread's tools. - yield* settings.updateSettings({ linkedEnvironmentsEnabled: true }); + yield* settings.updateSettings({ linkedEnvironmentsEnabled: false }); yield* resumeSecondThread; assert.equal((yield* Ref.get(state)).resumeCount, ++resumeCount); assert.deepEqual((yield* Ref.get(state)).unloadedNativeThreadIds, ["native-thread"]); @@ -5534,7 +5534,7 @@ it.effect( assert.equal((yield* Ref.get(state)).openCount, 1); // regression: #26722 an exclusive runtime configures MCP at open, so it reopens. - yield* settings.updateSettings({ linkedEnvironmentsEnabled: true }); + yield* settings.updateSettings({ linkedEnvironmentsEnabled: false }); yield* manager.open({ threadId: firstThreadId, providerSessionId, From f3a4bb29eaa353561a65a2301db65dd10d4c2db6 Mon Sep 17 00:00:00 2001 From: nullStack65 <112618179+nullStack65@users.noreply.github.com> Date: Wed, 18 Nov 2026 11:29:41 +0000 Subject: [PATCH 3/3] docs(user): note provider update checks are off in Closura builds They also gate the model catalog download, so say where to turn them on. Model: claude-opus-5-5 Task: docs Agent: Builder Co-Authored-By: Claude Opus 5.5 --- docs/user/updating.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/user/updating.md b/docs/user/updating.md index 388e9035ca77..966f704285db 100644 --- a/docs/user/updating.md +++ b/docs/user/updating.md @@ -185,7 +185,8 @@ provider at the same CLI. After a successful provider CLI update, T3 Code refreshes model discovery for every enabled instance of that provider using its own configuration. Connected clients receive the refreshed catalogs automatically. Provider update checks -must be enabled to download the latest T3 Code model catalog. +must be enabled to download the latest T3 Code model catalog. Closura builds turn +them off by default; turn them on in **Settings → Maintenance**. Provider updates do not restart running chats. An existing session can keep using the previous CLI until it ends. If discovery fails, check the provider