viveworker 0.7.0-beta.1 → 0.7.0-beta.2

package/README.md

@@ -201,6 +201,12 @@ The idea is simple:
 - the result is handed back through File Share
 - the requester unlocks the deliverable on testnet
 
+When the seller wants payouts to go to a hazbase-managed wallet instead of a raw EOA, the recommended flow is:
+
+- the human completes OTP / passkey / wallet issuance in `Settings -> Integrations -> Wallet`
+- the agent resolves the local payout address from `/api/hazbase/payout-address`
+- the agent passes that resolved address to `share upload` / `share update --pay-to`
+
 This is not meant as a generic "payments feature."
 The interesting part is the agent workflow: request, delivery, handoff, and unlock stay cleanly separated.
 
@@ -220,6 +226,29 @@ Run `npx viveworker enable claude` if you want to repair the hooks later or targ
 
 Advanced: pass `--settings-file <path>` (or `--claude-settings-file <path>`) to target a non-default Claude settings file.
 
+## Auto Pilot
+
+`viveworker` also includes **Auto Pilot**, a conservative auto-approval layer for the current workspace.
+
+You can enable it from `Settings > Auto Pilot`.
+
+Today it exposes two families of policy:
+
+- **Safe reads**: auto-approve common workspace-only read commands such as `rg`, `find`, `git diff`, `git show`, `sed -n`, `head`, `tail`, and `wc`
+- **Low-risk writes**: auto-approve small file changes only when they fit one of these lanes:
+  - `Content & copy`
+  - `UI & tests`
+  - `Small code patches (beta)`
+
+Important boundaries:
+
+- Auto Pilot is scoped to the **current workspace only**
+- secrets, config, deploy, auth, payment, networked changes, and anything outside the current workspace stay manual
+- `Small code patches (beta)` is stricter than the other write lanes and expects a recent read of the same file in the same thread
+
+When Auto Pilot does not approve something, the request stays in the normal phone approval flow.
+The approval detail view also explains why it stayed manual, so it is easier to tune and trust over time.
+
 ### Sync Mode (for Claude plans and questions)
 
 Claude Desktop exposes approval hooks but has no native IPC for answering `ExitPlanMode` / `AskUserQuestion` prompts remotely. To let you answer plans and questions from your paired device, `viveworker` offers **Sync mode** (toggle in `Settings`, formerly "Away mode"):

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "viveworker",
-  "version": "0.7.0-beta.1",
+  "version": "0.7.0-beta.2",
   "description": "Open mobile control surface for Codex, Claude, Thread Sharing, File Share, Moltbook, and A2A tasks on your trusted LAN.",
   "author": "Yuta Hoshino <hoshino.lireneo@gmail.com>",
   "license": "MIT",
@@ -61,6 +61,7 @@
     "ntfy/docker-compose.yml.example"
   ],
   "dependencies": {
+    "@hazbase/auth": "^0.5.0",
     "qrcode-terminal": "^0.12.0",
     "web-push": "^3.6.7"
   },

package/scripts/share-cli.mjs

@@ -89,6 +89,7 @@ function printHelp() {
   console.log("");
   console.log("Paid shares (x402 / USDC on Base — CLOSED BETA, testnet only): --price 0.10 --pay-to 0x…");
   console.log("  Buyers use any x402-compatible client (e.g. `x402-fetch` on npm).");
+  console.log("  To use a hazbase wallet as payTo, resolve it first via the local /api/hazbase/payout-address endpoint.");
   console.log("  --price and --password are mutually exclusive on a single share.");
   console.log("  `share list --metrics` prints 24h / 7d payment-flow stats for your shares.");
   console.log("");