@leaflow/sdk 0.203.0 → 0.204.0

package/dist/fleet/v1/generated/functions.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
  *
@@ -381,14 +384,16 @@ export declare const getRunMachineCommandUrl: (machineId: string) => string;
  * redirection and `&&` work; there is no terminal and no standard input. The machine admits
  * the account through PAM as for a login. The account is created if the caller has none yet.
  * A command that fails is still a successful request: its exit status is its result.
- * Before starting it, Fleet prepares or reuses the account's ready lightweight graphical
- * session, without starting a full desktop environment. The command has its own job scope;
- * its timeout or exit must not close the account's graphical context.
+ * When the machine reports graphical capability available, Fleet first prepares or reuses
+ * the account's ready lightweight graphical session, without starting a full desktop
+ * environment. Otherwise the command runs without creating a graphical session or injecting
+ * X environment variables. The command has its own job scope; its timeout or exit must not
+ * close an existing account graphical context.
  *
  * Inside the command, `sudo` works without a prompt while the caller has
  * `fleet:machines.admin` on the machine, and refuses otherwise.
  *
- * After graphical context preparation, the request is held until the command ends, at most
+ * After any required context preparation, the request is held until the command ends, at most
  * `timeout_seconds` and a few seconds more. Neither the command nor its output is hidden from the platform: do not put secrets
  * into either.
  *
@@ -396,7 +401,8 @@ export declare const getRunMachineCommandUrl: (machineId: string) => string;
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the command, session or graphical backend is unavailable;
+ * - `FEATURE_UNAVAILABLE` when a required capability is unavailable; an absent graphical
+ *   backend alone does not block a command;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when the account context is not ready or closing;
  * - `USER_NOT_FOUND`, `USER_NOT_ALLOWED`, `ACCOUNT_EXPIRED` or `PAM_PERMISSION_DENIED` when
  *   the machine refuses the account, as for opening a session;
@@ -1355,10 +1361,13 @@ export type createSessionResponse = createSessionResponseSuccess | createSession
 export declare const getCreateSessionUrl: () => string;
 /**
  * Opens a session for the caller on a machine, as the caller's account, and returns once it
- * is ready. With `desktop` the session has a desktop. Without, Fleet first prepares or reuses
- * the account's separate ready lightweight graphical session, then creates a terminal session
- * with its own SID and lifetime; closing that terminal does not close the account context. Its
- * one terminal runs the caller's login shell from the start, every participant attaches to
+ * is ready. With `desktop` the session requires graphical capability and has a desktop.
+ * Without `desktop`, Fleet creates a terminal session with its own SID and lifetime. If
+ * graphical capability is available, Fleet first prepares or reuses the account's separate
+ * ready lightweight graphical session; otherwise the terminal runs without creating a
+ * graphical context or injecting X environment variables. Closing a terminal does not close
+ * an existing account graphical context. Its one terminal runs the caller's login shell from
+ * the start, every participant attaches to
  * that terminal, and the session ends when the shell exits; a caller who wants another
  * terminal opens another session. Either kind also offers programs, files, ports, sound,
  * devices, printers and privilege approvals. The account is created if the caller has none
@@ -1375,7 +1384,8 @@ export declare const getCreateSessionUrl: () => string;
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the machine does not offer sessions or the graphical backend;
+ * - `FEATURE_UNAVAILABLE` when the machine does not offer the requested session capability;
+ *   a terminal-only request does not require a graphical backend;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when its shared account context is not ready or closing;
  * - `USER_HAS_DESKTOP_SESSION` with `desktop` when the account already has a session with a
  *   desktop on the machine, which `metadata.sessionId` names; connect to it instead;

package/dist/fleet/v1/generated/functions.js

@@ -127,14 +127,16 @@ export const getRunMachineCommandUrl = (machineId) => {
  * redirection and `&&` work; there is no terminal and no standard input. The machine admits
  * the account through PAM as for a login. The account is created if the caller has none yet.
  * A command that fails is still a successful request: its exit status is its result.
- * Before starting it, Fleet prepares or reuses the account's ready lightweight graphical
- * session, without starting a full desktop environment. The command has its own job scope;
- * its timeout or exit must not close the account's graphical context.
+ * When the machine reports graphical capability available, Fleet first prepares or reuses
+ * the account's ready lightweight graphical session, without starting a full desktop
+ * environment. Otherwise the command runs without creating a graphical session or injecting
+ * X environment variables. The command has its own job scope; its timeout or exit must not
+ * close an existing account graphical context.
  *
  * Inside the command, `sudo` works without a prompt while the caller has
  * `fleet:machines.admin` on the machine, and refuses otherwise.
  *
- * After graphical context preparation, the request is held until the command ends, at most
+ * After any required context preparation, the request is held until the command ends, at most
  * `timeout_seconds` and a few seconds more. Neither the command nor its output is hidden from the platform: do not put secrets
  * into either.
  *
@@ -142,7 +144,8 @@ export const getRunMachineCommandUrl = (machineId) => {
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the command, session or graphical backend is unavailable;
+ * - `FEATURE_UNAVAILABLE` when a required capability is unavailable; an absent graphical
+ *   backend alone does not block a command;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when the account context is not ready or closing;
  * - `USER_NOT_FOUND`, `USER_NOT_ALLOWED`, `ACCOUNT_EXPIRED` or `PAM_PERMISSION_DENIED` when
  *   the machine refuses the account, as for opening a session;
@@ -1244,10 +1247,13 @@ export const getCreateSessionUrl = () => {
 };
 /**
  * Opens a session for the caller on a machine, as the caller's account, and returns once it
- * is ready. With `desktop` the session has a desktop. Without, Fleet first prepares or reuses
- * the account's separate ready lightweight graphical session, then creates a terminal session
- * with its own SID and lifetime; closing that terminal does not close the account context. Its
- * one terminal runs the caller's login shell from the start, every participant attaches to
+ * is ready. With `desktop` the session requires graphical capability and has a desktop.
+ * Without `desktop`, Fleet creates a terminal session with its own SID and lifetime. If
+ * graphical capability is available, Fleet first prepares or reuses the account's separate
+ * ready lightweight graphical session; otherwise the terminal runs without creating a
+ * graphical context or injecting X environment variables. Closing a terminal does not close
+ * an existing account graphical context. Its one terminal runs the caller's login shell from
+ * the start, every participant attaches to
  * that terminal, and the session ends when the shell exits; a caller who wants another
  * terminal opens another session. Either kind also offers programs, files, ports, sound,
  * devices, printers and privilege approvals. The account is created if the caller has none
@@ -1264,7 +1270,8 @@ export const getCreateSessionUrl = () => {
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the machine does not offer sessions or the graphical backend;
+ * - `FEATURE_UNAVAILABLE` when the machine does not offer the requested session capability;
+ *   a terminal-only request does not require a graphical backend;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when its shared account context is not ready or closing;
  * - `USER_HAS_DESKTOP_SESSION` with `desktop` when the account already has a session with a
  *   desktop on the machine, which `metadata.sessionId` names; connect to it instead;

package/dist/fleet/v1/generated/models.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/schemas.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
  *
@@ -311,14 +314,16 @@ export declare const ListMachineEventsQueryParams: zod.ZodObject<{
  * redirection and `&&` work; there is no terminal and no standard input. The machine admits
  * the account through PAM as for a login. The account is created if the caller has none yet.
  * A command that fails is still a successful request: its exit status is its result.
- * Before starting it, Fleet prepares or reuses the account's ready lightweight graphical
- * session, without starting a full desktop environment. The command has its own job scope;
- * its timeout or exit must not close the account's graphical context.
+ * When the machine reports graphical capability available, Fleet first prepares or reuses
+ * the account's ready lightweight graphical session, without starting a full desktop
+ * environment. Otherwise the command runs without creating a graphical session or injecting
+ * X environment variables. The command has its own job scope; its timeout or exit must not
+ * close an existing account graphical context.
  *
  * Inside the command, `sudo` works without a prompt while the caller has
  * `fleet:machines.admin` on the machine, and refuses otherwise.
  *
- * After graphical context preparation, the request is held until the command ends, at most
+ * After any required context preparation, the request is held until the command ends, at most
  * `timeout_seconds` and a few seconds more. Neither the command nor its output is hidden from the platform: do not put secrets
  * into either.
  *
@@ -326,7 +331,8 @@ export declare const ListMachineEventsQueryParams: zod.ZodObject<{
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the command, session or graphical backend is unavailable;
+ * - `FEATURE_UNAVAILABLE` when a required capability is unavailable; an absent graphical
+ *   backend alone does not block a command;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when the account context is not ready or closing;
  * - `USER_NOT_FOUND`, `USER_NOT_ALLOWED`, `ACCOUNT_EXPIRED` or `PAM_PERMISSION_DENIED` when
  *   the machine refuses the account, as for opening a session;
@@ -920,10 +926,13 @@ export declare const ListSessionsQueryParams: zod.ZodObject<{
 }, zod.z.core.$strict>;
 /**
  * Opens a session for the caller on a machine, as the caller's account, and returns once it
- * is ready. With `desktop` the session has a desktop. Without, Fleet first prepares or reuses
- * the account's separate ready lightweight graphical session, then creates a terminal session
- * with its own SID and lifetime; closing that terminal does not close the account context. Its
- * one terminal runs the caller's login shell from the start, every participant attaches to
+ * is ready. With `desktop` the session requires graphical capability and has a desktop.
+ * Without `desktop`, Fleet creates a terminal session with its own SID and lifetime. If
+ * graphical capability is available, Fleet first prepares or reuses the account's separate
+ * ready lightweight graphical session; otherwise the terminal runs without creating a
+ * graphical context or injecting X environment variables. Closing a terminal does not close
+ * an existing account graphical context. Its one terminal runs the caller's login shell from
+ * the start, every participant attaches to
  * that terminal, and the session ends when the shell exits; a caller who wants another
  * terminal opens another session. Either kind also offers programs, files, ports, sound,
  * devices, printers and privilege approvals. The account is created if the caller has none
@@ -940,7 +949,8 @@ export declare const ListSessionsQueryParams: zod.ZodObject<{
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the machine does not offer sessions or the graphical backend;
+ * - `FEATURE_UNAVAILABLE` when the machine does not offer the requested session capability;
+ *   a terminal-only request does not require a graphical backend;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when its shared account context is not ready or closing;
  * - `USER_HAS_DESKTOP_SESSION` with `desktop` when the account already has a session with a
  *   desktop on the machine, which `metadata.sessionId` names; connect to it instead;

package/dist/fleet/v1/generated/schemas.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
  *
@@ -354,14 +357,16 @@ export const ListMachineEventsQueryParams = zod.strictObject({
  * redirection and `&&` work; there is no terminal and no standard input. The machine admits
  * the account through PAM as for a login. The account is created if the caller has none yet.
  * A command that fails is still a successful request: its exit status is its result.
- * Before starting it, Fleet prepares or reuses the account's ready lightweight graphical
- * session, without starting a full desktop environment. The command has its own job scope;
- * its timeout or exit must not close the account's graphical context.
+ * When the machine reports graphical capability available, Fleet first prepares or reuses
+ * the account's ready lightweight graphical session, without starting a full desktop
+ * environment. Otherwise the command runs without creating a graphical session or injecting
+ * X environment variables. The command has its own job scope; its timeout or exit must not
+ * close an existing account graphical context.
  *
  * Inside the command, `sudo` works without a prompt while the caller has
  * `fleet:machines.admin` on the machine, and refuses otherwise.
  *
- * After graphical context preparation, the request is held until the command ends, at most
+ * After any required context preparation, the request is held until the command ends, at most
  * `timeout_seconds` and a few seconds more. Neither the command nor its output is hidden from the platform: do not put secrets
  * into either.
  *
@@ -369,7 +374,8 @@ export const ListMachineEventsQueryParams = zod.strictObject({
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the command, session or graphical backend is unavailable;
+ * - `FEATURE_UNAVAILABLE` when a required capability is unavailable; an absent graphical
+ *   backend alone does not block a command;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when the account context is not ready or closing;
  * - `USER_NOT_FOUND`, `USER_NOT_ALLOWED`, `ACCOUNT_EXPIRED` or `PAM_PERMISSION_DENIED` when
  *   the machine refuses the account, as for opening a session;
@@ -1019,10 +1025,13 @@ export const ListSessionsQueryParams = zod.strictObject({
 });
 /**
  * Opens a session for the caller on a machine, as the caller's account, and returns once it
- * is ready. With `desktop` the session has a desktop. Without, Fleet first prepares or reuses
- * the account's separate ready lightweight graphical session, then creates a terminal session
- * with its own SID and lifetime; closing that terminal does not close the account context. Its
- * one terminal runs the caller's login shell from the start, every participant attaches to
+ * is ready. With `desktop` the session requires graphical capability and has a desktop.
+ * Without `desktop`, Fleet creates a terminal session with its own SID and lifetime. If
+ * graphical capability is available, Fleet first prepares or reuses the account's separate
+ * ready lightweight graphical session; otherwise the terminal runs without creating a
+ * graphical context or injecting X environment variables. Closing a terminal does not close
+ * an existing account graphical context. Its one terminal runs the caller's login shell from
+ * the start, every participant attaches to
  * that terminal, and the session ends when the shell exits; a caller who wants another
  * terminal opens another session. Either kind also offers programs, files, ports, sound,
  * devices, printers and privilege approvals. The account is created if the caller has none
@@ -1039,7 +1048,8 @@ export const ListSessionsQueryParams = zod.strictObject({
  *
  * Fails with:
  * - `MACHINE_OFFLINE` when the machine is not connected and does not connect again in time;
- * - `FEATURE_UNAVAILABLE` when the machine does not offer sessions or the graphical backend;
+ * - `FEATURE_UNAVAILABLE` when the machine does not offer the requested session capability;
+ *   a terminal-only request does not require a graphical backend;
  * - `SESSION_UNAVAILABLE` or `SESSION_CLOSED` when its shared account context is not ready or closing;
  * - `USER_HAS_DESKTOP_SESSION` with `desktop` when the account already has a session with a
  *   desktop on the machine, which `metadata.sessionId` names; connect to it instead;

package/dist/fleet/v1/generated/validators/accountList.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/accountList.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/accountResource.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/accountResource.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/approveEnrollmentRequest.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/approveEnrollmentRequest.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/callMcpToolRequest.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/callMcpToolRequest.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/callMcpToolResponse.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/callMcpToolResponse.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/callToolRequest.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/callToolRequest.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
  *