@alwith/module-computer 0.6.4 → 0.6.6
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/README.md +21 -0
- package/dist/index.d.ts +1 -1
- package/dist/index.js +1 -1
- package/native/darwin-arm64/artifact.json +1 -1
- package/native/darwin-arm64/libalwith_native_computer.dylib +0 -0
- package/native/linux-x64/artifact.json +1 -1
- package/native/linux-x64/libalwith_native_computer.so +0 -0
- package/native/win32-x64/alwith_native_computer.dll +0 -0
- package/native/win32-x64/artifact.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -120,6 +120,27 @@ its pure `dump-docs --type mcp` registry export. Tool names, descriptions, schem
|
|
|
120
120
|
and action annotations come from that executable rather than application copies.
|
|
121
121
|
Metadata discovery neither captures the desktop nor starts a control daemon.
|
|
122
122
|
|
|
123
|
+
The injected instructions govern only the `alwith_computer` channel. Users may choose
|
|
124
|
+
Hasgard or other desktop interaction tools under those tools' own authorization and
|
|
125
|
+
operating rules. Enabling this channel does not make it exclusive. A refusal or revoked
|
|
126
|
+
grant must not be silently bypassed by switching tools.
|
|
127
|
+
|
|
128
|
+
Session attachment does not request computer use. Within this channel, the injected instructions limit
|
|
129
|
+
model-initiated tool discovery, resource enumeration, Skill reading, and live
|
|
130
|
+
observations to tasks that require the desktop or GUI interaction. Ordinary chat,
|
|
131
|
+
code and file work, settings questions, and attached-image analysis do not trigger
|
|
132
|
+
computer preflight checks. MCP initialization and tool-catalog handshakes remain
|
|
133
|
+
part of the connection; execution permission remains application-wide.
|
|
134
|
+
|
|
135
|
+
The gateway also advertises MCP resources and serves the bundled host integration
|
|
136
|
+
guide at `skill://cua-driver/SKILL.md`. `resources/list` enumerates that fixed
|
|
137
|
+
resource; `resources/templates/list` returns an empty list; `resources/read` returns
|
|
138
|
+
its Markdown plus the compiled driver version and profile. The native driver has
|
|
139
|
+
no resource endpoint, so these requests are handled by the shared gateway rather
|
|
140
|
+
than forwarded to an execution process. Unknown resource URIs return `-32002`;
|
|
141
|
+
invalid parameters return `-32602`. Resource reads remain available while execution
|
|
142
|
+
is disabled or faulted and never acquire desktop ownership.
|
|
143
|
+
|
|
123
144
|
Only computer calls acquire desktop ownership, check the current application grant
|
|
124
145
|
and system permissions, and open an execution transport for the current Driver.
|
|
125
146
|
Disabling access revokes execution admission before stopping every native Driver
|
package/dist/index.d.ts
CHANGED
|
@@ -27,7 +27,7 @@ export interface ComputerMcpServer {
|
|
|
27
27
|
}>;
|
|
28
28
|
}
|
|
29
29
|
export declare const COMPUTER_SERVER_NAME = "alwith_computer";
|
|
30
|
-
export declare const COMPUTER_INSTRUCTIONS = "Computer
|
|
30
|
+
export declare const COMPUTER_INSTRUCTIONS = "These rules apply only to the alwith_computer channel. Users may choose Hasgard or other desktop interaction tools; follow their choice and each tool's own authorization and operating rules. Enabling alwith_computer does not make it the exclusive desktop interaction tool. Computer access through alwith_computer is an application-wide capability available to every conversation. Enabling it grants permission; it is not a request to use the computer. Decide from the user's current task whether observing the live desktop or interacting with a GUI is necessary. Only when the task requires computer use should you discover alwith_computer tools or read its driver Skill. For ordinary conversation, reasoning, coding, local file work, or tasks that can be completed with other relevant tools, do not discover computer tools, enumerate computer resources or resource templates, read skill://cua-driver/SKILL.md, check computer connectivity, list apps or windows, or capture the screen as a startup check or preflight. A question about computer settings or an attached screenshot alone does not require live computer access. Tool availability and an enabled grant are not reasons to probe the computer.\n\nWhen using the alwith_computer channel for a task that requires computer use, discover the private MCP server named alwith_computer before acting. When get_app_state is available, use the app-oriented tools: get_app_state starts app use and returns its key-window screenshot and accessibility tree; act using that app identity and the returned element indices or screenshot coordinates. Group independent actions against a stable layout in one host turn, awaiting them sequentially. Do not run alwith_computer desktop actions concurrently. Prefer set_value for an editable field when supported. Do not poll get_app_state after each action: stable grounded actions can follow without another snapshot; refresh after navigation, layout changes, modal transitions or an action error, and verify the completed sequence. Actions report dispatch, not verified completion. For a required computer task on a driver without get_app_state, read skill://cua-driver/SKILL.md from alwith_computer and use its window-oriented tools and element tokens. The host handles conversation ownership, queuing and preview. Respect driver refusals and explicit input delivery modes. Access through alwith_computer is disabled until the user enables it in the application. If an alwith_computer call fails or its access is revoked, stop actions through that channel and report the tool error. Never replay an action whose outcome is unknown. Do not silently switch tools to bypass an alwith_computer refusal or revoked access. Users may independently authorize and choose another desktop interaction tool. Ask the user to enable or reconnect alwith_computer only when that channel is needed.";
|
|
31
31
|
export declare function computerContext(resolve: () => Promise<ComputerConnection | null>): Promise<{
|
|
32
32
|
mcpServers: ComputerMcpServer[];
|
|
33
33
|
appendSystemPrompt?: string;
|
package/dist/index.js
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
var r="alwith_computer",
|
|
1
|
+
var r="alwith_computer",n="These rules apply only to the alwith_computer channel. Users may choose Hasgard or other desktop interaction tools; follow their choice and each tool's own authorization and operating rules. Enabling alwith_computer does not make it the exclusive desktop interaction tool. Computer access through alwith_computer is an application-wide capability available to every conversation. Enabling it grants permission; it is not a request to use the computer. Decide from the user's current task whether observing the live desktop or interacting with a GUI is necessary. Only when the task requires computer use should you discover alwith_computer tools or read its driver Skill. For ordinary conversation, reasoning, coding, local file work, or tasks that can be completed with other relevant tools, do not discover computer tools, enumerate computer resources or resource templates, read skill://cua-driver/SKILL.md, check computer connectivity, list apps or windows, or capture the screen as a startup check or preflight. A question about computer settings or an attached screenshot alone does not require live computer access. Tool availability and an enabled grant are not reasons to probe the computer.\n\nWhen using the alwith_computer channel for a task that requires computer use, discover the private MCP server named alwith_computer before acting. When get_app_state is available, use the app-oriented tools: get_app_state starts app use and returns its key-window screenshot and accessibility tree; act using that app identity and the returned element indices or screenshot coordinates. Group independent actions against a stable layout in one host turn, awaiting them sequentially. Do not run alwith_computer desktop actions concurrently. Prefer set_value for an editable field when supported. Do not poll get_app_state after each action: stable grounded actions can follow without another snapshot; refresh after navigation, layout changes, modal transitions or an action error, and verify the completed sequence. Actions report dispatch, not verified completion. For a required computer task on a driver without get_app_state, read skill://cua-driver/SKILL.md from alwith_computer and use its window-oriented tools and element tokens. The host handles conversation ownership, queuing and preview. Respect driver refusals and explicit input delivery modes. Access through alwith_computer is disabled until the user enables it in the application. If an alwith_computer call fails or its access is revoked, stop actions through that channel and report the tool error. Never replay an action whose outcome is unknown. Do not silently switch tools to bypass an alwith_computer refusal or revoked access. Users may independently authorize and choose another desktop interaction tool. Ask the user to enable or reconnect alwith_computer only when that channel is needed.";async function a(t){let e=await t();if(!e)return{mcpServers:[],revision:"disabled"};return{mcpServers:[{type:"stdio",name:"alwith_computer",command:e.command,args:[...e.args],env:e.env.map((o)=>({...o}))}],revision:e.generation,appendSystemPrompt:"These rules apply only to the alwith_computer channel. Users may choose Hasgard or other desktop interaction tools; follow their choice and each tool's own authorization and operating rules. Enabling alwith_computer does not make it the exclusive desktop interaction tool. Computer access through alwith_computer is an application-wide capability available to every conversation. Enabling it grants permission; it is not a request to use the computer. Decide from the user's current task whether observing the live desktop or interacting with a GUI is necessary. Only when the task requires computer use should you discover alwith_computer tools or read its driver Skill. For ordinary conversation, reasoning, coding, local file work, or tasks that can be completed with other relevant tools, do not discover computer tools, enumerate computer resources or resource templates, read skill://cua-driver/SKILL.md, check computer connectivity, list apps or windows, or capture the screen as a startup check or preflight. A question about computer settings or an attached screenshot alone does not require live computer access. Tool availability and an enabled grant are not reasons to probe the computer.\n\nWhen using the alwith_computer channel for a task that requires computer use, discover the private MCP server named alwith_computer before acting. When get_app_state is available, use the app-oriented tools: get_app_state starts app use and returns its key-window screenshot and accessibility tree; act using that app identity and the returned element indices or screenshot coordinates. Group independent actions against a stable layout in one host turn, awaiting them sequentially. Do not run alwith_computer desktop actions concurrently. Prefer set_value for an editable field when supported. Do not poll get_app_state after each action: stable grounded actions can follow without another snapshot; refresh after navigation, layout changes, modal transitions or an action error, and verify the completed sequence. Actions report dispatch, not verified completion. For a required computer task on a driver without get_app_state, read skill://cua-driver/SKILL.md from alwith_computer and use its window-oriented tools and element tokens. The host handles conversation ownership, queuing and preview. Respect driver refusals and explicit input delivery modes. Access through alwith_computer is disabled until the user enables it in the application. If an alwith_computer call fails or its access is revoked, stop actions through that channel and report the tool error. Never replay an action whose outcome is unknown. Do not silently switch tools to bypass an alwith_computer refusal or revoked access. Users may independently authorize and choose another desktop interaction tool. Ask the user to enable or reconnect alwith_computer only when that channel is needed."}}export{n as COMPUTER_INSTRUCTIONS,r as COMPUTER_SERVER_NAME,a as computerContext};
|
|
Binary file
|
|
Binary file
|
|
Binary file
|