@puddle-code/cli 0.0.13 → 0.0.15

package/CHANGELOG.md

@@ -7,14 +7,9 @@ Past releases: see docs/changelogs/.
 
 # Changelog
 
-## [0.0.13] — 2026-07-28
+## [0.0.15] — 2026-07-29
 
-### Changed
+### Added
 
-- Desktop (macOS): the native title bar is gone — the cockpit's own top bar (host, ⌘K field, settings, scratchpad, profile) doubles as a taller drag-region title bar with the traffic lights inlaid.
-- The window/tab title now names the project and the machine (host display-name customisation first, then hostname) instead of the literal "puddle".
-- Desktop: copyright credits Yiding Song (About panel / bundle metadata); the package is `@puddle-code/desktop`.
-
-### Fixed
-
-- Desktop (macOS): the app icon no longer sits on a white plate on macOS 26 — the icns now ships full-bleed artwork (`build/icon-mac.svg`) and the OS applies its own squircle mask; Linux keeps the self-rounded `icon.svg`.
+- Previews typeset **LaTeX** with KaTeX — `$…$` / `\(…\)` inline, `$$…$$` / `\[…\]` / ` ```math ` display — in both the markdown and the HTML view. KaTeX over MathJax: it is synchronous and needs no live document, so a preview re-renders on every keystroke and the sandboxed HTML iframe's maths is typeset before the document is serialised into it (its fonts travel baked into the document, since a null origin cannot load a font from ours). `$…$` follows pandoc's rules, so prose currency stays prose.
+- README: hero screenshot of the desktop cockpit — a live Claude Code session split beside the rendered README (light + dark under `docs/assets/`).

package/README.md

@@ -6,11 +6,18 @@
 Puddle is an open-source, multi-account coding agent orchestrator with first-class SSH support and a lightweight GUI. With a single command,
 
 ```bash
-puddle connect <user>@<host>
+puddle launch <user>@<host>
 ```
 
 Puddle manages parallel agents anywhere you SSH into, insulates agents in dedicated worktrees, and keeps your agents alive across disconnects and restarts.
 
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="docs/assets/cockpit-dark.png">
+    <img src="docs/assets/cockpit-light.png" alt="The Puddle desktop app: a live Claude Code session split beside the rendered README, with the file explorer on the left and parallel agent sessions on their own branches and accounts in the sidebar" width="920">
+  </picture>
+</p>
+
 ## Quick start
 
 **On your local machine where you will be using the GUI, run:**
@@ -22,7 +29,7 @@ npm install -g @puddle-code/cli
 **To launch agents on a remote host:**
 
 ```sh
-puddle connect <user>@<host>
+puddle launch <user>@<host>
 ```
 
 This connects Puddle to the remote host over SSH, bootstrapping the Puddle daemon on first contact and enabling you to begin development.
@@ -32,7 +39,7 @@ Puddle works using your system `ssh`, so `~/.ssh/config`, agents, and jump hosts
 **For development on your own machine:**
 
 ```sh
-puddle start
+puddle launch
 ```
 
 This installs the Puddle daemon under `~/.puddle` and serves the GUI at `http://localhost:7433`.
@@ -106,7 +113,7 @@ systemctl --user disable --now puddled              # Linux (systemd user unit)
 kill "$(cat ~/.puddle/puddled.pid)"                 # nohup fallback (no supervisor)
 ```
 
-**Restore the production daemon.** When you're done testing, put the release build back over your dev one: stop the daemon (above), clear the installed binaries with `rm -rf ~/.puddle/bin` (your `~/.puddle` state — profiles, sessions, worktrees — is untouched), then run the production `puddle start`, which refetches the daemon from GitHub Releases. (Clearing `bin` is what forces the refetch: the installer skips a version whose files are already present, so a dev build sharing the release's version number would otherwise stay put.)
+**Restore the production daemon.** When you're done testing, put the release build back over your dev one: stop the daemon (above), clear the installed binaries with `rm -rf ~/.puddle/bin` (your `~/.puddle` state — profiles, sessions, worktrees — is untouched), then run the production `puddle launch`, which refetches the daemon from GitHub Releases. (Clearing `bin` is what forces the refetch: the installer skips a version whose files are already present, so a dev build sharing the release's version number would otherwise stay put.)
 
 **Uninstall.** Removing the CLI alone leaves the daemon installed and running — a full teardown stops the daemon, then removes its state, its service file, and the production CLI: