k0-board 0.2.0 → 0.4.0

package/CHANGELOG.md

@@ -6,6 +6,119 @@ All notable changes to this project are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.4.0]
+
+The file viewer stops being read-only, and stops being just a pile of documents. It now shows the
+folders a repository is built from, and behind a switch it shows the configuration too — an
+`.env`, a `package.json`, a workflow's YAML — laid out as the kind of thing each one is, and
+editable in place with a Save button. The name search, meanwhile, turns out to have been quietly
+wrong the whole time: it matched letters scattered across a whole path rather than the file you
+meant, and it now looks only at the name and shows you why a row is there at all.
+
+### Added
+
+- **Folders, at last.** The file viewer's listing starts with the folders, and clicking one takes
+  you inside it: the folders it holds first, then its files. The path is written across the top
+  one piece at a time and **every piece is a way back up** — from `docs/backlog/handover` you
+  reach `docs` in one click, and the whole repository by clicking its name. The path above an open
+  document does the same, so from a file you can step out into the folder it lives in. Arrow keys
+  walk folders, Enter goes in, Esc comes out, ⌘-click opens one in another tab, and the address
+  follows you so a reload puts you back where you were.
+- **Open in Finder.** A button on a folder opens that folder in your file manager, and the same
+  button in the row above a file points the file out inside its own folder. It works on macOS,
+  Windows and Linux; where a system gives k0 no way to do it, the button stays where it is, greyed
+  out, with the reason in its tooltip rather than quietly doing nothing.
+- **The `config` button beside the search shows the configuration.** The viewer lists
+  documents, which is right until the day you want to check a key in an `.env`. Switch it on and
+  `.env` (and `.env.local`, and the rest), `.json`, `.yml`, `.yaml`, `.toml` and `.ini` join the
+  listing, the name search and the search inside the text — **including the ones git is told to
+  ignore**, because an `.env` is ignored by definition and it is the file you came for. Code stays
+  out either way. The switch is remembered, per browser.
+- **Configuration opens as the kind of thing it is.** A **JSON** file becomes a tree that folds,
+  coloured by type, with the first two levels open — and with **its own search box**, because the
+  browser's find does not look inside a closed branch: on a folded tree ⌘F says "not found" for
+  something three lines away. This one counts what it found and opens the branches holding it. An
+  **.env** becomes a table of names and values, comments kept. **YAML, TOML and INI** keep their
+  shape, with keys, values and comments told apart by colour.
+- **Configuration and notes can be edited here, with a Save button.** The pencil in the row above
+  a document turns it into a text box as tall as the pane — not a small window over it, because a
+  README does not fit in one. ⌘S saves, Cancel goes back to what is on disk. Only `.env` and the
+  other configuration, `.md` and `.txt`: no code, no PDFs, no images, and no creating or deleting
+  files. If the file **changed on disk while you were editing it** — a session wrote it, or you
+  did, in another window — the save stops and says so, and what you typed stays exactly where it
+  is. k0 will not write over somebody else's work without telling you.
+- **A search whose best answer is switched off says so.** Looking for `.env` with the switch off
+  used to give eighty files that merely contain those four letters somewhere in their path, and no
+  hint that the one you wanted was a click away. Now a line appears above the results — *3
+  configuration files also match — show them* — and it is the button: clicking it turns the switch
+  on. It appears only when a hidden file would have come **above** everything on screen, so it is
+  not there on the searches where it would only be noise.
+- **The name search looks only inside the file's own name, and underlines what it found.** The
+  directory used to be searched too, scattered letters and all, which is how `.env` once turned up
+  `v1.0-ROADMAP.md` — three of its four letters came from `.planning/milestones/`, a folder nobody
+  was reading, with no way to see that from the row. Now the directory is never searched, and the
+  letters that matched are underlined right in the name: `aud`it-`rep`ort reads as the two words
+  you meant. Neighbouring letters are underlined as one stretch, not one by one. The mark is a
+  line and not the yellow used for the text search, so the two answers stay apart: yellow means
+  the word is inside the file, a line means it is in the name.
+
+### Changed
+
+- **On a card, the git mark sits against the right edge** instead of hanging off the end of the
+  repository's name, where it landed in a different place on every note. It is now the same shape
+  as the heading of a column, so a row of cards has a line you can read down. A long repository
+  name is cut with an ellipsis rather than pushing the mark about.
+- Nothing a user can see: the coverage floor moves up to 87% of lines and 85% of branches, which
+  is where the two new modules leave it.
+
+## [0.3.0]
+
+k0 could already tell you what each session was costing you in memory, and `Close` on a card was
+already how you gave it back. This version is k0 remembering to do that for you: a terminal left
+untouched all day is shut by itself, and the card it belongs to stays exactly where it was, ready
+to be picked up again. It is careful about which ones — never one that is working, never one with
+a question on screen — and it is the first thing in k0 you can change without changing k0, in a
+settings file that writes itself.
+
+### Added
+
+- **The terminals you have stopped using close themselves, and the work stays.** A session left
+  open goes on costing memory whether or not anybody is looking at it — the `claude` process, the
+  MCP servers it started, the browsers those opened — and `Close` on a card has always been the
+  cure. Now k0 remembers to do it for you: **after twelve hours with nothing happening, a yellow
+  card's terminal is shut and its memory given back**. Nothing is lost. The card stays exactly
+  where it is with the status it had, and **Resume** picks the conversation up where it was, the
+  same as it always did. Only yellow — *Your turn* — is ever touched: a card that is **working**
+  is somebody mid-thought, and a card with a **question or a plan on screen** would lose the very
+  thing it was showing you, because a dialog that is open has not been written to the transcript
+  yet. A session sitting in a **shell** is left alone too — there may be a command of yours
+  running in it, and k0 cannot see what. A window you were using an hour ago is never closed,
+  whatever the card's history says: every clock k0 has for that session is consulted and the
+  newest one wins.
+- **A card says who closed it, and the top bar says the closing is on.** Where a card used to read
+  *session closed* it now reads *closed automatically* if it was k0 that tidied it away — same
+  italic, same place, one word different. And the memory chip at the end of the top bar carries the
+  hours in lighter type: **RAM 79% · CPU 19% · closes at 8h**, with the whole sentence on hover.
+  That is where it belongs, because that is where the memory is already being talked about, and
+  something that closes your windows for you should never be a surprise. Switched off, the chip
+  says nothing rather than *0h* — which would read as "closes immediately" — and the hover says so
+  instead.
+- **Settings, in a file that is the list of them.** `~/.k0/config.json` — on Windows
+  `%LOCALAPPDATA%\k0\config.json` — written out on the first run with every setting already in it
+  at its default, so opening it is how you find out what there is to change. It sits beside the
+  board rather than inside the app, so an update cannot throw it away, and k0 picks up a change by
+  itself without anything being restarted. `closeIdleTerminalsAfterHours` is the first entry:
+  **set it to `0` and the closing above never happens**. There is no settings page on the board and
+  there is not going to be one — the board is for what changes during a working day —
+  so `k0-board doctor` prints the whole list too, with what is in force and where the file is.
+
+### Fixed
+
+- **Resuming a session no longer types the old prompt back in.** A card's prompt belongs to the
+  moment the session starts; on **Resume** the conversation had already answered it hours ago, and
+  putting it back under the cursor was at best something stale in the way — at worst it was sent,
+  because where pasting is not available k0 types it instead. Start is unchanged.
+
 ## [0.2.0]
 
 k0 could always tell you how the work stood. This version lets it tell you whether the work is
@@ -226,7 +339,9 @@ here is everything that had to change for it to be somebody else's tool as well.
 - The personal fixtures k0 grew up on. `test/clean.test.mjs` now fails the build if any of them
   come back.
 
-[Unreleased]: https://github.com/alessio-ragni/k0-board/compare/v0.1.2...HEAD
+[Unreleased]: https://github.com/alessio-ragni/k0-board/compare/v0.3.0...HEAD
+[0.3.0]: https://github.com/alessio-ragni/k0-board/compare/v0.2.0...v0.3.0
+[0.2.0]: https://github.com/alessio-ragni/k0-board/compare/v0.1.2...v0.2.0
 [0.1.2]: https://github.com/alessio-ragni/k0-board/compare/v0.1.1...v0.1.2
 [0.1.1]: https://github.com/alessio-ragni/k0-board/compare/v0.1.0...v0.1.1
 [0.1.0]: https://github.com/alessio-ragni/k0-board/releases/tag/v0.1.0

package/README.md

@@ -133,7 +133,7 @@ Nothing on this list happens before you have seen it and said yes. Everything on
 | What | Where | Why |
 |---|---|---|
 | A copy of k0 | `~/.k0/app` | so the service does not point at a temporary npx cache |
-| Your board, logs and cache | `~/.k0/` | `%LOCALAPPDATA%\k0` on Windows |
+| Your board, settings, logs and cache | `~/.k0/` | `%LOCALAPPDATA%\k0` on Windows |
 | A service that starts at login | LaunchAgents · systemd user unit · Task Scheduler | so k0 is simply there |
 | **macOS only** — one administrator rule | `/etc/sudoers.d/k0-pmset` | to keep the Mac awake with the lid closed. Asks for your password once, and grants exactly two command lines |
 | **macOS only** — one key binding | your Terminal profile (backed up first) | so Shift+Enter starts a new line |
@@ -200,8 +200,10 @@ k0 makes **no network requests**. Not one, not even for a font.
 - **double click** — brings that session's terminal back to the front, even if you had minimised
   it. It is what stops you losing track of which window is which.
 
-- **Resume** — appears once you have closed the terminal: it reopens the same conversation exactly
-  where it was.
+- **Resume** — appears once the terminal has been closed, by you or by k0 after a long silence: it
+  reopens the same conversation exactly where it was. The card's prompt is **not** put back in —
+  that conversation answered it hours ago, and typing it in again would be at best something stale
+  in the way.
 
 - **Done** — closes the work **and its terminal**, with no questions: undo it with **Reopen**, and
   pick the conversation up again with **Resume**. It is not on backlog cards: they never started.
@@ -396,12 +398,12 @@ yet — a **lens** takes its place, so every card and every column still leads i
 
 Files on the left, what they say on the right, and a divider in between that you can drag.
 
-**Only documents are listed** — markdown, html, text, PDF, Word: things you read and print. In a
-real repository code is 95% of the files, and among two thousand `.tsx` files the document you
+**Documents are what is listed** — markdown, html, text, PDF, Word: things you read and print. In
+a real repository code is 95% of the files, and among two thousand `.tsx` files the document you
 were after cannot be found. This closes nothing off: a code file reached by a link inside a
-document still opens, and so do images.
+document still opens, and so do images — and the configuration is one switch away, below.
 
-The listing is flat, in three groups:
+At the top come the **folders**, then the files, in three groups:
 
 - **Changed** — what this session has touched: files still hanging in the working tree plus the
   ones inside commits made since it started.
@@ -409,19 +411,91 @@ The listing is flat, in three groups:
   no git.
 - **All files** — everything else, in path order.
 
+### Searching
+
 The search at the top looks in two places and keeps them apart:
 
-- **Names** — not the exact word, but the letters you type in the order you type them: `audrep`
-  finds `docs/audit-report.md`. It filters as you type, asking the server nothing.
+- **Names** — not the exact word, but the letters you type in the order you type them, **inside
+  the file's own name**: `audrep` finds `docs/audit-report.md`. It filters as you type, asking the
+  server nothing. The directory is never searched — it used to be, and `.env` would turn up a
+  `v1.0-ROADMAP.md` that merely had those four letters scattered across its folder, three of them
+  in a name nobody was reading. The letters that matched are **underlined**, so every row says why
+  it is there: `aud`it-`rep`ort reads as the two words you meant.
 - **In the text** — inside the documents, with the line the word appears on and the word
-  highlighted. Because what you remember about a file is what was in it, not what it was called.
-  Accents do not need typing — `cafe` finds `café`.
+  highlighted in yellow. Because what you remember about a file is what was in it, not what it was
+  called. Accents do not need typing — `cafe` finds `café`.
+
+The two marks are different on purpose: a line under the letters means they are in the file's
+name, yellow means the word was found inside the file.
 
 There is no index. The documents are read every time: a few hundred files of a few KB, all
 already in the operating system's cache. An index would cost more and go stale.
 
 `/` puts the cursor in the search, arrows scroll, Enter opens, Esc clears.
 
+### Going into a folder
+
+Click a folder and the listing narrows to it: the folders inside it first, then its files. At the
+top the path is written out one piece at a time, and **every piece is a way back up** — from
+`docs/backlog/handover` you get to `docs` in one click, and to the whole repository by clicking
+the repository's name. The path above an open document works the same way, so from a file you can
+step into the folder it lives in.
+
+The arrows walk folders like anything else and Enter goes in; Esc comes back out. A folder is a
+real link, so ⌘/Ctrl-click opens it in another tab, and the address follows you: reload it and
+you are still where you were.
+
+Next to it is a button that hands the folder to your **file manager** — the Finder on a Mac,
+Explorer on Windows, whatever your desktop uses on Linux. Every file has the same button in the
+row above it, and there it points the file out inside its folder rather than opening it. On a
+system where k0 has no way to do that, the button stays where it is, greyed out, with the reason
+in its tooltip.
+
+### The `config` switch, beside the search
+
+The viewer lists documents. The one thing that was missing from that is **configuration**: an
+`.env` you want to check a key in, the `package.json`, a workflow's YAML. They are not documents,
+and in a repository of prose they would be noise — so they live behind a switch, the **`config`**
+button to the right of the search box.
+
+Switch it on and `.env` (and `.env.local`, and the rest of them), `.json`, `.yml`, `.yaml`,
+`.toml` and `.ini` join the listing, the name search and the search inside the text. **Including
+the ones git is told to ignore** — an `.env` is ignored by definition, and it is the file you came
+for. Code does not join: `.js`, `.py`, `.css` stay out either way.
+
+The switch is remembered, per browser. It is not a search, it is a way of working.
+
+And if you forget it is off, the search says so: when a hidden configuration file would have come
+**above** everything on screen — searching `.env` in a repository that has one — a line appears at
+the top of the results saying how many, and clicking it turns the switch on. Only then: a hidden
+file that merely matches somewhere does not raise it, or the line would be there on every search
+and you would stop seeing it.
+
+Each of them opens as the kind of thing it is:
+
+- a **JSON** file becomes a tree that folds, coloured by type, with the first two levels open;
+- an **.env** becomes a table of names and values, comments and all;
+- **YAML, TOML and INI** keep their shape, with keys, values and comments told apart by colour.
+
+A JSON tree has its **own search box**, and that is not a duplicate of the browser's: the
+browser's find does not look inside a branch that is closed, so on a folded tree ⌘F says "not
+found" for something three lines away. This one counts what it found and opens the branches
+holding it.
+
+### Editing a file
+
+Configuration and notes can be changed from here: `.env` and the rest of the configuration above,
+plus `.md` and `.txt`. Click the **pencil** in the row above the document and the file becomes a
+text box as tall as the pane — not a small window over it, because a README does not fit in one.
+**Save** (or ⌘/Ctrl+S) writes it; **Cancel** goes back to what is on disk.
+
+Nothing else is editable: no code, no PDFs, no images, and no creating or deleting files. That is
+what you opened the repository with Claude for.
+
+If the file **changed on disk** while you were editing — a session wrote it, or you did, in
+another window — the save stops and says so, and what you typed stays where it is. k0 will not
+quietly write over somebody else's work.
+
 ### Pasting a chunk of chat
 
 There is a way to reach files that does not go through searching for them. When a session ends,
@@ -512,6 +586,47 @@ Reading the process table costs little on a calm machine and a lot on a struggli
 exactly when you look at it. So it is sampled every three seconds, and **only while the board is
 open**.
 
+### And the ones you forget, k0 closes for you
+
+The paragraph above assumes you noticed. Most of the time nobody does: the window that is costing
+you a gigabyte is the one you stopped thinking about yesterday. So **after twelve hours with
+nothing happening, k0 does that `Close` itself** — the session is stopped, its window goes, and the
+memory comes back.
+
+Nothing is lost by it. The card stays exactly where it is with the status it had, and **Resume**
+picks the conversation up where it was. That is the whole reason this is safe: a closed terminal
+has never been a lost session.
+
+**Only yellow is ever touched** — *Your turn*, the ball in your court and nothing happening. The
+rest is left alone, and each for its own reason:
+
+- **Working** and **Planning** are somebody mid-thought. Stopping one is not memory saved, it is
+  work lost — the same rule the `Close` link has always followed.
+- **Needs answer** and **Needs approval** would lose the very thing they were showing you. A
+  question and a finished plan are drawn by the terminal and are not written to the transcript
+  until they are answered, so closing that window throws the question away.
+- A session sitting in a **shell** is left alone as well. That is a shell you dropped into, and
+  there may be a command of yours running in it; k0 cannot see what it is, so k0 does not touch it.
+  On the board it reads as yellow like any other, which is exactly why this one has to be said.
+
+And a window you were using an hour ago is never closed, whatever the card's history says. k0 has
+four clocks for a session — two of its own and two Claude Code keeps — and **the newest one wins**.
+Being wrong in that direction leaves a window open until tomorrow; being wrong the other way closes
+a terminal you were about to go back to.
+
+A card k0 tidied away says so: where one you closed yourself reads *session closed*, this one reads
+*closed automatically*. Same italic, same place, one word different.
+
+And the memory chip at the end of the top bar says it is watching, and from when: **RAM 79% · CPU
+19% · closes at 8h**, in lighter type than the numbers beside it. That is the whole announcement,
+and it is on that chip rather than anywhere else because that is where the memory is already being
+talked about — something that closes your windows for you should never be a surprise. Hover for
+the sentence. Switched off, the chip says nothing at all rather than *0h*, which would read as
+"closes immediately", and the hover is what tells you it is off.
+
+Twelve hours is what it does if you never say otherwise. `closeIdleTerminalsAfterHours` in the
+settings file changes it, and **`0` switches it off** — see below.
+
 ---
 
 ## Filling the board with what you have already done
@@ -722,6 +837,38 @@ Two side effects of the Cmd+V k0 uses to write your prompt, worth knowing:
 
 ---
 
+## Settings
+
+There is no settings page on the board, and there is not going to be one. The board is for what
+changes during a working day; a number you set once and then never look at again is the opposite of
+that, and putting it on screen would cost the one page that has to stay readable in exchange for
+nothing.
+
+So the settings are a file, and **the file is the list**:
+
+```
+~/.k0/config.json                        macOS and Linux
+%LOCALAPPDATA%\k0\config.json            Windows
+```
+
+k0 writes it on the first run with **every setting already in it at its default**, so opening it is
+how you find out what there is to change. It sits beside the board rather than inside the app —
+`npx` unpacks into a cache npm is free to wipe, and `k0-board install` overwrites the app
+directory, so a setting kept in there would not survive an update. Change it and k0 picks it up by
+itself on the next round: nothing to restart.
+
+| | |
+|---|---|
+| `closeIdleTerminalsAfterHours` | How long a yellow card's terminal may sit there before k0 closes it and gives the memory back. `12` if you say nothing. **`0` switches it off.** Anything under an hour is treated as an hour — below that this stops being a tidy-up and starts closing windows while you are using them. |
+
+Delete a line to go back to its default; a file k0 cannot read is ignored altogether and the
+defaults hold, rather than k0 refusing to start over a stray comma.
+
+**`k0-board doctor` prints the same list**, with the value actually in force and where the file is,
+for the times you would rather ask than go and look.
+
+---
+
 ## How it is put together
 
 No dependencies, nothing to compile. Change a file, reload the page.
@@ -744,7 +891,11 @@ server/
   guard.js       who is allowed to talk to this server at all: the Host and the Origin
   db.js          SQLite (node:sqlite): the card, session_event, pref and dev_server tables —
                  docs/database.md
-  paths.js       where the board, the logs and the cache live
+  paths.js       where the board, the logs, the settings and the cache live
+  settings.js    the few things you can change, and the file that is the list of them —
+                 ~/.k0/config.json, written out with everything in it and re-read when it changes
+  idle.js        which terminals have sat still long enough to be closed and given back. Only the
+                 deciding: it kills nothing, so every rule in it can be proved without a machine
   watcher.js     reads Claude Code's own files and derives the statuses; also renames a session
   git.js         the only one that talks to git: what is committed, what is pushed, whose it is,
                  and — for the ChangeLog — what the commits actually said
@@ -758,7 +909,8 @@ server/
   mode.js        the four modes: how awake to keep the machine, and whether the text goes large
   projects.js    the repositories, in the order you last used them
   sessions.js    digs already-lived sessions out of the transcripts, to import as cards
-  files.js       the only one that reads the projects' disk: what is there, what changed, what it says
+  files.js       the only one that reads the projects' disk — and the only one that writes back
+                 into it: what is there, what changed, what it says, and the one small write
   machine.js     the only one that looks at processes and memory: what it all costs, and who is costing it
   pdf.js         the document on paper, printed by a headless browser
 web/             the three pages (html, css, js served exactly as they are)
@@ -774,6 +926,8 @@ web/             the three pages (html, css, js served exactly as they are)
   fuzzy.js       searching the names: the letters you type, in the order you type them
   mentions.js    which of a repository's files a piece of text names
   refs.js        what a name written inside a document points at, and which of the nine READMEs
+  json.js        a JSON file as a tree that folds, and the search that opens the right branches
+  conf.js        an .env as the table it always was, and YAML/TOML/INI with their parts told apart
 .claude/skills/
   k0-import/     the skill that fills the board with sessions you have already had
   k0-changelog/  the one that turns the facts of a stretch of work into something readable. k0
@@ -792,6 +946,12 @@ test/            npm test — Node's own runner, no framework. See docs/testing.
 
 ### What it reads, and what it never does
 
+k0 reads your repositories. It writes into one of them in exactly one place: the pencil in the
+file viewer, on a configuration file or a note that is already there. That write is deliberately
+narrow — no code, no new files, no deletions — it carries the file's own permissions across, it
+lands as a rename so an interrupted save leaves the old file whole, and it refuses outright if the
+file has changed on disk since the page read it.
+
 k0 does not emulate a terminal and installs no hooks. It reads two things Claude Code already
 writes for itself:
 
@@ -905,11 +1065,12 @@ The full picture, and how to report a problem privately, is in [SECURITY.md](SEC
 
 ## What is not here yet
 
-Checkboxes inside a card. In the viewer only documents are listed: code opens if you arrive at it
-from a link, but it is not browsable and the text search does not look at it. Files are read only:
-they are not edited, not diffed, and you cannot talk to them — for that you open the repository
-with Claude. Sessions opened by hand outside k0 are picked up with `/k0-import`, on request:
-nothing notices them by itself yet.
+Checkboxes inside a card. In the viewer the listing is documents and configuration: code opens if
+you arrive at it from a link, but it is not browsable and the text search does not look at it.
+Only configuration and notes can be edited, one file at a time — nothing is diffed, no file is
+created or deleted, and you cannot talk to them; for that you open the repository with Claude.
+Sessions opened by hand outside k0 are picked up with `/k0-import`, on request: nothing notices
+them by itself yet.
 
 ## Contributing
 

package/bin/k0-board.js

@@ -48,6 +48,7 @@ if (Number(process.versions.node.split('.')[0]) < MIN_NODE) {
 
 const { name: platformName, capabilities, notes, service, extras, shell } = await import('../platform/index.js')
 const paths = await import('../server/paths.js')
+const settings = await import('../server/settings.js')
 
 const APP_DIR = flag('from-source') ? SOURCE : paths.APP_DIR
 const ENTRY = path.join(APP_DIR, 'server', 'index.js')
@@ -417,9 +418,24 @@ async function doctor() {
     ['read the kernel memory-pressure verdict', capabilities.metrics.pressure],
     ['start at login', capabilities.service.autostart],
     ['show a tray icon', capabilities.tray],
+    ['show a file in the file manager', capabilities.revealInFileManager],
+    ['open a folder in the file manager', capabilities.openInFileManager],
   ]
   for (const [what, yes] of rows) (yes ? ok : warn)(what)
 
+  // The settings, in full, with what is actually in force. k0 has no settings page and is not
+  // getting one, so this — and the file itself — is where the list lives. Printing every key
+  // rather than only the ones somebody has changed is the point: it is an inventory.
+  step('Settings')
+  const conf = settings.status()
+  say(dim(`  ${conf.path}${conf.exists ? '' : ' (not written yet — the defaults are in force)'}`))
+  if (conf.broken) warn('this file could not be read: it is being ignored and the defaults are in force')
+  for (const [key, value] of Object.entries(conf.values)) {
+    const dflt = settings.DEFAULTS[key]
+    const off = key === 'closeIdleTerminalsAfterHours' && value === 0
+    say(`  ${bold(key)}  ${off ? 'off' : value}${value === dflt ? dim(' (default)') : dim(` (default ${dflt})`)}`)
+  }
+
   const explained = Object.entries(notes)
   if (explained.length) {
     step('Why not')

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "k0-board",
-  "version": "0.2.0",
+  "version": "0.4.0",
   "description": "A board of sticky notes that drives your Claude Code sessions",
   "keywords": [
     "claude-code",

package/platform/contract.js

@@ -40,7 +40,8 @@
  * @property {object} service
  * @property {boolean} service.autostart             can register a service that starts at login
  * @property {boolean} tray                          a menu bar / system tray icon is available
- * @property {boolean} revealInFileManager
+ * @property {boolean} revealInFileManager           can show a file selected in the file manager
+ * @property {boolean} openInFileManager             can open a directory in the file manager
  */
 
 /**
@@ -55,6 +56,7 @@ export const NO_CAPABILITIES = {
   service: { autostart: false },
   tray: false,
   revealInFileManager: false,
+  openInFileManager: false,
 }
 
 /**
@@ -133,6 +135,10 @@ export const NO_CAPABILITIES = {
 /**
  * @typedef {object} ShellAdapter
  * @property {(absPath: string) => Promise<unknown>} revealInFileManager
+ *   Shows the file in its own folder, selected. A folder handed to this gets selected in its
+ *   parent, which is the neighbouring thing and not the same one.
+ * @property {(absDir: string) => Promise<unknown>} openInFileManager
+ *   Opens the directory itself, so you are looking at what is inside it.
  * @property {(url: string) => Promise<unknown>} openBrowser
  * @property {() => string|null} findChrome        a Chromium-family browser able to print
  * @property {() => Set<string>} homeSkipList      directories under $HOME that are never projects

package/platform/darwin/index.js

@@ -18,6 +18,7 @@ export const capabilities = {
   service: service.capabilities,
   tray: true,
   revealInFileManager: true,
+  openInFileManager: true,
 }
 
 /**

package/platform/darwin/shell.js

@@ -7,6 +7,9 @@ const OPEN = () => which('open', ['/usr/bin/open'])
 
 export const revealInFileManager = (abs) => run(OPEN(), ['-R', abs], { timeout: 4000 })
 
+/** Without `-R` the Finder opens the directory instead of picking it out in the one above. */
+export const openInFileManager = (abs) => run(OPEN(), [abs], { timeout: 4000 })
+
 export const openBrowser = (url) => run(OPEN(), [url], { timeout: 4000 })
 
 /**
@@ -56,4 +59,4 @@ export function findClaude() {
   return claudeBin
 }
 
-export const capabilities = { revealInFileManager: true }
+export const capabilities = { revealInFileManager: true, openInFileManager: true }

package/platform/index.js

@@ -65,6 +65,7 @@ const unsupported = {
   },
   shell: {
     revealInFileManager: async () => {},
+    openInFileManager: async () => {},
     openBrowser: async () => {},
     findChrome: () => null,
     homeSkipList: () => new Set(),

package/platform/linux/index.js

@@ -24,6 +24,7 @@ export const capabilities = {
   service: service.capabilities(),
   tray: !!which('python3'),
   revealInFileManager: shell.capabilities().revealInFileManager,
+  openInFileManager: shell.capabilities().openInFileManager,
 }
 
 export const notes = {
@@ -61,6 +62,16 @@ export const notes = {
           'Neither ss nor lsof was found, so k0 cannot see which port a dev server is listening ' +
           'on. Install iproute2 (for ss) and the globe will know where to send you.',
       }),
+  ...(capabilities.openInFileManager
+    ? {}
+    : {
+        revealInFileManager:
+          'xdg-open was not found, so k0 has no way to hand a file or a folder to your file ' +
+          'manager. Install xdg-utils and the button will work.',
+        openInFileManager:
+          'xdg-open was not found, so k0 has no way to hand a file or a folder to your file ' +
+          'manager. Install xdg-utils and the button will work.',
+      }),
   ...(capabilities.servers.adopt
     ? {}
     : {

package/platform/linux/shell.js

@@ -31,6 +31,15 @@ export async function revealInFileManager(abs) {
   if (open) await runQuiet(open, [path.dirname(abs)])
 }
 
+/**
+ * Opening a directory needs none of the dance above: every desktop that has a file manager at
+ * all hands a directory to it through xdg-open.
+ */
+export async function openInFileManager(abs) {
+  const open = XDG_OPEN()
+  if (open) await runQuiet(open, [abs])
+}
+
 export const openBrowser = (url) => run(XDG_OPEN(), [url], { timeout: 4000 })
 
 const CHROME_CANDIDATES = [
@@ -94,4 +103,4 @@ export function findClaude() {
   return claudeBin
 }
 
-export const capabilities = () => ({ revealInFileManager: !!XDG_OPEN() })
+export const capabilities = () => ({ revealInFileManager: !!XDG_OPEN(), openInFileManager: !!XDG_OPEN() })

package/platform/win32/index.js

@@ -24,6 +24,7 @@ export const capabilities = {
   service: service.capabilities(),
   tray: hasPowerShell(),
   revealInFileManager: true,
+  openInFileManager: true,
 }
 
 export const notes = {

package/platform/win32/shell.js

@@ -8,6 +8,9 @@ const EXPLORER = () => which('explorer') || 'explorer.exe'
 /** `explorer /select,` opens the folder with the file already highlighted. */
 export const revealInFileManager = (abs) => runQuiet(EXPLORER(), [`/select,${path.normalize(abs)}`])
 
+/** The same command without `/select,` opens the folder itself. */
+export const openInFileManager = (abs) => runQuiet(EXPLORER(), [path.normalize(abs)])
+
 export const openBrowser = (url) => runQuiet('cmd', ['/c', 'start', '', url])
 
 const programFiles = [
@@ -61,4 +64,4 @@ export function findClaude() {
   return claudeBin
 }
 
-export const capabilities = () => ({ revealInFileManager: true })
+export const capabilities = () => ({ revealInFileManager: true, openInFileManager: true })

package/server/db.js

@@ -73,6 +73,7 @@ for (const [col, decl] of [
   ['imported_at', 'INTEGER'],
   ['work_path', 'TEXT'],
   ['head_at_start', 'TEXT'],
+  ['auto_closed', 'INTEGER NOT NULL DEFAULT 0'],
 ]) {
   const has = db.prepare('SELECT 1 FROM pragma_table_info(?) WHERE name = ?').get('card', col)
   if (!has) db.exec(`ALTER TABLE card ADD COLUMN ${col} ${decl}`)
@@ -214,6 +215,16 @@ export function setWorkPath(id, workPath) {
   return getCard(id)
 }
 
+/**
+ * Who shut this session's terminal: you, or k0 tidying up after a long silence. The card says so
+ * in one word, and the word has to be right — a window you closed yourself two minutes ago must
+ * not claim k0 did it. Does not touch `updated_at`: this is not work on the card.
+ */
+export function setAutoClosed(id, on) {
+  db.prepare('UPDATE card SET auto_closed = ? WHERE id = ?').run(on ? 1 : 0, id)
+  return getCard(id)
+}
+
 /** Where HEAD was when the session started: everything after it is this session's doing. */
 export function setHeadAtStart(id, sha) {
   db.prepare('UPDATE card SET head_at_start = ? WHERE id = ?').run(sha || null, id)