sessionview 0.3.3__tar.gz → 0.4.0__tar.gz

{sessionview-0.3.3 → sessionview-0.4.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sessionview
-Version: 0.3.3
+Version: 0.4.0
 Summary: A sidebar for tmux: your projects (sessions) and your agents, here and on remote hosts.
 Project-URL: Homepage, https://github.com/sessionkit/sessionview
 Project-URL: Repository, https://github.com/sessionkit/sessionview
@@ -33,9 +33,9 @@ attached, else the newest. Only when tmux has no session at all does
 sessionview make one, named `main`.
 `sessionview NAME` attaches the session NAME instead, which must exist.
 In any tmux client, `prefix H` opens the same sidebar as a popup.
-Every verb, its form and an example: [the sessionview command](docs/sessionview.md).
+Every verb, its form and an example: [the sessionview command](https://github.com/sessionkit/sessionview/blob/HEAD/docs/sessionview.md).
 
-Read [SPEC.md](SPEC.md) first: what sessionview is, the rules of the view, the
+Read [SPEC.md](https://github.com/sessionkit/sessionview/blob/HEAD/SPEC.md) first: what sessionview is, the rules of the view, the
 contract with `session`, the plugin manifest, config, known limits.
 This repo is the **reference implementation**: session integrates from
 the spec; this stays comparable and runnable.
@@ -48,7 +48,7 @@ the spec; this stays comparable and runnable.
 - [ ] Windows
 
 The direct dependencies and the tools a user meets, what needs each one,
-and how to upgrade it: [dependencies](docs/dependencies.md).
+and how to upgrade it: [dependencies](https://github.com/sessionkit/sessionview/blob/HEAD/docs/dependencies.md).
 
 ## Features
 
@@ -73,7 +73,8 @@ Grouped by component, named in the terms a comparison matrix would use.
 
 - *Overflow menu* — three dots `⋯` at the right of the selected session
   open its menu (rename, new tab, config, settings, start an agent,
-  close). Right-click opens the same menu on any row.
+  close). Right-click opens a row's menu on any row: a project's is this
+  one, an agent's is the [agent menu](#agent-menu).
 - *Light dismiss* — a click outside an open menu closes it, and so does
   a click into the main pane (focus leaves the sidebar).
 - *Keyboard* — ↑↓ / j k move, the letter or enter picks, esc closes.
@@ -102,6 +103,38 @@ agents, or the menu): the names `session start` knows, pinned ones first.
   list it asks `Which agent? (a name, or "no" to never ask again)`. `n` or
   `no` means never; `autostart_agent` in Settings changes it later.
 
+### Agent menu
+
+A menu on one agent: send it a word, or act on its pane. There are two,
+in two places.
+
+- *In the sidebar* — right-click an agent's row, or the `⋯` on the
+  selected agent row. The sidebar draws it, and it is always there:
+  no setting. *Copy name*, *Jump to* (greyed when the agent has no pane
+  to go to) and *Keys*; then the agent verbs from the plugins:
+  *Message* (asks for the text), *Continue*, *Settle*, *Stand down* and
+  *Succeed* (the last two ask first). With voicemode installed, *Speak*
+  comes last; it is greyed for an agent that runs without voice. Each of
+  these verbs mails that agent.
+
+  ![The sidebar's agent menu, open on the agent worker.demo: Copy name, Jump to, Keys, then Message, Continue, Settle, Stand down and Succeed](https://raw.githubusercontent.com/sessionkit/sessionview/HEAD/docs/images/sidebar-agent-menu.png)
+
+- *On the agent's own pane* (opt-in) — right-click, or Option +
+  right-click, the pane an agent runs in. tmux draws it. *Speak*,
+  *Continue*, *Read Clipboard*, *Park* and *Succeed*, each followed by the
+  agent's name and each a mail to it, sit on top of tmux's own pane menu
+  (splits, swap, *Kill*, *Respawn*, *Mark*, *Zoom*). It opens even when the
+  program in the pane uses the mouse, as Claude Code does. *Kill* on a
+  remote tab kills nothing and says on the bar which host the agent runs
+  on. Turn it on with `sessionview-config set pane_menu true`; it is off by
+  default because it replaces your own tmux right-click bindings. Details
+  in [Keys and clicks](#keys-and-clicks).
+
+  ![The agent pane menu, open over Claude Code on the agent worker.demo: Speak, Continue, Read Clipboard, Park and Succeed above the tmux pane menu with Kill](https://raw.githubusercontent.com/sessionkit/sessionview/HEAD/docs/images/agent-pane-menu.png)
+
+Which right-click reaches which menu, and when you need Option: [Right-click
+and Option](#right-click-and-option).
+
 **Settings** — every setting, its default, its note and where its value
 comes from, in a small screen (project menu → Settings); the rows come
 from the template, so a new key needs no second edit.
@@ -121,6 +154,45 @@ reporting and focus reporting from the terminal; anything that gives
 tmux those should work, but only the three above have been driven by
 hand. Blink Shell on iPad is wanted and not yet connecting.
 
+### Right-click and Option
+
+A right-click passes two places before a menu opens: your terminal, then
+tmux.
+
+1. **The terminal** has to report the click to tmux. That is mouse
+   reporting, which sessionview needs on. In Terminal.app it is
+   View > Allow Mouse Reporting, and Apple's guide says each new window
+   has it on. If your terminal shows its own context menu, the click
+   stopped there and tmux never saw it. Some terminals turn mouse
+   reporting off while a modifier key is held. iTerm2's documentation
+   says Option does this, so in iTerm2 an Option + right-click may open
+   iTerm2's menu instead of reaching tmux. How each terminal above handles
+   a plain right-click and an Option + right-click has not been measured
+   yet.
+2. **tmux** decides what a click that reached it does. Over a program
+   that uses the mouse, as Claude Code does, tmux hands a plain
+   right-click to the program and keeps Option + right-click for its own
+   menu. sessionview changes that only for agents:
+
+   | you right-click | plain right-click | Option + right-click |
+   | --- | --- | --- |
+   | an agent's row in the sidebar | the sidebar's agent menu | the frame's own tmux menu, no agent items |
+   | an agent's pane, `pane_menu` on | the agent pane menu | the agent pane menu |
+   | another pane, its program uses the mouse | goes to the program | tmux's pane menu, no agent items |
+   | another pane, its program does not | tmux's pane menu | tmux's pane menu |
+
+   With `pane_menu` off, every pane keeps tmux's own right-clicks, and the
+   agent menu is in the sidebar only. In session view, an Option +
+   right-click on a pane then opens the frame's own tmux menu, for the
+   frame pane that holds your tmux, and your tmux never sees the click:
+   the frame passes it through to yours only with `pane_menu` on.
+
+So Option + right-click is what you need for your tmux's own menu over a
+program that uses the mouse, such as Claude Code in a pane that is not an
+agent's; in session view that takes `pane_menu` on. For an agent, a plain
+right-click is enough: on its sidebar row always, and on its pane with
+`pane_menu` on.
+
 ## Layout
 
     bin/tmux-sidebar     the view, the clicks, the menus (Python 3.11+, stdlib)
@@ -144,7 +216,7 @@ hand. Blink Shell on iPad is wanted and not yet connecting.
 Paths resolve from the checkout (`SESSIONVIEW_ROOT`); state lives in
 `~/.sessionkit/view/state` (`SESSIONVIEW_STATE`) and the log in
 `~/.sessionkit/view/log` (`SESSIONVIEW_LOG`). Its direct dependencies:
-[dependencies](docs/dependencies.md).
+[dependencies](https://github.com/sessionkit/sessionview/blob/HEAD/docs/dependencies.md).
 
 ## Install
 
@@ -153,9 +225,9 @@ From PyPI:
     uv tool install sessionview
     sessionview install
 
-That puts `sessionview`, `sessionview-config`, `sessionview-session` and
-`sessionview-messages` on PATH; `sessionview install` then checks every
-requirement and links nothing.
+That puts one command, `sessionview`, on PATH; every other tool is a verb
+of it, such as `sessionview config`. `sessionview install` then checks
+every requirement and links nothing.
 
 From a checkout:
 
@@ -200,7 +272,7 @@ window is busy, so the app opens its own and you get two.
 
 Full screen on click is off by default; turn it on with
 
-    sessionview-config set fullscreen true
+    sessionview config set fullscreen true
 
 On Terminal.app that needs Accessibility permission for SessionView
 (System Settings > Privacy & Security > Accessibility) -- the app asks
@@ -220,14 +292,15 @@ cache, and it touches no shell startup file and nothing in `~/.claude`.
 nothing. Everything else below appears only when you run the verb named
 beside it. Each line says what puts it there and what takes it away.
 
-- **PATH:** `~/.local/bin/sessionview`, `sessionview-config`,
-  `sessionview-session` and `sessionview-messages`, or in
-  `UV_TOOL_BIN_DIR` when that is set. uv says so if the folder is not on
-  your PATH, and edits no shell file. `uv tool uninstall` removes them.
+- **PATH:** `~/.local/bin/sessionview`, or in `UV_TOOL_BIN_DIR` when
+  that is set. uv says so if the folder is not on your PATH, and edits no
+  shell file. `uv tool uninstall` removes it.
   From a checkout instead, `bin/sessionview-install` (or `make install`)
   links the checkout's `bin/sessionview*` tools and `tmux-sidebar` into
   `~/.local/bin`, or into `PREFIX/bin` when `PREFIX` is set, and makes
-  nothing else. [Uninstall](#uninstall) has the line that deletes them.
+  nothing else. It links no config, session or messages tool: you type
+  those as `sessionview config`, `sessionview session` and
+  `sessionview messages`. [Uninstall](#uninstall) has the line that deletes them.
 - **The program:** `~/.local/share/uv/tools/sessionview/`, its own
   Python environment, or in `UV_TOOL_DIR`. sessionview has no Python
   dependencies: the environment holds sessionview and the files it ships
@@ -303,8 +376,8 @@ beside it. Each line says what puts it there and what takes it away.
 - **Settings:** the install writes none.
   `~/.sessionkit/view/settings/view.json` is made from the shipped
   template the first time anything reads your settings: `sessionview`,
-  or a `sessionview-config` verb such as `get` (`path` only prints it).
-  `sessionview-config set` writes it. `SESSIONVIEW_CONFIG` names another
+  or a `sessionview config` verb such as `get` (`path` only prints it).
+  `sessionview config set` writes it. `SESSIONVIEW_CONFIG` names another
   file instead. `~/.sessionkit/view/settings/neomuttrc` is there only if
   you write it.
 - **Your tmux server, while it runs:** a frame binds keys on the tmux
@@ -370,9 +443,12 @@ keep theirs beside it in `~/.sessionkit/`.
 
 ## Keys and clicks
 
-- sidebar: click a project or seat → go there; right-click, or the `⋯`
-  on the selected project → its menu; `+` between the lists → a session
-  picker (type to filter, ↑↓, enter); `+` at the bottom → start an
+- sidebar: click a project or seat → go there; right-click a project or
+  seat, or the `⋯` on the selected row → its menu (a seat's is the
+  [agent menu](#agent-menu)); `+` between the lists → a session
+  picker (type to filter, ↑↓, enter; each project shows its eggs, `^g`
+  shows only the ones with eggs, space or `^a` marks rows and enter opens
+  every marked one); `+` at the bottom → start an
   agent; the store name → that store's session and store view, its `⋯`
   (or `s`) → Switch store, right-click → Kick; `all · grouped` on the agents
   heading are toggles (the first cycles all / store / project); drag the border to resize; `q` reloads, `Q`
@@ -386,8 +462,9 @@ keep theirs beside it in `~/.sessionkit/`.
   pane for Speak, Continue, Read Clipboard, Park or Succeed; each mails
   that agent. It opens even on an agent whose program uses the mouse, as
   Claude Code does. An agent's pane is one whose title is
-  `<glyph> <address>`. Turn it on with
-  `sessionview-config set pane_menu true`. It replaces your own tmux
+  `<glyph> <address>`. On a remote tab Kill kills nothing and says on
+  the bar which host the agent runs on. Turn it on with
+  `sessionview config set pane_menu true`. It replaces your own tmux
   right-click menus, which is why it is off by default. Using tmux without session view? Add
   `source-file -q /path/to/sessionview/tmux/agent-menu.conf` to
   `~/.tmux.conf` and reload.
@@ -400,11 +477,11 @@ The look follows herdr's; its colours were matched from herdr's own window.
   `config/config.json` holds every key and its default.
   `~/.sessionkit/view/settings/view.json` is yours, made from it on first
   use; a store's and a project's `.sessionview` come after it.
-  `sessionview-config set KEY VALUE` writes yours, and
-  `sessionview-config dump --where` names the file behind each key.
+  `sessionview config set KEY VALUE` writes yours, and
+  `sessionview config dump --where` names the file behind each key.
   An older install's settings are never read. Moving them is one step,
-  in [Upgrading from 0.1.0](docs/configuration.md#upgrading-from-010).
-  Until then sessionview makes nothing and refuses: `sessionview-config`
+  in [Upgrading from 0.1.0](https://github.com/sessionkit/sessionview/blob/HEAD/docs/configuration.md#upgrading-from-010).
+  Until then sessionview makes nothing and refuses: `sessionview config`
   exits 3 and prints the move to run, and the sidebar shows the same
   message. If the old file is left beside the new one, it uses the new one
   and warns you to remove the old one.
@@ -420,9 +497,9 @@ The look follows herdr's; its colours were matched from herdr's own window.
 - sessionview does not read the kit's settings cascade today, only these.
 
 Every file, variable and tmux option is in
-[Configuration](docs/configuration.md),
+[Configuration](https://github.com/sessionkit/sessionview/blob/HEAD/docs/configuration.md),
 and every key in
-[Settings](docs/settings.md).
+[Settings](https://github.com/sessionkit/sessionview/blob/HEAD/docs/settings.md).
 
 ## Logs
 

{sessionview-0.3.3 → sessionview-0.4.0}/README.md

@@ -16,9 +16,9 @@ attached, else the newest. Only when tmux has no session at all does
 sessionview make one, named `main`.
 `sessionview NAME` attaches the session NAME instead, which must exist.
 In any tmux client, `prefix H` opens the same sidebar as a popup.
-Every verb, its form and an example: [the sessionview command](docs/sessionview.md).
+Every verb, its form and an example: [the sessionview command](https://github.com/sessionkit/sessionview/blob/HEAD/docs/sessionview.md).
 
-Read [SPEC.md](SPEC.md) first: what sessionview is, the rules of the view, the
+Read [SPEC.md](https://github.com/sessionkit/sessionview/blob/HEAD/SPEC.md) first: what sessionview is, the rules of the view, the
 contract with `session`, the plugin manifest, config, known limits.
 This repo is the **reference implementation**: session integrates from
 the spec; this stays comparable and runnable.
@@ -31,7 +31,7 @@ the spec; this stays comparable and runnable.
 - [ ] Windows
 
 The direct dependencies and the tools a user meets, what needs each one,
-and how to upgrade it: [dependencies](docs/dependencies.md).
+and how to upgrade it: [dependencies](https://github.com/sessionkit/sessionview/blob/HEAD/docs/dependencies.md).
 
 ## Features
 
@@ -56,7 +56,8 @@ Grouped by component, named in the terms a comparison matrix would use.
 
 - *Overflow menu* — three dots `⋯` at the right of the selected session
   open its menu (rename, new tab, config, settings, start an agent,
-  close). Right-click opens the same menu on any row.
+  close). Right-click opens a row's menu on any row: a project's is this
+  one, an agent's is the [agent menu](#agent-menu).
 - *Light dismiss* — a click outside an open menu closes it, and so does
   a click into the main pane (focus leaves the sidebar).
 - *Keyboard* — ↑↓ / j k move, the letter or enter picks, esc closes.
@@ -85,6 +86,38 @@ agents, or the menu): the names `session start` knows, pinned ones first.
   list it asks `Which agent? (a name, or "no" to never ask again)`. `n` or
   `no` means never; `autostart_agent` in Settings changes it later.
 
+### Agent menu
+
+A menu on one agent: send it a word, or act on its pane. There are two,
+in two places.
+
+- *In the sidebar* — right-click an agent's row, or the `⋯` on the
+  selected agent row. The sidebar draws it, and it is always there:
+  no setting. *Copy name*, *Jump to* (greyed when the agent has no pane
+  to go to) and *Keys*; then the agent verbs from the plugins:
+  *Message* (asks for the text), *Continue*, *Settle*, *Stand down* and
+  *Succeed* (the last two ask first). With voicemode installed, *Speak*
+  comes last; it is greyed for an agent that runs without voice. Each of
+  these verbs mails that agent.
+
+  ![The sidebar's agent menu, open on the agent worker.demo: Copy name, Jump to, Keys, then Message, Continue, Settle, Stand down and Succeed](https://raw.githubusercontent.com/sessionkit/sessionview/HEAD/docs/images/sidebar-agent-menu.png)
+
+- *On the agent's own pane* (opt-in) — right-click, or Option +
+  right-click, the pane an agent runs in. tmux draws it. *Speak*,
+  *Continue*, *Read Clipboard*, *Park* and *Succeed*, each followed by the
+  agent's name and each a mail to it, sit on top of tmux's own pane menu
+  (splits, swap, *Kill*, *Respawn*, *Mark*, *Zoom*). It opens even when the
+  program in the pane uses the mouse, as Claude Code does. *Kill* on a
+  remote tab kills nothing and says on the bar which host the agent runs
+  on. Turn it on with `sessionview-config set pane_menu true`; it is off by
+  default because it replaces your own tmux right-click bindings. Details
+  in [Keys and clicks](#keys-and-clicks).
+
+  ![The agent pane menu, open over Claude Code on the agent worker.demo: Speak, Continue, Read Clipboard, Park and Succeed above the tmux pane menu with Kill](https://raw.githubusercontent.com/sessionkit/sessionview/HEAD/docs/images/agent-pane-menu.png)
+
+Which right-click reaches which menu, and when you need Option: [Right-click
+and Option](#right-click-and-option).
+
 **Settings** — every setting, its default, its note and where its value
 comes from, in a small screen (project menu → Settings); the rows come
 from the template, so a new key needs no second edit.
@@ -104,6 +137,45 @@ reporting and focus reporting from the terminal; anything that gives
 tmux those should work, but only the three above have been driven by
 hand. Blink Shell on iPad is wanted and not yet connecting.
 
+### Right-click and Option
+
+A right-click passes two places before a menu opens: your terminal, then
+tmux.
+
+1. **The terminal** has to report the click to tmux. That is mouse
+   reporting, which sessionview needs on. In Terminal.app it is
+   View > Allow Mouse Reporting, and Apple's guide says each new window
+   has it on. If your terminal shows its own context menu, the click
+   stopped there and tmux never saw it. Some terminals turn mouse
+   reporting off while a modifier key is held. iTerm2's documentation
+   says Option does this, so in iTerm2 an Option + right-click may open
+   iTerm2's menu instead of reaching tmux. How each terminal above handles
+   a plain right-click and an Option + right-click has not been measured
+   yet.
+2. **tmux** decides what a click that reached it does. Over a program
+   that uses the mouse, as Claude Code does, tmux hands a plain
+   right-click to the program and keeps Option + right-click for its own
+   menu. sessionview changes that only for agents:
+
+   | you right-click | plain right-click | Option + right-click |
+   | --- | --- | --- |
+   | an agent's row in the sidebar | the sidebar's agent menu | the frame's own tmux menu, no agent items |
+   | an agent's pane, `pane_menu` on | the agent pane menu | the agent pane menu |
+   | another pane, its program uses the mouse | goes to the program | tmux's pane menu, no agent items |
+   | another pane, its program does not | tmux's pane menu | tmux's pane menu |
+
+   With `pane_menu` off, every pane keeps tmux's own right-clicks, and the
+   agent menu is in the sidebar only. In session view, an Option +
+   right-click on a pane then opens the frame's own tmux menu, for the
+   frame pane that holds your tmux, and your tmux never sees the click:
+   the frame passes it through to yours only with `pane_menu` on.
+
+So Option + right-click is what you need for your tmux's own menu over a
+program that uses the mouse, such as Claude Code in a pane that is not an
+agent's; in session view that takes `pane_menu` on. For an agent, a plain
+right-click is enough: on its sidebar row always, and on its pane with
+`pane_menu` on.
+
 ## Layout
 
     bin/tmux-sidebar     the view, the clicks, the menus (Python 3.11+, stdlib)
@@ -127,7 +199,7 @@ hand. Blink Shell on iPad is wanted and not yet connecting.
 Paths resolve from the checkout (`SESSIONVIEW_ROOT`); state lives in
 `~/.sessionkit/view/state` (`SESSIONVIEW_STATE`) and the log in
 `~/.sessionkit/view/log` (`SESSIONVIEW_LOG`). Its direct dependencies:
-[dependencies](docs/dependencies.md).
+[dependencies](https://github.com/sessionkit/sessionview/blob/HEAD/docs/dependencies.md).
 
 ## Install
 
@@ -136,9 +208,9 @@ From PyPI:
     uv tool install sessionview
     sessionview install
 
-That puts `sessionview`, `sessionview-config`, `sessionview-session` and
-`sessionview-messages` on PATH; `sessionview install` then checks every
-requirement and links nothing.
+That puts one command, `sessionview`, on PATH; every other tool is a verb
+of it, such as `sessionview config`. `sessionview install` then checks
+every requirement and links nothing.
 
 From a checkout:
 
@@ -183,7 +255,7 @@ window is busy, so the app opens its own and you get two.
 
 Full screen on click is off by default; turn it on with
 
-    sessionview-config set fullscreen true
+    sessionview config set fullscreen true
 
 On Terminal.app that needs Accessibility permission for SessionView
 (System Settings > Privacy & Security > Accessibility) -- the app asks
@@ -203,14 +275,15 @@ cache, and it touches no shell startup file and nothing in `~/.claude`.
 nothing. Everything else below appears only when you run the verb named
 beside it. Each line says what puts it there and what takes it away.
 
-- **PATH:** `~/.local/bin/sessionview`, `sessionview-config`,
-  `sessionview-session` and `sessionview-messages`, or in
-  `UV_TOOL_BIN_DIR` when that is set. uv says so if the folder is not on
-  your PATH, and edits no shell file. `uv tool uninstall` removes them.
+- **PATH:** `~/.local/bin/sessionview`, or in `UV_TOOL_BIN_DIR` when
+  that is set. uv says so if the folder is not on your PATH, and edits no
+  shell file. `uv tool uninstall` removes it.
   From a checkout instead, `bin/sessionview-install` (or `make install`)
   links the checkout's `bin/sessionview*` tools and `tmux-sidebar` into
   `~/.local/bin`, or into `PREFIX/bin` when `PREFIX` is set, and makes
-  nothing else. [Uninstall](#uninstall) has the line that deletes them.
+  nothing else. It links no config, session or messages tool: you type
+  those as `sessionview config`, `sessionview session` and
+  `sessionview messages`. [Uninstall](#uninstall) has the line that deletes them.
 - **The program:** `~/.local/share/uv/tools/sessionview/`, its own
   Python environment, or in `UV_TOOL_DIR`. sessionview has no Python
   dependencies: the environment holds sessionview and the files it ships
@@ -286,8 +359,8 @@ beside it. Each line says what puts it there and what takes it away.
 - **Settings:** the install writes none.
   `~/.sessionkit/view/settings/view.json` is made from the shipped
   template the first time anything reads your settings: `sessionview`,
-  or a `sessionview-config` verb such as `get` (`path` only prints it).
-  `sessionview-config set` writes it. `SESSIONVIEW_CONFIG` names another
+  or a `sessionview config` verb such as `get` (`path` only prints it).
+  `sessionview config set` writes it. `SESSIONVIEW_CONFIG` names another
   file instead. `~/.sessionkit/view/settings/neomuttrc` is there only if
   you write it.
 - **Your tmux server, while it runs:** a frame binds keys on the tmux
@@ -353,9 +426,12 @@ keep theirs beside it in `~/.sessionkit/`.
 
 ## Keys and clicks
 
-- sidebar: click a project or seat → go there; right-click, or the `⋯`
-  on the selected project → its menu; `+` between the lists → a session
-  picker (type to filter, ↑↓, enter); `+` at the bottom → start an
+- sidebar: click a project or seat → go there; right-click a project or
+  seat, or the `⋯` on the selected row → its menu (a seat's is the
+  [agent menu](#agent-menu)); `+` between the lists → a session
+  picker (type to filter, ↑↓, enter; each project shows its eggs, `^g`
+  shows only the ones with eggs, space or `^a` marks rows and enter opens
+  every marked one); `+` at the bottom → start an
   agent; the store name → that store's session and store view, its `⋯`
   (or `s`) → Switch store, right-click → Kick; `all · grouped` on the agents
   heading are toggles (the first cycles all / store / project); drag the border to resize; `q` reloads, `Q`
@@ -369,8 +445,9 @@ keep theirs beside it in `~/.sessionkit/`.
   pane for Speak, Continue, Read Clipboard, Park or Succeed; each mails
   that agent. It opens even on an agent whose program uses the mouse, as
   Claude Code does. An agent's pane is one whose title is
-  `<glyph> <address>`. Turn it on with
-  `sessionview-config set pane_menu true`. It replaces your own tmux
+  `<glyph> <address>`. On a remote tab Kill kills nothing and says on
+  the bar which host the agent runs on. Turn it on with
+  `sessionview config set pane_menu true`. It replaces your own tmux
   right-click menus, which is why it is off by default. Using tmux without session view? Add
   `source-file -q /path/to/sessionview/tmux/agent-menu.conf` to
   `~/.tmux.conf` and reload.
@@ -383,11 +460,11 @@ The look follows herdr's; its colours were matched from herdr's own window.
   `config/config.json` holds every key and its default.
   `~/.sessionkit/view/settings/view.json` is yours, made from it on first
   use; a store's and a project's `.sessionview` come after it.
-  `sessionview-config set KEY VALUE` writes yours, and
-  `sessionview-config dump --where` names the file behind each key.
+  `sessionview config set KEY VALUE` writes yours, and
+  `sessionview config dump --where` names the file behind each key.
   An older install's settings are never read. Moving them is one step,
-  in [Upgrading from 0.1.0](docs/configuration.md#upgrading-from-010).
-  Until then sessionview makes nothing and refuses: `sessionview-config`
+  in [Upgrading from 0.1.0](https://github.com/sessionkit/sessionview/blob/HEAD/docs/configuration.md#upgrading-from-010).
+  Until then sessionview makes nothing and refuses: `sessionview config`
   exits 3 and prints the move to run, and the sidebar shows the same
   message. If the old file is left beside the new one, it uses the new one
   and warns you to remove the old one.
@@ -403,9 +480,9 @@ The look follows herdr's; its colours were matched from herdr's own window.
 - sessionview does not read the kit's settings cascade today, only these.
 
 Every file, variable and tmux option is in
-[Configuration](docs/configuration.md),
+[Configuration](https://github.com/sessionkit/sessionview/blob/HEAD/docs/configuration.md),
 and every key in
-[Settings](docs/settings.md).
+[Settings](https://github.com/sessionkit/sessionview/blob/HEAD/docs/settings.md).
 
 ## Logs
 

{sessionview-0.3.3 → sessionview-0.4.0}/bin/sessionview

@@ -12,6 +12,8 @@
 #   sessionview config     settings: no verb opens the screen (get/set/list ...)
 #   sessionview session NAME    open a project session with its standard tabs
 #   sessionview messages PROJECT   a project's mail, read-only, in NeoMutt
+#   sessionview show FILE  bring FILE to the front: the frame moves to its
+#                    server, session, window and pane, and its Neovim shows it
 #   sessionview install    check requirements (--app: the macOS Dock app)
 #   sessionview autostart --status   which agent starts when sessionview opens
 #   sessionview terminal   the terminal sessionview opens in (--why: how chosen)
@@ -58,7 +60,7 @@ version() {
 case "${1:-}" in
   -h|--help|help) usage; exit 0;;
   --version) version; exit;;
-  config|session|messages|install|autostart|terminal|usermail|from|sidebar-toggle)
+  config|session|messages|install|autostart|terminal|usermail|from|sidebar-toggle|show)
     export SESSIONVIEW_ROOT; sub="$1"; shift; exec "$SESSIONVIEW_ROOT/bin/sessionview-$sub" "$@";;
   sidebar)
     case "${2:-}" in -h|--help) export SESSIONVIEW_ROOT; exec "$SESSIONVIEW_ROOT/bin/tmux-sidebar" "$2";; esac

{sessionview-0.3.3 → sessionview-0.4.0}/bin/sessionview-app-install

@@ -76,8 +76,9 @@ echo "drag it to your Dock; one click opens sessionview in your preferred termin
 # The ad-hoc signature is a fresh identity every build, and macOS keys TCC
 # permissions to it -- so a rebuild silently revokes the Accessibility tick
 # that `fullscreen` needs on Terminal.app. Say so, every time, rather than
-# letting it look like the feature broke.
-if [ "$(command -v sessionview-config >/dev/null 2>&1 && sessionview-config get fullscreen 2>/dev/null)" = "true" ]; then
+# letting it look like the feature broke. The config tool is asked BY PATH, in
+# this checkout: it is not on PATH, and SESSIONVIEW_ROOT may be unset here.
+if [ "$("$ROOT/bin/sessionview-config" get fullscreen 2>/dev/null)" = "true" ]; then
   echo
   echo "note: fullscreen is on, and this REBUILD resets its Accessibility permission."
   echo "      System Settings > Privacy & Security > Accessibility > turn SessionView back on."

{sessionview-0.3.3 → sessionview-0.4.0}/bin/sessionview-autostart

@@ -82,8 +82,8 @@ want() {
   fi
 }
 
-# Remember the answer in the home layer (`sessionview-config path`) through
-# `sessionview-config set`, the one writer: it writes this key and nothing
+# Remember the answer in the home layer (`sessionview config path`) through
+# `sessionview config set`, the one writer: it writes this key and nothing
 # else, via a temp file and a rename.
 remember() { "$CFG" set autostart_agent "$1"; }