kino-cli 0.1.5 → 0.1.8

package/README.md

@@ -5,6 +5,21 @@ answers questions about it, writes and fixes code, and runs the team's documente
 pull request or working through review comments. It runs on the model you choose, and it asks before anything
 leaves your machine.
 
+**The console** (66 s): first start, a question, a fix approved as a diff, the tests run.
+
+[![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)
+
+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:
 
 1. [Install](#1-install)
@@ -136,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.
@@ -143,7 +170,20 @@ continues a run that was waiting or had failed.
 **Attach files** with `@`: `explain @src/api/routes.py` (Tab completes paths). **Several lines:** Alt-Enter,
 Ctrl-J, or a `\` at the end of a line; pasting several lines also works.
 
-**The bar at the bottom** shows the model, the approval mode, and the tokens and requests used so far.
+**The prompt area:**
+
+```
+──────────────────────────────────────────────────────────────── 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.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.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:**
 - Esc or Ctrl-C while kino works stops it. The run is kept, and `/resume` continues it.
@@ -161,13 +201,44 @@ Ctrl-J, or a `\` at the end of a line; pasting several lines also works.
   `git push`), one API operation, or, for edits, every edit. `/permissions` shows what you allowed, and
   `/permissions revoke <n|all>` takes it back. Nothing is remembered after you leave.
 
-Modes, changed with `/mode`:
+**Modes.** Shift+Tab cycles `ask → auto-edit → plan → research → auto → ask`; `/mode <name>` sets any of
+them, `read-only` included.
 
-| Mode | File changes | Outward actions |
-|---|---|---|
-| `ask` (default) | shown and asked | asked |
-| `auto-edit` | shown and applied | asked |
-| `read-only` | refused | refused |
+| Mode | What kino does | File changes | Outward actions |
+|---|---|---|---|
+| `ask` (default) | the task | shown and asked | asked |
+| `auto-edit` | the task | shown and applied | asked |
+| `plan` | investigates and answers with a plan, then asks whether to go ahead | none | none |
+| `research` | investigates and answers with a report, with `file:line` references | none | none |
+| `auto` | the task, without stopping to ask | shown and applied | shown and allowed |
+| `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. The plan
+is drawn as formatted text in a box titled **Plan** (research reports get a **Report** box). Then it asks:
+
+```
+╭─ Plan ready ────────────────────────────────╮
+│ Go ahead with this plan?                    │
+│   1. Yes, and ask before each edit          │
+│   2. Yes, and apply edits without asking    │
+│   3. Yes, in auto mode (outward actions too)│
+│   4. No, keep planning                      │
+╰─────────────────────────────────────────────╯
+```
+
+With a yes, kino switches to that mode and carries the plan out. With no, you stay in plan mode: say what to
+change in the plan.
+
+**Research mode** answers questions about the code without changing anything: the direct answer first, the
+findings with `file:line` references, how the parts connect, what is uncertain, and what it did not check.
+
+**Auto mode** runs without stopping for approvals. Every edit and every outward action the policy allows (push,
+pull requests, ticket and API writes) is shown as it happens and goes ahead. Use it when you trust the task and
+the setup. What auto mode does not change:
+- the hard guards still refuse force-push, merges, `reset --hard` and the rest (see [Safety](#12-safety));
+- your config's deny rules still refuse their calls;
+- questions only you can answer are still asked.
 
 Some things are never done, whatever you answer: see [Safety](#12-safety).
 
@@ -177,7 +248,9 @@ 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\|read-only]` | show or set how changes are approved |
+| `/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 |
 | `/cost` | requests, tool calls and tokens used this session |
@@ -194,8 +267,9 @@ Some things are never done, whatever you answer: see [Safety](#12-safety).
 | Enter | send |
 | Alt-Enter, Ctrl-J, `\` at line end | new line |
 | Tab | complete a command, a process name, or a path after `@` |
-| ↑ / ↓ | earlier messages |
-| Esc | stop the current run |
+| Shift+Tab | the next mode |
+| ↑ / ↓ | 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 |
 
@@ -385,7 +459,8 @@ API calls stay with kino's own steps, behind its confirmations.
 ## 12. Safety
 
 - **Outward actions are confirmed one call at a time**: push, pull requests, comments, ticket and API writes. With
-  nobody at the terminal they are refused, or the run waits until someone answers.
+  nobody at the terminal they are refused, or the run waits until someone answers. The exception is auto mode,
+  which you switch on yourself: there they are shown and go ahead.
 - **Never done, whatever you answer**: force-push, `git reset --hard`, `git stash`, merging pull requests,
   admin overrides, co-author trailers.
 - **Files** can only change inside the folder kino works in.
@@ -426,6 +501,7 @@ knowledge:
 | `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `GEMINI_API_KEY` | provider keys |
 | `OLLAMA_HOST` | where Ollama runs (default `http://localhost:11434`) |
 | `KINO_UV`, `KINO_NO_UV_INSTALL` | which uv the npm package uses; don't install uv |
+| `KINO_NO_UPDATE_CHECK` | `1`: never look up newer kino versions |
 
 All commands: `kino --help`, and `kino <command> --help` for each one.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kino-cli",
-  "version": "0.1.5",
+  "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"