peekme 0.3.3 → 0.3.4

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # Changelog
 
+## 0.3.4 (2026-09-29)
+
+- Codex inside tmux over SSH: Option+P typed `π` although text was selected. Codex (0.159)
+  asks tmux whether it handles the mouse, and when tmux has the mouse off, which is its default,
+  Codex leaves the mouse to the terminal. The selection is then made by your terminal on your
+  own machine, and peekme on the other side of SSH cannot see it. peekme can't change that, so
+  now the first Option+P there opens a box that says so and how to fix it: `set -g mouse on` in
+  `~/.tmux.conf`. Alt+P shows the same box. Found by driving the real Codex in Terminal and
+  iTerm2 on macOS, through SSH and tmux.
+- On a Mac reached over SSH, peekme no longer reads that Mac's clipboard as a selection. It is
+  not the clipboard of the terminal you type in.
+- Short messages in a box now show whole, not one line with PgUp/PgDn.
+- With two copies of peekme on one machine (an old one from `cargo install`, a newer one from npm
+  or Homebrew), `codex` could keep starting the old copy. The old copy's `peekme install` had
+  linked `codex` to itself, and the new copy only fixed links that were missing. So Codex got
+  none of the later fixes, for example Option+P inside tmux over SSH, while `claude` worked. Now
+  the newer peekme moves such links to itself when it starts, and says so once.
+
 ## 0.3.3 (2026-09-29)
 
 - Claude Code with Amazon Bedrock, Google Vertex or an API gateway: explanations failed with

package/README.md

@@ -11,9 +11,9 @@ room, like Peek in VS Code. Esc closes it and the screen is exactly as before.
 The explanation comes from a small, fast model and it knows the conversation. If you select
 "its split panes" in an answer that recommends Kitty, it tells you it is about Kitty.
 
-Status: 0.3.3. Tested with Claude Code 2.1.284, Codex 0.159 and Copilot CLI 1.0.89 on Linux, also
-inside tmux and over SSH. On macOS it is tested in Terminal and iTerm2 with a stand-in agent, also
-inside tmux and over SSH.
+Status: 0.3.4. Tested with Claude Code 2.1.285, Codex 0.159 and Copilot CLI 1.0.89 on Linux, also
+inside tmux and over SSH. On macOS it is tested in Terminal and iTerm2 with a stand-in agent, and
+in Terminal with the real Codex, also inside tmux and over SSH.
 
 ## One peekme for all your agents
 
@@ -34,46 +34,21 @@ GitHub Copilot CLI:
 
 ## Install
 
-You need Claude Code, Codex CLI or GitHub Copilot CLI (logged in). More than one is fine too. Then install peekme in one of
-these ways and run `peekme install`:
-
 ```
-npm i -g peekme                               # you have npm already if you installed an agent with it
-brew install gregorybolshakov/tap/peekme      # Homebrew, on macOS or Linux
-cargo install peekme                          # builds it with Rust
+npm i -g peekme
 peekme install
 ```
 
-npm 12 may say that it skipped an install script of peekme. That is fine: peekme then downloads
-its binary the first time it runs.
-
-Without npm, Homebrew or Rust, the script from the
-[latest release](https://github.com/GregoryBolshakov/peekme/releases/latest) puts peekme in
-`~/.local/bin`:
-
-```
-curl --proto '=https' --tlsv1.2 -LsSf https://github.com/GregoryBolshakov/peekme/releases/latest/download/peekme-installer.sh | sh
-```
-
-Ready binaries are there too, for Linux and macOS on x86_64 and ARM.
+Open a new terminal. Now `claude`, `codex` and `copilot` open with peekme, and you type them as
+always. That's all.
 
-After this, `claude`, `codex` and `copilot` open with peekme in every new terminal. You keep
-typing them as always, and your aliases and scripts that call them keep working. `peekme install`
-adds a short, marked block to your `~/.bashrc` or `~/.zshrc` (for fish, a file in
-`~/.config/fish/conf.d`). If you install one of the agents later, it gets peekme too.
+peekme has no account of its own. The explanation uses the login of the agent you are in.
 
-```
-peekme doctor      # check the setup, and see what is in the way if something is
-peekme uninstall   # remove the block, your files are as before
-command claude     # run plain Claude Code once
-command codex      # run plain Codex once
-command copilot    # run plain Copilot CLI once
-```
+Don't have npm? Use one of these instead of the first line:
 
-The first time you run `peekme` on its own, it asks if it should do `peekme install` for you.
-
-When you update peekme and the new version knows more agents, it adds them to your shell setup by
-itself the next time it starts, and says so once. They work in new terminals.
+- Homebrew: `brew install gregorybolshakov/tap/peekme`
+- Rust: `cargo install peekme`
+- Neither: `curl -LsSf https://github.com/GregoryBolshakov/peekme/releases/latest/download/peekme-installer.sh | sh`
 
 ## Use
 
@@ -103,6 +78,11 @@ Terminal press Cmd+C after you select. Over SSH only the agent's own selection c
 use the full screen mode there (Claude Code with `"tui": "fullscreen"`, Codex and Copilot CLI
 by default).
 
+Inside tmux, Codex leaves the mouse to the terminal when tmux has the mouse off, which is tmux's
+default. A selection is then your terminal's own, and over SSH peekme cannot read it. Add
+`set -g mouse on` to `~/.tmux.conf` and restart Codex. peekme tells you this the first time you
+press Option+P there.
+
 In Claude Code, Alt+P opens the model picker. With peekme it explains the selection instead.
 `/model` still opens the model picker.
 
@@ -188,6 +168,12 @@ more.
 
 ### How `claude`, `codex` and `copilot` get peekme
 
+```
+peekme doctor      # check the setup, and see what is in the way if something is
+peekme uninstall   # remove it, your files are as before
+command claude     # run plain Claude Code once (same for codex, copilot)
+```
+
 `peekme install` does two things:
 
 1. It defines shell functions `claude`, `codex` and `copilot` in your shell setup. A function wins over
@@ -200,6 +186,15 @@ more.
 Both find the real agent on PATH themselves, so updating the agent changes nothing. If you
 remove peekme, the functions fall back to the plain agents.
 
+The block in `~/.bashrc` or `~/.zshrc` (for fish, a file in `~/.config/fish/conf.d`) is short
+and marked. It covers all three agents, so an agent you install later gets peekme too. When a new
+peekme version knows more agents, it adds them to your setup the next time it starts and says
+so once.
+
+npm 12 may say that it skipped an install script of peekme. That is fine: peekme then downloads
+its binary the first time it runs. Ready binaries for Linux and macOS (x86_64 and ARM) are on the
+[latest release](https://github.com/GregoryBolshakov/peekme/releases/latest) page.
+
 To use peekme with another program, run `peekme -- COMMAND`.
 
 ## Limits

package/npm-shrinkwrap.json

@@ -19,7 +19,7 @@
       "hasInstallScript": true,
       "license": "MIT OR Apache-2.0",
       "name": "peekme",
-      "version": "0.3.3"
+      "version": "0.3.4"
     },
     "node_modules/detect-libc": {
       "engines": {
@@ -48,5 +48,5 @@
     }
   },
   "requires": true,
-  "version": "0.3.3"
+  "version": "0.3.4"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "artifactDownloadUrls": [
-    "https://github.com/GregoryBolshakov/peekme/releases/download/v0.3.3"
+    "https://github.com/GregoryBolshakov/peekme/releases/download/v0.3.4"
   ],
   "author": "Gregory Bolshakov",
   "bin": {
@@ -69,7 +69,7 @@
       "zipExt": ".tar.xz"
     }
   },
-  "version": "0.3.3",
+  "version": "0.3.4",
   "volta": {
     "node": "18.14.1",
     "npm": "9.5.0"