@techsologic/unolock-agent 0.1.34 → 0.1.35

package/README.md

@@ -144,18 +144,24 @@ For host configuration and implementation details, see:
 * [OpenClaw plugin config example](examples/openclaw-plugin-config.json)
 
 For skill-aware agents, start with the skill above.
-For direct agent use, prefer the CLI:
+For direct agent use, prefer the CLI. If `unolock-agent` is already installed, use it directly. Only use `npx -y @techsologic/unolock-agent@latest ...` when the executable is not installed yet. Run the command you need directly.
+
+```bash
+unolock-agent link-agent-key 'https://safe.example/#/agent-register/...' 1
+unolock-agent list-spaces
+unolock-agent list-notes
+unolock-agent list-files
+```
+
+Only if the executable is not installed yet, use the same commands through:
 
 ```bash
 npx -y @techsologic/unolock-agent@latest link-agent-key 'https://safe.example/#/agent-register/...' 1
-npx -y @techsologic/unolock-agent@latest list-spaces
-npx -y @techsologic/unolock-agent@latest list-notes
-npx -y @techsologic/unolock-agent@latest list-files
 ```
 
-Only if a host needs the explicit host-command form, use the same executable with:
+Only if a host needs the explicit host-command form, use:
 
-* Hosts that require this command shape launch `npx -y @techsologic/unolock-agent@latest mcp`.
+* `npx -y @techsologic/unolock-agent@latest mcp`
 * The host writes JSON-RPC to `stdin` and reads JSON-RPC from `stdout`.
 * The `mcp` subcommand starts and uses the local UnoLock runtime automatically.
 * On a fresh host, the first start can take longer because local cryptographic code may need to be compiled or prepared.

package/bin/unolock-agent.js

@@ -7,8 +7,8 @@ const path = require("path");
 const https = require("https");
 const { spawn } = require("child_process");
 
-const PACKAGE_VERSION = "0.1.34";
-const FALLBACK_BINARY_VERSION = "0.1.34";
+const PACKAGE_VERSION = "0.1.35";
+const FALLBACK_BINARY_VERSION = "0.1.35";
 const REPO = "TechSologic/unolock-agent";
 const TOP_LEVEL_USAGE = `usage: unolock-agent [-h] [--version] {link-agent-key,set-agent-pin,list-spaces,get-current-space,set-current-space,list-records,list-notes,list-checklists,get-record,create-note,update-note,append-note,rename-record,create-checklist,set-checklist-item-done,add-checklist-item,remove-checklist-item,list-files,get-file,download-file,upload-file,rename-file,replace-file,delete-file,tpm-diagnose,tpm-check,self-test,mcp} ...
 

package/openclaw-plugin/skills/unolock-agent-access/SKILL.md

@@ -10,15 +10,16 @@ This skill uses the local `unolock-agent` executable on the user's device.
 
 ## Preferred Workflow
 
-1. If `unolock-agent` is not already installed, use `npx -y @techsologic/unolock-agent@latest`.
-2. On a fresh host, allow extra time for the first start.
-3. Ask the user for the one-time Agent Key URL and the PIN together.
-4. Link the key on this device:
+1. If `unolock-agent` is already installed, run that directly. Only use `npx -y @techsologic/unolock-agent@latest` when `unolock-agent` is not installed yet.
+2. Run the `unolock-agent` command you need directly.
+3. On a fresh host, allow extra time for the first start.
+4. Ask the user for the one-time Agent Key URL and the PIN together.
+5. Link the key on this device:
    `unolock-agent link-agent-key '<agent-key-url>' '<pin>'`
-5. List spaces and select the working space when needed:
+6. List spaces and select the working space when needed:
    `unolock-agent list-spaces`
    `unolock-agent set-current-space <space_id>`
-6. Use the normal note, checklist, and file commands for day-to-day work.
+7. Use the normal note, checklist, and file commands for day-to-day work.
 
 ## Main CLI Commands
 
@@ -33,6 +34,8 @@ This skill uses the local `unolock-agent` executable on the user's device.
 ## Key Rules
 
 - give the agent the Agent Key URL and PIN together for first setup
+- if `unolock-agent` is installed, use `unolock-agent ...` directly for CLI commands
+- run the `unolock-agent` command you need directly
 - if a command reports that the PIN is needed, run `unolock-agent set-agent-pin '<pin>'` and retry the original command
 - keep the PIN in UnoLock process memory only
 - if a host explicitly requires the host-command form, use `npx -y @techsologic/unolock-agent@latest mcp`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techsologic/unolock-agent",
-  "version": "0.1.34",
+  "version": "0.1.35",
   "description": "npx wrapper for the official UnoLock Agent release binaries",
   "license": "UNLICENSED",
   "homepage": "https://unolock.ai",

package/skills/unolock-agent-access/SKILL.md

@@ -11,15 +11,16 @@ This skill uses the local `unolock-agent` executable on the user's device.
 ## Preferred Workflow
 
 1. Load this skill if the host supports skills.
-2. If `unolock-agent` is not already installed, use `npx -y @techsologic/unolock-agent@latest`.
-3. On a fresh host, allow extra time for the first start.
-4. Ask the user for the one-time Agent Key URL and the PIN together.
-5. Link the key on this device:
+2. If `unolock-agent` is already installed, run that directly. Only use `npx -y @techsologic/unolock-agent@latest` when `unolock-agent` is not installed yet.
+3. Run the `unolock-agent` command you need directly.
+4. On a fresh host, allow extra time for the first start.
+5. Ask the user for the one-time Agent Key URL and the PIN together.
+6. Link the key on this device:
    `unolock-agent link-agent-key '<agent-key-url>' '<pin>'`
-6. List spaces and select the working space when needed:
+7. List spaces and select the working space when needed:
    `unolock-agent list-spaces`
    `unolock-agent set-current-space <space_id>`
-7. Use the normal note, checklist, and file commands for day-to-day work.
+8. Use the normal note, checklist, and file commands for day-to-day work.
 
 ## Main CLI Commands
 
@@ -34,6 +35,8 @@ This skill uses the local `unolock-agent` executable on the user's device.
 ## Key Rules
 
 - give the agent the Agent Key URL and PIN together for first setup
+- if `unolock-agent` is installed, use `unolock-agent ...` directly for CLI commands
+- run the `unolock-agent` command you need directly
 - if a command reports that the PIN is needed, run `unolock-agent set-agent-pin '<pin>'` and retry the original command
 - keep the PIN in UnoLock process memory only
 - if a host explicitly requires the host-command form, use `npx -y @techsologic/unolock-agent@latest mcp`