Skip to content

v2026.11.1

Choose a tag to compare

@hex hex released this 02 Nov 20:44

What's Changed

Features

  • cs -config set <KEY> <value> keeps a cs setting in ~/.config/cs/config, and cs <name> -config set in that session's own .cs/local/config, which outranks it there. Every cs command, hook and status line repaint reads both files each time it runs, a cs -spawn window and a teammate pane included, so an edit applies without a relaunch, and your shell's export of a key still wins over both. cs -config get prints the value readers see, unset removes one, reset removes every one the file holds after asking on a terminal (--yes skips the question, and without a terminal it refuses with no --yes), and list prints all 43 settings with each value, where it comes from and when a change applies, then every line the files skip with its line number and why; list --porcelain prints one tab-separated record per setting for tools, its last field a sentence on what the setting does; the configuration docs list its twelve fields. set refuses a key no file keeps (secrets, programs cs runs, paths, CS_ACTOR, CS_STATUSLINE_CAPS) and a value the setting's readers would not take, each by name. The file is KEY=value lines, never run as shell; the writer keeps every other line as typed. A launch hands claude no value it read from a file. cs -doctor names each skipped line and each value your environment hides from a file, and its Authority rows say where each switch comes from; cs -uninstall keeps the file.

  • Bare /cs (and /cs-panel) opens the settings pane: every cs setting cs -config list names, under its group, with its value, where it comes from and when a change applies, and above them the /config rows of the cs, cs-update, cs-mermaid and cs-filter-chat mods. The pane draws in the cs-tui binary's language: the claude-sessions wordmark in the installer's banner box with the cs version, the counts of settings and overrides and the session name, and a second line in the box naming a newer cs and cs -update when the launch found one, each group's name over a rule, ● on and ○ off toggles, a percent as its number and %, every value in ink with the source word in colour the only mark of an override, and every other colour a Claude Code theme key, so the pane follows your theme (auto, dark or light) with no setting. Below 72 columns, as in the dock, a row shows its name and value; from 72 its source and when a change applies too. The whole row is one button the focus inverts. Under the rows, the footer for the selected row says what the setting does, its whole value, where it comes from and when a change applies, its key, and the keys that act on it, or why Enter cannot change it. A flag whose 1 turns its feature off reads in the feature's terms, ● on while unset. It opens in a filter field: typing shows only the rows whose label, key or group holds the text, with how many show of the total beside the column header, Enter moves to the first row shown, the arrows walk the rows, Up from the first returns to the field, Esc closes. Enter on an on/off setting no file holds flips it at once, and Enter on a /config toggle flips it; the keys' line says Enter flip on both. Enter on any other row opens its chooser right under it in the pane, a line of buttons (more lines where they do not fit) that the arrows walk and Enter picks: a typed setting gives a field holding its value, a choice gives a picker of every choice and a flag a file holds a picker of on and off, the current one selected, where the arrows move and Enter picks (the mobile app draws no picker, so there the other choices are buttons and a flag offers Turn on or Turn off), and each offers Default while a file holds the value (a typed setting always) and Keep, which closes the chooser; the write is cs -config set, or $.config.set for a mod row. Under a session name the footer's last line, writes to: ● this session ○ this machine, picks the file a write goes to, this session's until you pick the other; a value this session's file already holds changes there. reset all…, at the right end of the keys' line, swaps that line for remove N overrides from this session's file · confirm · keep, naming the file the scope line picks, and confirm runs cs -config reset --yes on it. No change opens a dialog, so the pane keeps the keyboard. A setting your shell exports, CS_NO_FUNCTION_HOOKS and a managed /config row take no change and say why. The pane reads cs again after each change and at the end of each turn, and runs no clock. /cs <argument> still scrolls the rail. This release drops the sessions list the pane showed before, and cs -list --porcelain, which only that list read.

  • Every prompt of the lead carries one sentence asking Claude to append a finding worth keeping (a decision and its reason, a measured fact, a failed approach, a preference you state) to its own narrative before its final answer, and says routine work is not a finding. The narrative reminder reaches Claude only with your next prompt, so a finding from the last turn before you leave was lost; this line asks for it in that turn. A tmux teammate and a nested claude -p get none. CS_NARRATIVE_PROMPT_DISABLE=1, a row in /cs, turns it off, and so does CS_SCOPE_DISABLE=1.

  • install.sh ships the cs-filter-chat mod. While it is on, the chat shows what you type and what Claude answers, and nothing of the work between them. It is off by default; /filter-chat, or the cs band's key, which reads filter chat ● while on, its dot green, and filter chat ○ while off, switches it for that session. It is the cs setting CS_FILTER_CHAT, so cs -config and the /cs pane list it too. It draws in Claude Code theme keys, so its inks follow your theme on every draw, auto included: your line in remember, a safeguard stop in merged, an error you must act on in error, and one Claude Code handles in text. Your lines' colour is a /config row, cs-filter-chat.youInk, which the /cs pane lists too: remember (blue, the default), planMode (teal), success (green), merged (violet), error (red) or text (plain). An install removes the files it wrote under the old name, ~/.claude/skills/cs-chat-only/, and keeps any it did not, with a warning naming each.

  • On a resume in a git repository, the Session State block ends with a line saying the conversation before this one may have finished actions its summary does not show, and to check git log, cs -msg log and the remote before repeating a push, a merge, an install or a message. The block now prints on every such resume, even with no recent commits to report.

Changed

  • A directory lock is a claim file inside it, not a mkdir alone. Ubuntu 26.04 ships Rust uutils coreutils, whose mkdir exits 0 when a racing mkdirat returns EEXIST, so two takers could both read success: the integrate lock (cs -integrate-feature and the autosave hook), the usage refresher's lock in cs-statusline and the test runner's lane claim now settle the race with bash's own noclobber open of a claim file, which exactly one writer creates.
  • An ordinary Stop costs about 100 ms less in each of stop-blocks.sh and stop-notices.sh, measured as 15-run medians on one input: the libraries' bash -n checks are memoised per file version under ~/.cache/cs/parsed/, the path helpers every write takes start no dirname or basename, and each hook reads the Stop input with one jq.
  • hooks/narrative-reminder.sh is now hooks/stop-blocks.sh. The hook has not reminded about the narrative since those notices moved to stop-notices.sh: it drains the task queue, reports a staged retire, wakes on unread mail and posts the verdict stop-notices.sh waits for, and every answer it gives is a block. An upgrade removes the deployed old file and re-registers its Stop, FileChanged and CwdChanged entries under the new name. .cs/.narrative-reminder-cooldown keeps its name: it belongs to the narrative reminder.
  • A feature session's claude is named with a + for the @ (cs myproj@fix-auth runs claude --name myproj+fix-auth, and --remote the same server name). Claude Code's SendMessage refuses any address with an @ in it, so no peer session could message a feature's conversation, though ListAgents listed it. The + form is what Claude Code shows and what the live-duplicate guard and the served check read back from ps; the directory, CLAUDE_SESSION_NAME, cs -msg and every other cs surface keep base@feature. The + form typed into cs (cs base+feature, cs -rm base+feature, a mail target) is refused by name with the @ form and creates nothing; a feature session's context tells the model both addresses; and the duplicate guard and the served check still count a feature or its server launched under the @ name before this release.
  • cs -list prints the cs-tui hint from the listing itself, so cs -list --bogus prints only the error.
  • cs says one word for one condition. A running conversation reads live in the lock refusal and menu, the duplicate guard, /finish, the remote and encrypt refusals and the TUI (Session is live (PID n)), and the TUI preview shows live · pid N or live · heartbeat; locked is the vault's word. Feature readiness reads as the same sentences in cs <base> -features, the TUI and the cs mod's band (uncommitted changes, base session is live, retire staged, no commits), and --porcelain keeps the raw state keys. cs -queue list heads its tasks Queued (n), and the TUI calls its pane queue in the title, the footer and the legend.
  • The rotation nudge, the context warning and the narrative reminder no longer draw Claude Code's Ran N stop hooks row in the chat. They come from a second Stop hook, stop-notices.sh, registered as async, and reach Claude as context with your next prompt, so they never start or extend a turn. An armed or draining task queue still gets none of them, and neither does any Stop the first hook answers with a block (a drain that ends or parks, a staged retire, a mail wake): that hook posts its verdict to .cs/local/stop-verdict, keyed to the Stop by the input's cksum and the transcript's size, and the async one waits for it, two seconds when no verdict is coming and at most eight while one is pending; the whole run ends inside an 8 s budget whatever it waits on. The notices are worded for where they land, beside your next request and about the turn before it; the narrative reminder asks for what that turn found, says a line that restates routine work is not a finding, and names the empty case. A context notice stamps its cursor after it prints, and goes out once more on a later Stop when the transcript records no async_hook_response attachment carrying it, that repeat stamped before it prints so it cannot come back on every Stop; the cursors and the narrative reminder's cooldown are stamped under one lock, so two overlapping runs send one notice.
  • The narrative reminder reads only your own narrative, narrative.<actor>.md, to decide whether it is stale: a teammate writing theirs no longer holds yours back, and a session with no narrative of yours is reminded. The reminder names that file (Yours is ...) where it named the newest narrative on disk.
  • The narrative reminder is gated on work, not on a 5-minute clock: it goes out when the conversation made an edit, a commit, or 800 or more characters of text since your narrative was last written, counted from the conversation's transcript past a cursor in .cs/local/narrative-cursor.<session_id>, and never twice within 60 s. A quiet turn no longer draws a reminder, and a busy one is not held back by a reminder minutes ago. Without a transcript to read, the 5-minute cooldown decides as before.

Docs

  • docs/rejected-designs.md lists the designs cs rejected or declined, each with its reason and date, so a contributor or a later session does not propose one again; the README's Documentation table links it.

Full Changelog: v2026.10.11...v2026.11.1

Full Changelog: v2026.10.11...v2026.11.1