kino-cli 0.1.7 → 0.1.8

package/README.md

@@ -9,11 +9,16 @@ leaves your machine.
 
 [![The kino console: choosing a model, asking a question, approving a fix](https://raw.githubusercontent.com/DogukanGun/homebrew-tap/main/media/kino-console.gif)](https://github.com/DogukanGun/homebrew-tap/releases/tag/demo-videos)
 
+**Modes** (2 min): Shift+Tab through the modes, a question in research mode, then plan mode: the plan, the
+go-ahead, the fix approved and tested.
+
+[![kino's modes: research, then plan, go ahead and fix](https://raw.githubusercontent.com/DogukanGun/homebrew-tap/main/media/kino-modes.gif)](https://github.com/DogukanGun/homebrew-tap/releases/tag/demo-videos)
+
 **kino-code on its own** (44 s): `kino code -p` fixes a real bug and the tests pass.
 
 [![kino-code fixing a bug from the command line](https://raw.githubusercontent.com/DogukanGun/homebrew-tap/main/media/kino-demo.gif)](https://github.com/DogukanGun/homebrew-tap/releases/tag/demo-videos)
 
-Both are unedited recordings on a Claude Code login. The MP4 files are on [the release page](https://github.com/DogukanGun/homebrew-tap/releases/tag/demo-videos).
+All three are unedited recordings on a Claude Code login. The MP4 files are on [the release page](https://github.com/DogukanGun/homebrew-tap/releases/tag/demo-videos).
 
 This guide covers everything, start to finish:
 
@@ -146,6 +151,18 @@ Apply this edit? [y/N/a]
 
 It then runs the tests and reports what it changed and how it checked, ending with `✓ done`.
 
+**Keep typing while kino works.** The input stays open during a run, with `✻ Working… (12s · esc to interrupt)`
+above it. Each line you send while it works is queued under the input (`⎿ queued: …`) and runs after the
+current one, in order. **↑** on an empty input takes the last queued line back to edit. Approvals and
+questions are asked in the same input: the question replaces `❯`, and what you had half-typed comes back
+after you answer. If you interrupt a run (Esc or Ctrl-C), the queued lines come back to the input instead of
+running.
+
+**Clicking in the input** moves the cursor there. For that, kino turns on the terminal's mouse reporting, which
+also takes the scroll wheel: while the console is open, scroll back with the terminal's scrollbar, and select
+text with Option (macOS) or Shift held. `/mouse off` gives the wheel back to the terminal (saved for every
+folder); `/mouse on` turns clicking on again.
+
 **It remembers the conversation.** Each new message knows the earlier ones, how they ended and which files they
 changed, so "now add a test for it" works. `/clear` starts over. `kino -c` reopens the last conversation, and
 continues a run that was waiting or had failed.
@@ -159,13 +176,13 @@ Ctrl-J, or a `\` at the end of a line; pasting several lines also works.
 ──────────────────────────────────────────────────────────────── shop ───
 ❯ fix the cart total
 ─────────────────────────────────────────────────────────────────────────
-  ⏵⏵ auto mode on (shift+tab to cycle)    claude-code:claude-sonnet-5-5 · 1.2k in / 340 out · kino 0.1.7
+  ⏵⏵ auto mode on (shift+tab to cycle)    claude-code:claude-sonnet-5-5 · 1.2k in / 340 out · kino 0.1.8
 ```
 
 - Above the input, at the right: the label, which is the folder's name unless you set one with `/rename <name>`.
 - Below it, at the left: the mode. **Shift+Tab** cycles through the modes (see [4](#4-approvals-and-modes)).
 - At the right: the model, the tokens used so far, and kino's version. When npm has a newer kino, it says
-  `kino 0.1.8 available · npm i -g kino-cli@latest` instead. kino checks for that at most once a day, in the
+  `kino 0.1.9 available · npm i -g kino-cli@latest` instead. kino checks for that at most once a day, in the
   background; `KINO_NO_UPDATE_CHECK=1` turns the check off.
 
 **Stop and leave:**
@@ -197,8 +214,8 @@ them, `read-only` included.
 | `read-only` | the task, without changing anything | refused | refused |
 
 **Plan mode** is for changes you want to agree on first. kino reads the code and answers with a plan: the goal,
-each file to change and how, new tests, the commands that will verify it, risks and open questions. Then it
-asks:
+each file to change and how, new tests, the commands that will verify it, risks and open questions. The plan
+is drawn as formatted text in a box titled **Plan** (research reports get a **Report** box). Then it asks:
 
 ```
 ╭─ Plan ready ────────────────────────────────╮
@@ -232,6 +249,7 @@ Some things are never done, whatever you answer: see [Safety](#12-safety).
 | `/help` | list the commands |
 | `/model [provider:model]` | open the model picker, or switch to that model |
 | `/mode [ask\|auto-edit\|plan\|research\|auto\|read-only]` | show or set the mode (Shift+Tab cycles) |
+| `/mouse [on\|off]` | click in the input to move the cursor (on by default; off gives the wheel back to scrolling) |
 | `/rename [name]` | the label above the prompt; with no name, back to the folder's name |
 | `/permissions [revoke <n\|all>]` | what you allowed this session; take it back |
 | `/diff` | `git diff` of what changed |
@@ -250,8 +268,8 @@ Some things are never done, whatever you answer: see [Safety](#12-safety).
 | Alt-Enter, Ctrl-J, `\` at line end | new line |
 | Tab | complete a command, a process name, or a path after `@` |
 | Shift+Tab | the next mode |
-| ↑ / ↓ | earlier messages |
-| Esc | stop the current run |
+| ↑ / ↓ | earlier messages; ↑ on an empty input while lines are queued takes the last one back to edit |
+| Esc | stop the current run (queued lines come back to the input) |
 | Ctrl-C | stop the run; clear the line; twice on an empty line to leave |
 | Ctrl-D | leave |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kino-cli",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "kino: an agent that learns your codebase and tools, then works as one of the team's developers. Includes kino-code, a coding agent on any model.",
   "bin": {
     "kino": "bin/kino.js"