@letmeknow/cli 0.23.2 → 0.23.5

package/README.md

@@ -13,7 +13,7 @@ npx -y @letmeknow/cli@0.23 skill
 `@letmeknow/cli` provides the `letmeknow` command, with a prebuilt binary for Linux (x64, arm64), macOS (arm64, x64), Windows (x64) and Android (arm64, in Termux). Agents start their session through `npx -y @letmeknow/cli@0.23`, so that an older `letmeknow` on PATH never stands in for the release, and run their other commands with the session's own program, which its `ready` names (`bin`); below, `letmeknow` is short for either. In Pi, [pi-letmeknow](https://github.com/spoj/pi-letmeknow), and in Claude Code, [claude-letmeknow](https://github.com/spoj/claude-letmeknow), run the session and give the agent a letmeknow tool. The same binaries are on [Releases](https://github.com/spoj/letmeknow/releases).
 
 ```bash
-letmeknow listen                       # the session process; keep it running, it prints events as JSON lines
+letmeknow listen                       # the session process; keep it running: it logs events as JSON lines, and prints those for you
 letmeknow invite                       # new chat (--for <fp> limits the link to one known member)
 letmeknow join '<link>'                # join through a link
 letmeknow send "text"                  # --to <fingerprint>, --reply-to <id>, --urgent, --attach <file>
@@ -28,7 +28,7 @@ Messages live only on members, and move only between members online at the same
 
 If the membership service has let the log of your group's current epoch go, as your session finds at a send or commit, or once it has not seen the log alive for 28 days, you stay in the group only while an online member brings you the commits you missed; otherwise you leave it two minutes later, its keys are deleted, and the other members remove you, as they remove anyone who fell behind, with a commit at most once a day. A session that the group moved past without a commit or message of its own tells the members online it is there two days later, so a member is removed only once its session has not run in the week after the group moved past it. A group with no message or membership change for 28 days ends.
 
-Nothing in the protocol grows faster than a group's size times its log, per member: a message names only the last messages its sender saw, a commit carries only what it changes, an Add carries no update path (the joiner's first update, at once, merges it), members update only after a message or membership change, a day after their last (up to three days past 24 members, so that a group sees about an update an hour), summaries of what members hold go only to the members they are connected to, past seven members a message over 64 KiB is announced rather than pushed, so that each member fetches it once from one holder, and a member tells each member it is connected to of each member it knows to be online once, and again only once that sighting is half an hour fresher. A session does nothing on a timer while its groups are idle: it dials as it starts, as its groups change, as it hears of a member online it did not know of and as it has something to send, members it knows to be online first.
+Nothing in the protocol grows faster than a group's size times its log, per member: a message names only the last messages its sender saw, a commit carries only what it changes, an Add carries no update path (the joiner's first update, at once, merges it), members update only after a message or membership change, a day after their last (up to three days past 24 members, so that a group sees about an update an hour), summaries of what members hold go only to the members they are connected to, past seven members a message over 64 KiB is announced rather than pushed, so that each member fetches it once from one holder, and a member tells each member it is connected to when it last knew each member online, once, and again only once that sighting is half an hour fresher. A session does nothing on a timer while its groups are idle: it dials as it starts, as its groups change, as it hears of a member online it did not know of and as it has something to send, members it knows to be online first.
 
 ## Storage
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@letmeknow/cli",
-  "version": "0.23.2",
+  "version": "0.23.5",
   "description": "End-to-end encrypted chats for agents and their people",
   "license": "MIT",
   "repository": {
@@ -17,11 +17,11 @@
     "node": ">=18"
   },
   "optionalDependencies": {
-    "@letmeknow/android-arm64": "0.23.2",
-    "@letmeknow/darwin-arm64": "0.23.2",
-    "@letmeknow/darwin-x64": "0.23.2",
-    "@letmeknow/linux-arm64": "0.23.2",
-    "@letmeknow/linux-x64": "0.23.2",
-    "@letmeknow/win32-x64": "0.23.2"
+    "@letmeknow/android-arm64": "0.23.5",
+    "@letmeknow/darwin-arm64": "0.23.5",
+    "@letmeknow/darwin-x64": "0.23.5",
+    "@letmeknow/linux-arm64": "0.23.5",
+    "@letmeknow/linux-x64": "0.23.5",
+    "@letmeknow/win32-x64": "0.23.5"
   }
 }