@leaflow/sdk 0.0.0-dev.489.g3a7785d → 0.0.0-dev.494.g12e1b53
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/fleet/v1/generated/functions.d.ts +121 -13
- package/dist/fleet/v1/generated/functions.js +123 -8
- package/dist/fleet/v1/generated/models.d.ts +197 -4
- package/dist/fleet/v1/generated/models.js +18 -0
- package/dist/fleet/v1/generated/schemas.zod.d.ts +114 -12
- package/dist/fleet/v1/generated/schemas.zod.js +102 -12
- package/dist/fleet/v1/generated/validators/accountList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/accountList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/accountResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/accountResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/approveEnrollmentRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/approveEnrollmentRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/callMcpToolRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/callMcpToolRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/callMcpToolResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/callMcpToolResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/callToolRequest.zod.d.ts +264 -0
- package/dist/fleet/v1/generated/validators/callToolRequest.zod.js +262 -0
- package/dist/fleet/v1/generated/validators/callToolResponse.zod.d.ts +270 -0
- package/dist/fleet/v1/generated/validators/callToolResponse.zod.js +257 -0
- package/dist/fleet/v1/generated/validators/createGroupMemberRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createGroupMemberRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createGroupRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createGroupRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createMachineRegistrationRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createMachineRegistrationRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createMachineRegistrationResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createMachineRegistrationResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createParticipantRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createParticipantRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createParticipantResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createParticipantResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createPeerConnectionCandidatesRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createPeerConnectionCandidatesRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createPeerConnectionRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createPeerConnectionRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/createSessionRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/createSessionRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/cursorPagination.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/cursorPagination.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/deleteMcpServerParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/deleteMcpServerParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/denyPrivilegeRequestRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/denyPrivilegeRequestRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/desktopOptions.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/desktopOptions.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/desktopState.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/desktopState.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/directoryName.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/directoryName.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/enrollmentResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/enrollmentResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/enrollmentState.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/enrollmentState.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/error.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/error.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/errorStatus.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/errorStatus.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/featureState.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/featureState.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/fieldViolation.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/fieldViolation.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/findEnrollmentByPairingCodeParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/findEnrollmentByPairingCodeParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/findEnrollmentResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/findEnrollmentResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/getPeerConnectionParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/getPeerConnectionParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/groupList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/groupList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/groupResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/groupResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/iceCandidate.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/iceCandidate.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/iceServer.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/iceServer.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listAccountsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listAccountsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listGroupMembersParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listGroupMembersParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listGroupsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listGroupsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listMachineEventsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listMachineEventsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listMachineRegistrationsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listMachineRegistrationsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listMachinesParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listMachinesParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listMcpToolsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listMcpToolsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listPrivilegeAutoApprovalsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listPrivilegeAutoApprovalsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listPrivilegeRequestsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listPrivilegeRequestsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listSessionsParams.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/listSessionsParams.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/listToolsParams.zod.d.ts +267 -0
- package/dist/fleet/v1/generated/validators/listToolsParams.zod.js +265 -0
- package/dist/fleet/v1/generated/validators/machineEventList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineEventList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineEventResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineEventResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineEventType.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineEventType.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineFeature.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineFeature.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineRegistrationList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineRegistrationList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineRegistrationResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineRegistrationResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineRegistrationState.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineRegistrationState.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/machineResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/machineResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpConfigurationFile.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpConfigurationFile.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpConfigurationResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpConfigurationResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpImplementation.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpImplementation.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpServerFailure.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpServerFailure.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpServerResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpServerResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpToolList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpToolList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpToolResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpToolResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpTransport.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpTransport.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/mcpUnavailableServer.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/mcpUnavailableServer.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/migrationStep.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/migrationStep.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/namedIdentity.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/namedIdentity.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/offsetPagination.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/offsetPagination.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/operatingSystem.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/operatingSystem.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/participantList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/participantList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/participantResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/participantResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/peerConnection.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/peerConnection.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/privilegeAutoApprovalList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/privilegeAutoApprovalList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/privilegeAutoApprovalMode.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/privilegeAutoApprovalMode.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/privilegeAutoApprovalResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/privilegeAutoApprovalResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/privilegeDecider.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/privilegeDecider.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/privilegeRequestList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/privilegeRequestList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/privilegeRequestResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/privilegeRequestResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/privilegeRequestState.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/privilegeRequestState.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/publicKey.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/publicKey.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/renewParticipantRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/renewParticipantRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/renewParticipantResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/renewParticipantResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/replaceMcpConfigurationRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/replaceMcpConfigurationRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/rtcConfiguration.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/rtcConfiguration.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/runCommandRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/runCommandRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/runCommandResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/runCommandResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/sendMcpRequestRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/sendMcpRequestRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/sendMcpRequestResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/sendMcpRequestResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/sessionCloseReason.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/sessionCloseReason.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/sessionList.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/sessionList.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/sessionMode.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/sessionMode.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/sessionResource.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/sessionResource.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/sessionState.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/sessionState.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/signedMessage.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/signedMessage.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/signingKey.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/signingKey.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/toolActivityList.zod.d.ts +251 -0
- package/dist/fleet/v1/generated/validators/toolActivityList.zod.js +253 -0
- package/dist/fleet/v1/generated/validators/toolContent.zod.d.ts +263 -0
- package/dist/fleet/v1/generated/validators/toolContent.zod.js +260 -0
- package/dist/fleet/v1/generated/validators/toolDescriptor.zod.d.ts +263 -0
- package/dist/fleet/v1/generated/validators/toolDescriptor.zod.js +258 -0
- package/dist/fleet/v1/generated/validators/toolImage.zod.d.ts +258 -0
- package/dist/fleet/v1/generated/validators/toolImage.zod.js +255 -0
- package/dist/fleet/v1/generated/validators/toolList.zod.d.ts +276 -0
- package/dist/fleet/v1/generated/validators/toolList.zod.js +257 -0
- package/dist/fleet/v1/generated/validators/toolRef.zod.d.ts +257 -0
- package/dist/fleet/v1/generated/validators/toolRef.zod.js +257 -0
- package/dist/fleet/v1/generated/validators/updateAccountRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/updateAccountRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/updateGroupRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/updateGroupRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/updateMachineRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/updateMachineRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/updateMcpServerRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/updateMcpServerRequest.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/updateMcpServerResponse.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/updateMcpServerResponse.zod.js +9 -5
- package/dist/fleet/v1/generated/validators/updatePrivilegeAutoApprovalRequest.zod.d.ts +9 -5
- package/dist/fleet/v1/generated/validators/updatePrivilegeAutoApprovalRequest.zod.js +9 -5
- package/dist/proto/leaflow/fleet/control/v1/control_pb.d.ts +24 -2
- package/dist/proto/leaflow/fleet/control/v1/control_pb.js +1 -1
- package/dist/proto/leaflow/fleet/session/v1/session_pb.d.ts +8 -0
- package/dist/proto/leaflow/fleet/session/v1/session_pb.js +1 -1
- package/dist/proto/leaflow/fleet/tool/v1/tool_pb.d.ts +683 -0
- package/dist/proto/leaflow/fleet/tool/v1/tool_pb.js +205 -0
- package/dist/proto/leaflow/fleet/virtualdesktop/capture/v1/capture_pb.d.ts +21 -1
- package/dist/proto/leaflow/fleet/virtualdesktop/capture/v1/capture_pb.js +1 -1
- package/dist/proto/leaflow/fleet/virtualdesktop/datatransfer/v1/datatransfer_pb.d.ts +11 -2
- package/dist/proto/leaflow/fleet/virtualdesktop/datatransfer/v1/datatransfer_pb.js +1 -1
- package/dist/proto/leaflow/fleet/virtualdesktop/display/v1/display_pb.d.ts +18 -0
- package/dist/proto/leaflow/fleet/virtualdesktop/display/v1/display_pb.js +10 -5
- package/dist/proto/leaflow/fleet/virtualdesktop/input/v1/input_pb.d.ts +8 -0
- package/dist/proto/leaflow/fleet/virtualdesktop/input/v1/input_pb.js +1 -1
- package/dist/proto/leaflow/fleet/virtualdesktop/window/v1/window_pb.d.ts +24 -1
- package/dist/proto/leaflow/fleet/virtualdesktop/window/v1/window_pb.js +1 -1
- package/dist/routes.d.ts +24 -0
- package/dist/routes.js +27 -0
- package/package.json +1 -1
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|
|
@@ -83,11 +83,15 @@
|
|
|
83
83
|
* and remote ones it connects to;
|
|
84
84
|
* - `leaflow.fleet.host.v1`: terminal sessions, with programs, files, ports, sound, devices,
|
|
85
85
|
* printers and privilege approvals;
|
|
86
|
-
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a
|
|
87
|
-
*
|
|
88
|
-
*
|
|
89
|
-
*
|
|
90
|
-
*
|
|
86
|
+
* - `leaflow.fleet.virtualdesktop.host.v1`: sessions with a graphical backend;
|
|
87
|
+
* - `leaflow.fleet.tool.v1`: live session tools. Builtin `computer.*` tools are exposed only while
|
|
88
|
+
* the virtual desktop capability is actually available; MCP is a separate source.
|
|
89
|
+
*
|
|
90
|
+
* A graphical backend does not require a full desktop environment. Terminal logins, commands
|
|
91
|
+
* and MCP server initialization prepare or reuse the account's lightweight graphical context,
|
|
92
|
+
* in addition to their own session or job. Configuration reads and writes do not initialize a
|
|
93
|
+
* server and do not require this preparation. A request that needs a feature the machine does
|
|
94
|
+
* not report available fails with `FEATURE_UNAVAILABLE`, whose `metadata.feature` names it.
|
|
91
95
|
*
|
|
92
96
|
* ## Directory
|
|
93
97
|
*
|