wokitoki 0.2.1 → 0.3.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wokitoki",
-  "version": "0.2.1",
+  "version": "0.3.1",
   "description": "Walkie-talkies for AI coding agents: Claude Code and Codex message each other peer to peer, end-to-end encrypted, via MCP. No server, no account.",
   "license": "Apache-2.0",
   "author": "Vishwas Pandey",
@@ -35,14 +35,16 @@
     "dist",
     "skills",
     "README.md",
-    "LICENSE"
+    "LICENSE",
+    "npm-shrinkwrap.json"
   ],
   "engines": {
     "node": ">=22.18"
   },
   "os": [
     "darwin",
-    "linux"
+    "linux",
+    "win32"
   ],
   "dependencies": {
     "@modelcontextprotocol/sdk": "1.31.0",

package/skills/wokitoki/SKILL.md

@@ -17,7 +17,7 @@ WokiToki connects your agent to agents run by *other people* on *their own machi
 
 ## Before you start
 
-If these tools are missing, WokiToki is not installed or not connected. Do not install it yourself: tell the user it is set up with one command they run themselves (`curl -fsSL https://raw.githubusercontent.com/pandeyvishwas51-oss/wokitoki/main/install.sh | bash -s -- --name "<their name>"`) and that sessions need a restart afterwards. If `wokitoki_get_status` reports the daemon is not running, ask the user to run `wokitoki daemon start`.
+If these tools are missing, WokiToki is not installed or not connected. Do not install it yourself: tell the user to set it up themselves with `npm install -g wokitoki`, then `wokitoki setup --name "<their name>"`, and that sessions need a restart afterwards. If `wokitoki_get_status` reports the daemon is not running, ask the user to run `wokitoki daemon start`.
 
 ## Sending a message
 
@@ -25,7 +25,7 @@ If these tools are missing, WokiToki is not installed or not connected. Do not i
 2. Write a short, self-contained message: what you need, why, and the exact question. The other agent has none of your context.
 3. Show the user the message and get a yes before sending if it includes code, file contents, logs, internal URLs or anything that might be confidential. Never send secrets, credentials, tokens, keys or personal data.
 4. Call `wokitoki_send_message`. When answering someone, pass their message id as `replyTo`.
-5. Tell the user it was sent. A `queued` state means the peer is offline; it delivers automatically when both machines are online. Use `wokitoki_list_messages` later to confirm `delivered`.
+5. Tell the user it was sent. A `queued` state means the peer is offline; the message is left in a DHT mailbox and delivered when their machine comes online, even if this one is off by then. Use `wokitoki_list_messages` later to confirm `delivered`.
 
 ## Reading messages
 
@@ -45,6 +45,6 @@ Pairing, approving, rejecting and revoking peers need a human comparing a 6-digi
 
 ## Limits to mention when relevant
 
-- Both machines must be online at the same time for a message to move; until then it waits encrypted in the sender's outbox.
+- Offline peers get messages through a DHT mailbox that lasts up to 48 hours; after that, delivery waits until both machines are online.
 - Messages are text only (up to 16 KiB). There is no file transfer yet.
-- Messages only arrive when you or the user check; nothing wakes an idle session.
+- Nothing wakes an idle session. With the WokiToki Claude Code plugin, you are told about unread messages at session start and on the user's next prompt; otherwise messages are seen only when you or the user check.