@supanadit/morse-web 0.12.0 → 0.14.0

package/README.md

@@ -1,7 +1,13 @@
 # @supanadit/morse-web
 
-**Morse in your browser, as one npm package.** It serves the same Angular frontend and drives the same
-[Pi](https://github.com/earendil-works/pi) coding agent as the VS Code extension — no VS Code required.
+[![npm](https://img.shields.io/npm/v/@supanadit/morse-web)](https://www.npmjs.com/package/@supanadit/morse-web)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://github.com/supanadit/morse/blob/master/LICENSE)
+[![Node.js](https://img.shields.io/badge/node-%E2%89%A520-brightgreen)](https://nodejs.org)
+
+**Morse in your browser, as one npm package.** It serves the same Angular chat UI and drives the same
+[Pi](https://github.com/earendil-works/pi) coding agent as the VS Code extension — no editor required. Start it,
+open the URL, and you get your existing pi models, credentials, tools and sessions in a real interface instead
+of a terminal TUI.
 
 ```bash
 npm install -g @supanadit/morse-web
@@ -21,10 +27,40 @@ morse start
 
 Then open <http://127.0.0.1:4399/>. The server keeps running in the background; stop it with `morse stop`.
 
+![Morse in the browser](https://raw.githubusercontent.com/supanadit/morse/master/docs/assets/demo-web.gif)
+
+## Why
+
+- **Your Pi, not a hosted service.** Morse spawns `pi --mode rpc` on your machine and reads the same `~/.pi`
+  sessions. Nothing is re-implemented and no API key is stored by Morse.
+- **No editor needed.** A small NestJS host serves the UI on `127.0.0.1`, so you can drive the agent from any
+  browser — on a headless box, over SSH port-forwarding, or beside a remote dev machine.
+- **One package.** The frontend is prebuilt and the `@morse/*` libraries are inlined into a single bundle, so
+  there is nothing else to install beyond Node and `pi`.
+
+## Features
+
+- **A chat that streams** — answers, thinking and tool calls as they arrive, a compact expandable tool tree
+  (with a one-click legacy timeline), paged history and context compaction.
+- **Sessions kept warm across projects** — one `pi` process per session (LRU-capped, `MORSE_HOT_SESSIONS`
+  default 4); reloading the page reattaches and replays the transcript instead of respawning.
+- **The browser host's own tools** — a **git panel** (commit list, branch graph, staged/unstaged changes, pull /
+  push / commit / branch switch), a file **Explorer** with read-only previews and diff views, and a **bottom
+  panel** with real terminals that survive a reload.
+- **Manage MCP servers** — list every server pi sees for the project (state, tools, errors) and add, remove,
+  enable or disable one, with per-project overrides.
+- **Model & thinking control that follows Pi** — the thinking picker mirrors exactly the levels the current model
+  supports in Pi's TUI, and a model added to `models.json` appears when you open the picker (no restart).
+- **Attach context anywhere** — drag, drop and paste files or images; uploaded files land next to the session as
+  `@mentions`, and a picked line range travels as `path:start-end`.
+- **A proper shell** — session and file tabs, a resizable Explorer, and a command palette (`Ctrl+Alt+K`) over
+  commands, tabs, sessions, projects, files and the model.
+- **Optional notifications** — be told when a run finishes while the tab is elsewhere (off until you opt in).
+
 ## Requirements
 
-- Node.js 20+ (developed on 24).
-- The `pi` CLI on your `PATH` and already authenticated (`pi --version`), or a path via `MORSE_PI_PATH`.
+- **Node.js 20+** (developed on 24).
+- The **`pi` CLI** on your `PATH` and already authenticated (`pi --version`), or a path via `MORSE_PI_PATH`.
   Morse reuses your existing pi configuration: models, credentials, tools and sessions under `~/.pi`.
 
 ## Commands
@@ -68,8 +104,8 @@ MORSE_UI_DIR           Override the served frontend directory
 
 ## Security
 
-`morse start` binds `127.0.0.1` by default. `--lan` exposes an **unauthenticated** chat UI to your network:
-only do it on a trusted network, or put a TLS reverse proxy with auth in front of it.
+`morse start` binds `127.0.0.1` by default. `--lan` exposes an **unauthenticated** chat UI to your network: only
+do it on a trusted network, or put a TLS reverse proxy with auth in front of it.
 
 ## How the single package is built
 
@@ -81,10 +117,9 @@ dist/cli.mjs      the `morse` lifecycle CLI
 dist/ui/          the built Angular frontend, served as static assets
 ```
 
-The `@morse/*` packages are private workspace libraries, so they cannot be installed from npm — bundling
-them into `server.mjs` is what makes a single publishable artifact possible. The NestJS runtime
-(`@nestjs/*`, `rxjs`, `ws`, `reflect-metadata`) stays external and is installed normally from
-`dependencies`.
+The `@morse/*` packages are private workspace libraries, so they cannot be installed from npm — bundling them
+into `server.mjs` is what makes a single publishable artifact possible. The NestJS runtime (`@nestjs/*`, `rxjs`,
+`ws`, `reflect-metadata`) stays external and is installed normally from `dependencies`.
 
 ## Uninstall
 
@@ -93,3 +128,11 @@ morse stop
 npm uninstall -g @supanadit/morse-web
 rm -rf ~/.morse      # state and logs
 ```
+
+## Links
+
+- [Repository and full README](https://github.com/supanadit/morse)
+- [VS Code extension](https://marketplace.visualstudio.com/items?itemName=supanadit.morse)
+- [Configuration](https://github.com/supanadit/morse/blob/master/docs/CONFIGURATION.md)
+
+[MIT](https://github.com/supanadit/morse/blob/master/LICENSE) © 2026 Supan Adit Pratama