@leaflow/sdk 0.0.0-dev.496.g35e57c5 → 0.0.0-dev.500.g2168b0d

package/dist/fleet/v1/generated/validators/toolActivityList.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/toolContent.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/toolContent.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/toolDescriptor.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *
@@ -243,16 +246,13 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
+export declare const toolDescriptorNameMax = 194;
 export declare const ToolDescriptor: zod.ZodObject<{
-    tool: zod.ZodObject<{
-        source: zod.ZodEnum<{
-            builtin: "builtin";
-            mcp: "mcp";
-        }>;
-        name: zod.ZodString;
-        server: zod.ZodOptional<zod.ZodString>;
-    }, zod.z.core.$strict>;
     name: zod.ZodString;
+    source: zod.ZodEnum<{
+        builtin: "builtin";
+        mcp: "mcp";
+    }>;
     title: zod.ZodString;
     description: zod.ZodString;
     input_schema: zod.ZodRecord<zod.ZodString, zod.ZodUnknown>;

package/dist/fleet/v1/generated/validators/toolDescriptor.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *
@@ -243,10 +246,16 @@
  * OpenAPI spec version: 1.0.0
  */
 import * as zod from "zod";
-import { ToolRef } from "./toolRef.zod.js";
+export const toolDescriptorNameMax = 194;
 export const ToolDescriptor = zod.strictObject({
-    tool: ToolRef,
-    name: zod.string(),
+    name: zod
+        .string()
+        .min(1)
+        .max(toolDescriptorNameMax)
+        .describe("The name to call it by. Builtin tools are named computer.*; MCP tools are named\n`<server>__<tool>`, so a name selects exactly one tool."),
+    source: zod
+        .enum(["builtin", "mcp"])
+        .describe("Whether the tool is builtin or comes from an MCP server. For filtering only."),
     title: zod.string(),
     description: zod.string(),
     input_schema: zod.record(zod.string(), zod.unknown()),

package/dist/fleet/v1/generated/validators/toolImage.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/toolImage.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/toolList.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *
@@ -246,15 +249,11 @@ import * as zod from "zod";
 export declare const ToolList: zod.ZodObject<{
     session_id: zod.ZodString;
     items: zod.ZodArray<zod.ZodObject<{
-        tool: zod.ZodObject<{
-            source: zod.ZodEnum<{
-                builtin: "builtin";
-                mcp: "mcp";
-            }>;
-            name: zod.ZodString;
-            server: zod.ZodOptional<zod.ZodString>;
-        }, zod.z.core.$strict>;
         name: zod.ZodString;
+        source: zod.ZodEnum<{
+            builtin: "builtin";
+            mcp: "mcp";
+        }>;
         title: zod.ZodString;
         description: zod.ZodString;
         input_schema: zod.ZodRecord<zod.ZodString, zod.ZodUnknown>;

package/dist/fleet/v1/generated/validators/toolList.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateAccountRequest.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateAccountRequest.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateGroupRequest.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateGroupRequest.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateMachineRequest.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateMachineRequest.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateMcpServerRequest.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateMcpServerRequest.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateMcpServerResponse.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updateMcpServerResponse.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updatePrivilegeAutoApprovalRequest.zod.d.ts

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/dist/fleet/v1/generated/validators/updatePrivilegeAutoApprovalRequest.zod.js

@@ -87,11 +87,14 @@
  * - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
  *   the virtual desktop capability is actually available; MCP is a separate source.
  *
- * A graphical backend does not require a full desktop environment. Terminal logins, commands
- * and MCP server initialization prepare or reuse the account's lightweight graphical context,
- * in addition to their own session or job. Configuration reads and writes do not initialize a
- * server and do not require this preparation. A request that needs a feature the machine does
- * not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
+ * A graphical backend does not require a full desktop environment. When the machine reports
+ * graphical capability available, terminal logins and commands prepare or reuse the account's
+ * lightweight graphical context, in addition to their own session or job. Without graphical
+ * capability, ordinary commands and terminal sessions run without creating a graphical context
+ * or injecting X environment variables. MCP server initialization prepares or reuses a graphical
+ * context; configuration reads and writes do not initialize a server or require this preparation.
+ * A request that needs a feature the machine does not report available fails with
+ * `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
  *
  * ## Directory
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leaflow/sdk",
-  "version": "0.0.0-dev.496.g35e57c5",
+  "version": "0.0.0-dev.500.g2168b0d",
   "description": "Leaflow 平台 API 的 TypeScript SDK",
   "license": "MIT",
   "repository": {