@webinson/peer 0.4.2 → 0.4.14

package/README.md

@@ -24,10 +24,13 @@ In a Claude Code thread:
 - A shared thread's title starts with `● Peer · `, so it stands out in Claude Code's session list; the mark comes
   back if Claude Code renames the thread, and `/peer stop` takes it off.
 - `/peer-list` lists the shared threads by repository, then by person, with each thread's branch and
-  state, and the threads that stopped in the last hours.
+  state, and the threads that stopped in the last hours. With the plugin installed it opens a `Peer` pane beside
+  the chat that reloads every 15 s; without it, or where no pane fits, the hook answers with the list.
 
-`/peer`, `/peer stop` and `/peer-list` are answered by the hook before the prompt reaches the model,
-so they cost no tokens. `peer list` prints the same list in a terminal.
+`/peer stop` and `/peer-list` are answered by the hook before the prompt reaches the model, so they
+cost no tokens. A bare `/peer` is shared by the hook too, then reaches the agent, which confirms it in a
+line or two: one short turn, instead of Claude Code's "hook blocked your prompt" warning. `/peer-thread` opens a pane with what this thread saved to your own OpenViking memory, in sentences (read-only;
+`peer thread <session id>` prints it). `peer list` prints the same list in a terminal; `peer list --json` gives the pane the hub's list as it came.
 
 ## What is shared
 
@@ -59,7 +62,7 @@ only the hook knows the session id. After that the hooks report that thread arou
 mark. A hook never fails or holds up a session: it gives the hub 3 seconds and drops what does not
 go through. What the hooks did, without any prompt text, is in `~/.peer/hook.log`.
 
-If `/peer` reaches the model ("the hook did not run"), `peer doctor` checks the sign-in, the hooks in
+If the agent says the hook did not run, or `/peer stop` reaches the model, `peer doctor` checks the sign-in, the hooks in
 Claude Code's settings and the paths they run, and runs the hook the way Claude Code does. An app
 or IDE that starts Claude through the Agent SDK may not load `~/.claude/settings.json`; `claude` in
 a terminal does.
@@ -74,21 +77,34 @@ If your team runs a shared project memory (an OpenViking server, see the Peer Hu
 `deploy/team-memory/`), connect this computer once, inside the project's repository:
 
 ```bash
-printf '%s' "$YOUR_TEAM_KEY" | peer team connect https://memory.example.com --as <you> --project <id>
+printf '%s' "$YOUR_TEAM_KEY" | peer team connect https://memory.example.com --as <you>
 ```
 
-The key comes on stdin and is saved in `~/.peer/team-memory/member.json` (mode 0600). After that, the first
+The project is the one your Peer workspace keeps this repository in, with all of that project's repositories;
+a repository in no Hub project (or without `peer login`) is a project of its own, named by its normalized
+origin (`github.com-acme-shop`). `--project <id>` names another. The key comes on stdin and is saved in `~/.peer/team-memory/member.json` (mode 0600). After that, the first
 prompt of every thread in that repository (and the first after a resume or compaction) gets at most five
 teammates' published findings that match it: verified or observed, not your own, about 1,500 tokens,
 fenced as data from colleagues; a page whose paths changed in three or more commits since it was last
 confirmed comes marked "may be stale". The prompt's first 400 characters go to the team server as the search
 query. Nothing else of the thread is sent. `peer team status` shows the connection and the last recalls.
 
+## Your own memory
+
+`/peer-all` lists what your personal OpenViking (as `~/.openviking/ovcli.conf` points to it) remembers, 20 to a
+page: `/peer-all page 2`; `--newest` or `--oldest` orders it by the time a memory last changed (for an event, when it
+was added). With the thread mark installed it opens a pane with a search field that searches as you type, a this-repository switch and a time
+button that goes unsorted, newest first, oldest first and back. `/peer-all <words>` searches the memories' full text: every word, in
+any order, anywhere in a memory, case and diacritics left aside (`pamat` finds "pamäť"); `"a phrase"` in quotes keeps
+its words together; conversation archives are left out, and `here` keeps it to the current repository:
+`/peer-all here batch limit`. The hook answers, so the list reaches you and never the thread or its capture.
+`peer all …` prints the same in a terminal. Editing and deleting stay in OpenViking Studio.
+
 ## Other commands
 
 ```
 peer status       who you are, the workspace and the threads this computer shares
-peer doctor       why /peer reaches the model instead of Peer's hook
+peer doctor       why Peer's hook did not answer /peer
 peer team connect connect to the team's memory server (see above)
 peer team status  the team server, project and the last recalls
 peer install      set Claude Code up again