Skip to main content
@wurk/cli and @wurk/sdk 0.9.0 are published on npm. The CLI includes the matching SDK. A skill update, npm update and hosted MCP update are separate: updating one does not update the others.

​
Upgrade an existing installation

  1. Stop CLI commands, notification watchers, local MCP hosts and other applications writing to the same state directory.
  2. Back up the entire original private state directory, including SQLite sidecar files. Preserve wallets, accounts, spending grants, payment history, media records and notification cursors together. Keep the backup private and outside Git.
  3. In the existing CLI installation directory, update the exact package:
On Windows, use npm.cmd. If your application explicitly installs both packages, update them together:
  1. Check ./node_modules/.bin/wurk --version on Linux/macOS, or ./node_modules/.bin/wurk.cmd --version on Windows. Expect 0.9.0 and keep the updated application lockfile.
  2. Inspect the original state before restarting automation: use config inspect, wallet list, account list and operations list with --state-dir ORIGINAL_STATE_DIR. Inspect unresolved operations and reconcile payment, finance and creator actions using their original references. Opening the payment journal performs the version 2 migration described below.
  3. Resume using the same state directory, origin, wallet and operation/request IDs. Update every writer sharing this state before restarting it. Do not run config init again or reimport wallets to replace existing state.
The supported Node versions are >=22.22.0 <23, >=24.12.0 <25, and >=26.0.0 <27. Native Windows x64 and ARM64 installs do not require compiling the SQLite adapter.
Version 0.9.0 upgrades the local payment journal from SQLite schema 1 to 2 when opened. Older clients cannot safely reopen that upgraded journal. Do not downgrade or use a copied old database to bypass a pending payment or spent allowance. Restoring an old snapshot also omits any payments made after that snapshot.
New installations use https://api.wurk.fun. Existing saved operations and grants remain bound to their original origin, including https://wurkapi.fun. Keep that configured origin for recovery; do not rewrite an existing journal or silently switch its origin because a documentation example changed.

​
What changes in 0.9.0

Successful payment can release the associated checkout creation/payment cooldowns for the supported families. Status polling and unpaid-attempt limits remain; follow rate limits instead of sleeping after every confirmed job or retrying blindly.

​
Refresh agent instructions and MCP

Read the current skill metadata and release guide. The documentation release accompanying these clients is skill 1.5.12; it is a separate version from npm 0.9.0. Check what your server actually serves before assuming its rollout is complete. If your agent stores a local copy of the skill, refresh its complete bundle using the release guide’s installer. Updating only the entry SKILL.md can leave linked references stale. Updating a repository or the HTTP skill does not automatically update copies installed from another registry. Restart a local MCP host after updating its CLI installation, keeping its original policy, grants and state. Hosted MCP is supplied by the API deployment: it does not upgrade when you run npm locally. Use the tools advertised by the connected server; wurk_payment_retry_rejected requires current host permission and, on hosted MCP, a new browser-wallet signature.