sessionview 0.3.1__tar.gz → 0.3.2__tar.gz

{sessionview-0.3.1 → sessionview-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sessionview
-Version: 0.3.1
+Version: 0.3.2
 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
@@ -26,8 +26,11 @@ Install from PyPI: `uv tool install sessionview` (see [Install](#install)).
 
     sessionview
 
-In this terminal, that puts the sidebar on the left and the session
-`main` on the right; a private outer tmux holds the two panes.
+In this terminal, that puts the sidebar on the left and a tmux session
+on the right; a private outer tmux holds the two panes. The session is
+one tmux already has: your default assistant's, else the one you last
+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).
@@ -92,8 +95,12 @@ agents, or the menu): the names `session start` knows, pinned ones first.
   not start. An agent already running is never started twice.
 - *Agents have a home* — an agent's own file says where it wakes
   (`start: directory:`); a project's menu starts it in the project.
-- *Consent on first open* — Dreamcatcher asks once which agent to start
-  when it opens (a numbered pick, or never), and remembers.
+- *Consent on first open* — the first time it opens, sessionview asks
+  which agent to start whenever it opens, and remembers the answer. It
+  says *sessionview can start an agent for you each time it opens*, lists
+  your agents by number and asks `Which? (number, name, or "n")`. When it cannot get the
+  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.
 
 **Settings** — every setting, its default, its note and where its value
 comes from, in a small screen (project menu → Settings); the rows come
@@ -135,7 +142,8 @@ hand. Blink Shell on iPad is wanted and not yet connecting.
                          claude-code: short, safe driving skills with tools
 
 Paths resolve from the checkout (`SESSIONVIEW_ROOT`); state lives in
-`~/.local/state/sessionview` (`SESSIONVIEW_STATE`). Its direct dependencies:
+`~/.sessionkit/view/state` (`SESSIONVIEW_STATE`) and the log in
+`~/.sessionkit/view/log` (`SESSIONVIEW_LOG`). Its direct dependencies:
 [dependencies](docs/dependencies.md).
 
 ## Install
@@ -235,14 +243,13 @@ beside it. Each line says what puts it there and what takes it away.
   sessionview` drops this package's entries, and `uv cache prune` drops
   the ones nothing uses.
 - **Folders, each made by a verb you run:**
-  - `~/.local/state/sessionview/`: the state folder, made the first time
-    `sessionview` opens (or `sessionview session` or `sessionview
-    messages` runs). `SESSIONVIEW_STATE` moves it. An older release's
-    `~/.local/state/herd/` is renamed to it then, when only the old
-    one exists. In it:
+  - `~/.sessionkit/view/state/`: the state folder, mode 0700, made the
+    first time `sessionview` opens (or `sessionview session` or
+    `sessionview messages` runs). `SESSIONVIEW_STATE` names another
+    folder instead. Each file sessionview makes in it is private (mode
+    0600). In it:
     - `frame-PID.tty`, one while each frame is open. The frame deletes
       it when it closes; a frame killed outright can leave it behind.
-    - `sessionview.log`, the log ([Logs](#logs)).
     - `recent.tsv`, a line each time `sessionview session` opens a
       project, for the picker's order.
     - `picker-order`, when you flip the picker's sort.
@@ -254,6 +261,23 @@ beside it. Each line says what puts it there and what takes it away.
     - `sidebar-remote-HOST.json`, what the sidebar last saw from each
       host in your `remotes` setting.
     - `mutt/`, an rc file for each box `sessionview messages` opens.
+  - `~/.sessionkit/view/log/`: the log folder, mode 0700, made at the
+    same time. It holds `sessionview.log` ([Logs](#logs)).
+    `SESSIONVIEW_LOG` names another log file. When `SESSIONVIEW_STATE`
+    is set, the log is `sessionview.log` in that folder instead.
+  - `~/.local/state/sessionview/`: the state folder of releases before
+    this one. Nothing new is made there. On an upgrade, the first start
+    hard-links `recent.tsv`, `picker-order`, `sidebar-mail.txt` and each
+    file in `mutt/` into the new state folder. The old names are kept,
+    so the two names are one file, and a sidebar still running from
+    before the upgrade stays correct. The old folder is left in place,
+    with the old `sessionview.log`, `sidebar-mouse.log`, the frame pins
+    and the plugin and remote files, which are not carried over. One
+    line is added to the end of the old log, naming the new one. Each
+    start sets the old folder to mode 0700, so the old names are private
+    too; the files in it keep their modes. An
+    older release's `~/.local/state/herd/` is renamed to this folder
+    first, when only the herd one exists.
   - `~/Applications/SessionView.app`: `sessionview install --app` (or
     `make app` in a checkout), or in `DEST` when that is set. It is
     built in a temporary folder that is deleted after, and a rebuild
@@ -320,21 +344,25 @@ rm ~/.local/bin/sessionview ~/.local/bin/sessionview-* ~/.local/bin/tmux-sidebar
 ```
 
 That leaves what the verbs made, listed above. The Dock app, the
-plugin's cached copy and the state folder are sessionview's alone. To
-delete them:
+plugin's cached copy, and the state and log folders are sessionview's
+alone. To delete them:
 
 ```bash
 rm -rf "${HOME:?}/Applications/SessionView.app"
 rm -rf "${HOME:?}/.claude/plugins/cache/sessionview"
+rm -rf "${HOME:?}/.sessionkit/view/state" "${HOME:?}/.sessionkit/view/log"
 rm -rf "${HOME:?}/.local/state/sessionview"
 ```
 
+The last line is for an upgrade from an earlier release: it removes the
+old state folder, with the old log in it.
+
 uv's cache stays too, with the other things uv installed; `uv cache
 clean sessionview` drops this package's entries. The key bindings go
 when your tmux server next exits.
 
 The rest is your data: delete it by hand only if you want it gone.
-`~/.sessionkit/view/` holds your settings, and the kit's other packages
+`~/.sessionkit/view/settings/` holds your settings, and the kit's other packages
 keep theirs beside it in `~/.sessionkit/`.
 
 ## Keys and clicks
@@ -380,8 +408,9 @@ The look follows herdr's; its colours were matched from herdr's own window.
 - **Environment:** `SESSIONVIEW_CONFIG` (another file for yours),
   `SESSIONVIEW_FROM` (the name mail is sent as, else `mail_from`, else
   `$USER`; `sessionview from` prints the name in effect), `SESSIONVIEW_STATE`
-  (state, default `~/.local/state/sessionview`), `SESSIONVIEW_PLUGINS`
-  (another plugin directory).
+  (state, default `~/.sessionkit/view/state`), `SESSIONVIEW_LOG` (the log
+  file, default `~/.sessionkit/view/log/sessionview.log`),
+  `SESSIONVIEW_PLUGINS` (another plugin directory).
 - sessionview does not read the kit's settings cascade today, only these.
 
 Every file, variable and tmux option is in
@@ -391,19 +420,25 @@ and every key in
 
 ## Logs
 
-- `~/.local/state/sessionview/sessionview.log`: what went wrong, one
+- `~/.sessionkit/view/log/sessionview.log`: what went wrong, one
   entry each, starting with the time (a failed tmux call, an uncaught
   error with its traceback). Follow it with
-  `tail -f ~/.local/state/sessionview/sessionview.log` when a click
+  `tail -f ~/.sessionkit/view/log/sessionview.log` when a click
   seems to do nothing.
+- **After an upgrade:** the log of earlier releases,
+  `~/.local/state/sessionview/sessionview.log`, stays where it is and
+  is never moved. Its last line names the new log, and the new log's
+  first line names the old one.
 - **Levels:** `log_level` in your settings (or `$SESSIONVIEW_LOG_LEVEL`
   for one run). `error`, the default, logs only what went wrong.
   `timing` adds a line per click or key with its milliseconds, and each
   command that took 50 ms or more, so a slow click names its slow part.
   `debug` adds every command and every mouse event (what the old
   `sidebar-mouse.log` held).
-- It sits under `$SESSIONVIEW_STATE` when that is set. It is not rotated:
-  turn `timing` or `debug` on while you look, then back to `error`.
+- `$SESSIONVIEW_LOG` names another log file. Without it, a
+  `$SESSIONVIEW_STATE` that names another folder keeps the log there, as
+  `sessionview.log`. It is not rotated: turn `timing` or `debug` on
+  while you look, then back to `error`.
 - **Health:** `sessionview install --check`: exit 0 and `ready` when
   every requirement is present, exit 1 with each MISSING one named
   otherwise. It checks the machine, not a running sidebar.

{sessionview-0.3.1 → sessionview-0.3.2}/README.md

@@ -9,8 +9,11 @@ Install from PyPI: `uv tool install sessionview` (see [Install](#install)).
 
     sessionview
 
-In this terminal, that puts the sidebar on the left and the session
-`main` on the right; a private outer tmux holds the two panes.
+In this terminal, that puts the sidebar on the left and a tmux session
+on the right; a private outer tmux holds the two panes. The session is
+one tmux already has: your default assistant's, else the one you last
+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).
@@ -75,8 +78,12 @@ agents, or the menu): the names `session start` knows, pinned ones first.
   not start. An agent already running is never started twice.
 - *Agents have a home* — an agent's own file says where it wakes
   (`start: directory:`); a project's menu starts it in the project.
-- *Consent on first open* — Dreamcatcher asks once which agent to start
-  when it opens (a numbered pick, or never), and remembers.
+- *Consent on first open* — the first time it opens, sessionview asks
+  which agent to start whenever it opens, and remembers the answer. It
+  says *sessionview can start an agent for you each time it opens*, lists
+  your agents by number and asks `Which? (number, name, or "n")`. When it cannot get the
+  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.
 
 **Settings** — every setting, its default, its note and where its value
 comes from, in a small screen (project menu → Settings); the rows come
@@ -118,7 +125,8 @@ hand. Blink Shell on iPad is wanted and not yet connecting.
                          claude-code: short, safe driving skills with tools
 
 Paths resolve from the checkout (`SESSIONVIEW_ROOT`); state lives in
-`~/.local/state/sessionview` (`SESSIONVIEW_STATE`). Its direct dependencies:
+`~/.sessionkit/view/state` (`SESSIONVIEW_STATE`) and the log in
+`~/.sessionkit/view/log` (`SESSIONVIEW_LOG`). Its direct dependencies:
 [dependencies](docs/dependencies.md).
 
 ## Install
@@ -218,14 +226,13 @@ beside it. Each line says what puts it there and what takes it away.
   sessionview` drops this package's entries, and `uv cache prune` drops
   the ones nothing uses.
 - **Folders, each made by a verb you run:**
-  - `~/.local/state/sessionview/`: the state folder, made the first time
-    `sessionview` opens (or `sessionview session` or `sessionview
-    messages` runs). `SESSIONVIEW_STATE` moves it. An older release's
-    `~/.local/state/herd/` is renamed to it then, when only the old
-    one exists. In it:
+  - `~/.sessionkit/view/state/`: the state folder, mode 0700, made the
+    first time `sessionview` opens (or `sessionview session` or
+    `sessionview messages` runs). `SESSIONVIEW_STATE` names another
+    folder instead. Each file sessionview makes in it is private (mode
+    0600). In it:
     - `frame-PID.tty`, one while each frame is open. The frame deletes
       it when it closes; a frame killed outright can leave it behind.
-    - `sessionview.log`, the log ([Logs](#logs)).
     - `recent.tsv`, a line each time `sessionview session` opens a
       project, for the picker's order.
     - `picker-order`, when you flip the picker's sort.
@@ -237,6 +244,23 @@ beside it. Each line says what puts it there and what takes it away.
     - `sidebar-remote-HOST.json`, what the sidebar last saw from each
       host in your `remotes` setting.
     - `mutt/`, an rc file for each box `sessionview messages` opens.
+  - `~/.sessionkit/view/log/`: the log folder, mode 0700, made at the
+    same time. It holds `sessionview.log` ([Logs](#logs)).
+    `SESSIONVIEW_LOG` names another log file. When `SESSIONVIEW_STATE`
+    is set, the log is `sessionview.log` in that folder instead.
+  - `~/.local/state/sessionview/`: the state folder of releases before
+    this one. Nothing new is made there. On an upgrade, the first start
+    hard-links `recent.tsv`, `picker-order`, `sidebar-mail.txt` and each
+    file in `mutt/` into the new state folder. The old names are kept,
+    so the two names are one file, and a sidebar still running from
+    before the upgrade stays correct. The old folder is left in place,
+    with the old `sessionview.log`, `sidebar-mouse.log`, the frame pins
+    and the plugin and remote files, which are not carried over. One
+    line is added to the end of the old log, naming the new one. Each
+    start sets the old folder to mode 0700, so the old names are private
+    too; the files in it keep their modes. An
+    older release's `~/.local/state/herd/` is renamed to this folder
+    first, when only the herd one exists.
   - `~/Applications/SessionView.app`: `sessionview install --app` (or
     `make app` in a checkout), or in `DEST` when that is set. It is
     built in a temporary folder that is deleted after, and a rebuild
@@ -303,21 +327,25 @@ rm ~/.local/bin/sessionview ~/.local/bin/sessionview-* ~/.local/bin/tmux-sidebar
 ```
 
 That leaves what the verbs made, listed above. The Dock app, the
-plugin's cached copy and the state folder are sessionview's alone. To
-delete them:
+plugin's cached copy, and the state and log folders are sessionview's
+alone. To delete them:
 
 ```bash
 rm -rf "${HOME:?}/Applications/SessionView.app"
 rm -rf "${HOME:?}/.claude/plugins/cache/sessionview"
+rm -rf "${HOME:?}/.sessionkit/view/state" "${HOME:?}/.sessionkit/view/log"
 rm -rf "${HOME:?}/.local/state/sessionview"
 ```
 
+The last line is for an upgrade from an earlier release: it removes the
+old state folder, with the old log in it.
+
 uv's cache stays too, with the other things uv installed; `uv cache
 clean sessionview` drops this package's entries. The key bindings go
 when your tmux server next exits.
 
 The rest is your data: delete it by hand only if you want it gone.
-`~/.sessionkit/view/` holds your settings, and the kit's other packages
+`~/.sessionkit/view/settings/` holds your settings, and the kit's other packages
 keep theirs beside it in `~/.sessionkit/`.
 
 ## Keys and clicks
@@ -363,8 +391,9 @@ The look follows herdr's; its colours were matched from herdr's own window.
 - **Environment:** `SESSIONVIEW_CONFIG` (another file for yours),
   `SESSIONVIEW_FROM` (the name mail is sent as, else `mail_from`, else
   `$USER`; `sessionview from` prints the name in effect), `SESSIONVIEW_STATE`
-  (state, default `~/.local/state/sessionview`), `SESSIONVIEW_PLUGINS`
-  (another plugin directory).
+  (state, default `~/.sessionkit/view/state`), `SESSIONVIEW_LOG` (the log
+  file, default `~/.sessionkit/view/log/sessionview.log`),
+  `SESSIONVIEW_PLUGINS` (another plugin directory).
 - sessionview does not read the kit's settings cascade today, only these.
 
 Every file, variable and tmux option is in
@@ -374,19 +403,25 @@ and every key in
 
 ## Logs
 
-- `~/.local/state/sessionview/sessionview.log`: what went wrong, one
+- `~/.sessionkit/view/log/sessionview.log`: what went wrong, one
   entry each, starting with the time (a failed tmux call, an uncaught
   error with its traceback). Follow it with
-  `tail -f ~/.local/state/sessionview/sessionview.log` when a click
+  `tail -f ~/.sessionkit/view/log/sessionview.log` when a click
   seems to do nothing.
+- **After an upgrade:** the log of earlier releases,
+  `~/.local/state/sessionview/sessionview.log`, stays where it is and
+  is never moved. Its last line names the new log, and the new log's
+  first line names the old one.
 - **Levels:** `log_level` in your settings (or `$SESSIONVIEW_LOG_LEVEL`
   for one run). `error`, the default, logs only what went wrong.
   `timing` adds a line per click or key with its milliseconds, and each
   command that took 50 ms or more, so a slow click names its slow part.
   `debug` adds every command and every mouse event (what the old
   `sidebar-mouse.log` held).
-- It sits under `$SESSIONVIEW_STATE` when that is set. It is not rotated:
-  turn `timing` or `debug` on while you look, then back to `error`.
+- `$SESSIONVIEW_LOG` names another log file. Without it, a
+  `$SESSIONVIEW_STATE` that names another folder keeps the log there, as
+  `sessionview.log`. It is not rotated: turn `timing` or `debug` on
+  while you look, then back to `error`.
 - **Health:** `sessionview install --check`: exit 0 and `ready` when
   every requirement is present, exit 1 with each MISSING one named
   otherwise. It checks the machine, not a running sidebar.

{sessionview-0.3.1 → sessionview-0.3.2}/bin/sessionview

@@ -6,7 +6,8 @@
 #        sessionview --help | --version
 #
 #   sessionview [SESSION]  the frame: sidebar on the left, SESSION attached on
-#                    the right (default main; a named SESSION must exist).
+#                    the right (default: one the server has, else main;
+#                    a named SESSION must exist).
 #                    --sock names its tmux server; --width, columns.
 #   sessionview config     settings: no verb opens the screen (get/set/list ...)
 #   sessionview session NAME    open a project session with its standard tabs
@@ -22,7 +23,7 @@
 #
 # Also: prefix H in any tmux client opens the sidebar as a popup.
 # Config: ~/.sessionkit/view/settings/view.json over the shipped config/config.json.
-# State: ~/.local/state/sessionview (SESSIONVIEW_STATE=).
+# State: ~/.sessionkit/view/state (SESSIONVIEW_STATE=). Log: ~/.sessionkit/view/log (SESSIONVIEW_LOG=).
 # (end of usage)
 # Ghostty was stripped out so this works in any terminal with only tmux. It
 # started as ghostty-herd; the Ghostty launcher, the split hook and cmd+d
@@ -66,7 +67,7 @@ case "${1:-}" in
       "$SESSIONVIEW_ROOT/bin/tmux-sidebar" --help >&2
       exit 2
     fi
-    SESSIONVIEW_STATE="${SESSIONVIEW_STATE:-$HOME/.local/state/sessionview}"; . "$SESSIONVIEW_ROOT/lib/state.sh"; . "$SESSIONVIEW_ROOT/lib/python.sh"; export SESSIONVIEW_ROOT SESSIONVIEW_STATE
+    . "$SESSIONVIEW_ROOT/lib/state.sh"; . "$SESSIONVIEW_ROOT/lib/python.sh"; export SESSIONVIEW_ROOT SESSIONVIEW_STATE
     # The supervisor: q = exit 0 = reload (picks up an edited tmux-sidebar or
     # sidebar.toml), Q = exit 3 = quit. A CRASH IS NOT A QUIT: any other exit
     # holds the error on screen and waits (one undefined name once took the
@@ -86,7 +87,9 @@ esac
 # (--sock, else this tmux's own server when run inside one, else default):
 # a typo or a probe word must not mean "open a frame on a new session named
 # after it". Read-only check; on a miss, usage and exit 2, nothing touched.
-# A new named session is `sessionview session NAME`. No word = main, as before.
+# A new named session is `sessionview session NAME`. No word: the frame picks
+# a session the server already has, and makes main only when it has none
+# (lib/landing.sh).
 word=""; sock=""; prev=""
 for a in "$@"; do
   case "$prev" in --sock) sock="$a"; prev=""; continue;; --width) prev=""; continue;; esac
@@ -110,5 +113,5 @@ if [ -n "$word" ]; then
   # the frame looks where this checked: inside tmux, the caller's own server
   [ -n "$extra" ] && set -- "$@" --sock "$sock"
 fi
-SESSIONVIEW_STATE="${SESSIONVIEW_STATE:-$HOME/.local/state/sessionview}"; . "$SESSIONVIEW_ROOT/lib/state.sh"; . "$SESSIONVIEW_ROOT/lib/python.sh"; export SESSIONVIEW_ROOT SESSIONVIEW_STATE
+. "$SESSIONVIEW_ROOT/lib/state.sh"; . "$SESSIONVIEW_ROOT/lib/python.sh"; export SESSIONVIEW_ROOT SESSIONVIEW_STATE
 exec "$SESSIONVIEW_ROOT/bin/sessionview-frame" "$@"

{sessionview-0.3.1 → sessionview-0.3.2}/bin/sessionview-autostart

@@ -116,9 +116,14 @@ sys.exit(1)' "$1"
 # that then fails to start. Empty output, missing command, any error: the
 # free-text question below still works, so this fails open like everything
 # else in this file.
+#
+# Each line is NAME, then a TAB and a mark (`claude<TAB>built in`), or the
+# NAME alone. Only the field before the first TAB is a name: the mark can hold
+# a space, and splitting the whole output on whitespace offered "built" and
+# "in" as agents.
 agent_list() {
   command -v session >/dev/null 2>&1 || return 0
-  session start --list-agents 2>/dev/null
+  session start --list-agents 2>/dev/null | awk -F '\t' '$1 != "" { print $1 }'
 }
 
 # Discard every byte waiting to be read on the terminal. ask() calls this once

{sessionview-0.3.1 → sessionview-0.3.2}/bin/sessionview-frame

@@ -7,7 +7,9 @@
 #
 #   sessionview-frame [SESSION] [--sock SOCKET] [--width N]
 #
-# SESSION   what the right pane attaches (default: main)
+# SESSION   what the right pane attaches (default: a session the server
+#           already has: the default seat's, else the last attached, else
+#           the newest; main, made, only when the server has none)
 # --sock    the tmux server SESSION lives on (default: default; a store's is
 #           tm-store-NAME)
 # --width   sidebar columns (default: config width via sessionview-config, else 34)
@@ -32,7 +34,7 @@ while [ $# -gt 0 ]; do case "$1" in
   *) SESSION="$1"; GIVEN=1;;
 esac; shift; done
 # The state dir and the Python only after the flags: -h touches nothing.
-SESSIONVIEW_STATE="${SESSIONVIEW_STATE:-$HOME/.local/state/sessionview}"; . "$SESSIONVIEW_ROOT/lib/state.sh"; . "$SESSIONVIEW_ROOT/lib/python.sh"; export SESSIONVIEW_ROOT SESSIONVIEW_STATE
+. "$SESSIONVIEW_ROOT/lib/state.sh"; . "$SESSIONVIEW_ROOT/lib/python.sh"; export SESSIONVIEW_ROOT SESSIONVIEW_STATE
 # The frame takes over the terminal it runs in, so it needs one: a script or
 # an agent's shell (stdin/stdout not a tty) is refused and nothing is touched.
 # Every refusal is one line on stderr, exit 2.
@@ -72,11 +74,21 @@ if [ -n "${TMUX:-}" ]; then
   # (measured: SESSIONVIEW_FRAME_SOCK set here did not reach the frame,
   # which landed on the default frame server) - carry what matters by hand.
   cmd="SESSIONVIEW_ROOT=$(q "$SESSIONVIEW_ROOT") SESSIONVIEW_STATE=$(q "$SESSIONVIEW_STATE") SESSIONVIEW_PYTHON=$(q "${SESSIONVIEW_PYTHON:-}")"
+  # A log the user gave goes too; a derived one never does (lib/state.sh).
+  if [ -n "${SESSIONVIEW_LOG:-}" ]; then cmd="$cmd SESSIONVIEW_LOG=$(q "$SESSIONVIEW_LOG")"; fi
   cmd="$cmd SESSIONVIEW_FRAME_SOCK=$(q "$FRAME_SOCK") TMUX="
   cmd="$cmd exec $(q "$0") $(q "$SESSION") --sock $(q "$SOCK")"
   [ -n "$WIDTH" ] && cmd="$cmd --width $(q "$WIDTH")"
   exec tmux -S "$here_path" detach-client -t "$ctty" -E "$cmd"
 fi
+# Outside tmux with no SESSION named: land in a session the server already
+# has (the default seat's, else the last attached, else the newest; the rule
+# and its reasons are in lib/landing.sh). `main` is made below only when the
+# server has no session at all.
+if [ -z "$GIVEN" ]; then
+  . "$SESSIONVIEW_ROOT/lib/landing.sh"
+  if sv_landing "$SOCK"; then SESSION="$SV_LANDING"; fi
+fi
 if [ -z "$WIDTH" ]; then
   WIDTH="$("$SESSIONVIEW_ROOT/bin/sessionview-config" get width 2>/dev/null || true)"
   WIDTH="${WIDTH:-34}"
@@ -209,7 +221,9 @@ o resize-pane -t "$SIDE" -x "$WIDTH"
 TTY="$(tty 2>/dev/null || echo none)"
 o set-hook -g "client-detached[$$]" "if -F '#{==:#{hook_client},$TTY}' 'kill-session -t =$F'"
 o select-pane -t "$MAIN"
-# pin = the client pane's tty: that is the client the sidebar may move
-o display-message -p -t "$MAIN" '#{pane_tty}' >"$PIN"
+# pin = the client pane's tty: that is the client the sidebar may move. Made
+# 0600: the umask is the subshell's alone, never this script's, which starts
+# the user's tmux server (a server keeps its umask for every pane it opens).
+( umask 077; o display-message -p -t "$MAIN" '#{pane_tty}' >"$PIN" )
 o attach -t "=$F"
 cleanup

{sessionview-0.3.1 → sessionview-0.3.2}/bin/sessionview-install

@@ -157,13 +157,15 @@ fi
 if command -v session >/dev/null 2>&1; then say PASS "session on PATH"
 else say WARN "session not on PATH - the sidebar lists tmux sessions without it, but no agent rows, so no agent menu (Message, Settle, ...), and no 'Start an agent' (uv tool install sessiontools)"; fi
 # neomutt - the messages tab (bin/sessionview-messages runs `neomutt -R`, exit 2 without
-# it). MISSING, not WARN: sessionview needs NeoMutt.
+# it). A WARN, not MISSING: that tab is made only when sessionmail, which is optional,
+# is installed, so sessionview runs without neomutt and the check still says ready.
+# (It was MISSING until 2026-10-28, when neomutt was ruled optional for the check.)
 if command -v neomutt >/dev/null 2>&1; then
   nv="$(neomutt -v 2>/dev/null | sed -n 's/^NeoMutt \([0-9]*\).*/\1/p' | head -1)"
   if neomutt -v 2>/dev/null | grep -q '+notmuch'; then say PASS "neomutt ${nv:-?} with notmuch"
   else say WARN "neomutt ${nv:-?} built without notmuch - the messages tab opens, with no sidebar (brew install neomutt)"; fi
 else
-  fail "neomutt - brew install neomutt (the messages tab)"
+  say WARN "neomutt not on PATH - the messages tab, which sessionview makes only when sessionmail is installed, cannot open (brew install neomutt)"
 fi
 # notmuch - the messages tab's sidebar queries Type: and Project:; unindexed, the Asks
 # rows are every mail to NAME+ask, with no error

{sessionview-0.3.1 → sessionview-0.3.2}/bin/sessionview-messages

@@ -108,16 +108,21 @@ if command -v notmuch >/dev/null 2>&1; then
     *) SIDEBAR_WHY="$FOLDER is not under notmuch database.path $DB";;
   esac; fi
 else SIDEBAR_WHY="no notmuch on PATH (brew install notmuch)"; fi
-SESSIONVIEW_STATE="${SESSIONVIEW_STATE:-$HOME/.local/state/sessionview}"; . "$SESSIONVIEW_ROOT/lib/state.sh"; STATE="$SESSIONVIEW_STATE/mutt"; mkdir -p "$STATE"
+. "$SESSIONVIEW_ROOT/lib/state.sh"; STATE="$SESSIONVIEW_STATE/mutt"; mkdir -p -m 700 "$STATE"
 RC="$STATE/${BOX//\//-}.rc"
-{
+# Written IN PLACE (> truncates the same file), never a temp file renamed over
+# it: the rc may have a second name, a hard link in the old state dir's mutt/
+# (docs/decisions/state-and-log-home.md, section 3). Made 0600 when it is new:
+# the umask is the subshell's alone, never this script's, which execs neomutt;
+# an existing rc keeps its mode.
+( umask 077; {
   printf 'set mbox_type=Maildir\nset folder="%s"\nset spoolfile=+\nset mark_old=no\n' "$FOLDER"
   [ -n "$SIDEBAR_WHY" ] && printf '# sidebar: %s\n' "$SIDEBAR_WHY"
   [ -n "$SIDEBAR" ] && printf '%s\n' "$SIDEBAR"
   printf 'source "%s"\n' "$SESSIONVIEW_ROOT/config/neomuttrc"
   [ -z "$SIDEBAR" ] && printf 'set sidebar_visible=no\n'
   [ -f "$VIEW_SETTINGS/neomuttrc" ] && printf 'source "%s"\n' "$VIEW_SETTINGS/neomuttrc"
-} >"$RC"
+} >"$RC" )
 if [ "$PRINT" = 1 ]; then
   echo "box=$BOX folder=$FOLDER rc=$RC"
   if [ -n "$SIDEBAR" ]; then echo "sidebar=$NAME, Asks, Asks · threads${SIDEBAR_WHY:+ ($SIDEBAR_WHY)}"