leglas 0.4.1 → 0.6.0

package/README.md

@@ -15,7 +15,7 @@
 </p>
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/pr-assets/rail-single.jpg" width="900" alt="The Leglas interface: a rail of three design directions on the left, and the selected one running as the real app filling the rest of the window" />
+  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/main/.github/assets/screenshots/rail-single.jpg" width="900" alt="The Leglas interface: a rail of three design directions on the left, and the selected one running as the real app filling the rest of the window" />
 </p>
 
 <p align="center"><i>Every direction in the rail, the selected one running as your actual app. Arrow keys flip between them.</i></p>
@@ -46,7 +46,7 @@ and sessions that clean up after themselves.
 ## What you can do with Leglas
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/pr-assets/compare-artboards.jpg" width="900" alt="The Leglas interface: a rail of three design directions on the left, and two of them running side by side as the real app, each labelled with its name." />
+  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/main/.github/assets/screenshots/compare-artboards.jpg" width="900" alt="The Leglas interface: a rail of three design directions on the left, and two of them running side by side as the real app, each labelled with its name." />
 </p>
 
 <p align="center"><i>Two directions for the same page, running side by side as the actual app.</i></p>
@@ -66,12 +66,15 @@ and sessions that clean up after themselves.
   precise request for your agent, file path included. The composer
   carries its own agent picker, the way every chat you already use
   carries a model picker: the CLIs found on your machine (Claude Code,
-  Codex, Cursor) are one click away next to the send button, each asked
-  for its login status so a signed-out CLI says so before a run instead
-  of failing one. Not on that list? Type the command that runs your
-  agent once, in the same menu, and Leglas hands it each request; or
-  connect an agent Leglas can't spawn (an IDE panel, an MCP host) with
-  the copy-paste MCP wiring behind "Connect another agent". Each run
+  Codex, Cursor) are one click away next to the send button. Leglas checks
+  your shell path and the conventional per-user install locations, then asks
+  each CLI for its login status so a signed-out agent says so before a run
+  instead of failing one. Claude Code and Codex can optionally override effort
+  for this project, remembered separately for each agent; `Agent default`
+  leaves the CLI's own setting untouched. To
+  work from an IDE panel or chat host, choose
+  "Connect agent via MCP" for the exact setup and a live confirmation
+  once the agent uses a Leglas tool. Each run
   reports in a card above the field: who is working, what file they
   are touching, how long it has been, a stop button while it runs and
   retry when it fails. Your agent, your subscription, no keys.
@@ -177,13 +180,26 @@ directly above the field. Your agent drains the queue with `npx leglas requests
 it with `--clear`. Leglas runs no model of its own; your agent already
 knows your conventions and your taste.
 
+Most of what you would type into that field is the part describing where
+the problem is, so you can point at it instead. Press `A` and the preview
+becomes a picker: hovering outlines the element under the pointer,
+clicking drops a numbered pin that takes a note, and dragging marks an
+area and names every element inside it. The page still scrolls, so the
+thing three screens down is as easy to mark as the headline. Annotations
+are a request on their own, so the field can stay empty; leave three and
+send once. Each one carries the element's own words, its tag and classes,
+a path and the box it filled, and the request tells your agent which of
+those to trust first, because the design moves under them by design. One
+whose element has since gone turns amber rather than pointing confidently
+at the wrong thing.
+
 The line under the field is the whole status: whether anything is
 listening, what you have queued, and when it has been picked up.
 
 <p align="center">
-  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/pr-assets/field-idle.png" width="290" alt="The change field reading: Enter queues it for npx leglas requests" />
-  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/pr-assets/field-queued.png" width="290" alt="The change field reading: one change queued for your agent" />
-  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/pr-assets/field-pickedup.png" width="290" alt="The change field reading: Your agent is on it" />
+  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/main/.github/assets/screenshots/field-idle.png" width="290" alt="The change field reading: Enter queues it for npx leglas requests" />
+  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/main/.github/assets/screenshots/field-queued.png" width="290" alt="The change field reading: one change queued for your agent" />
+  <img src="https://raw.githubusercontent.com/FredAmartey/leglas/main/.github/assets/screenshots/field-pickedup.png" width="290" alt="The change field reading: Your agent is on it" />
 </p>
 
 <p align="center"><i>Nothing waiting, then a request queued, then an agent that has taken it.</i></p>
@@ -194,6 +210,13 @@ wrong. `npx leglas watch` in another terminal is the same loop with the
 agent's own output in view, and it needs no flag once an agent has been
 picked in the interface.
 
+To use a CLI that is not in the picker, keep the custom command explicit
+in the terminal:
+
+```sh
+npx leglas watch --run "my-agent {prompt}"
+```
+
 ### MCP server
 
 For agent hosts that cannot run shell commands, `leglas-mcp` exposes the
@@ -308,8 +331,9 @@ drawn at and the scale it is shown at. If you want the narrow rendering,
 that is what the tools popover's "Scale each side to fit" switch is for.
 
 Arrows move between directions, `1` to `9` jump straight to one, `R` asks
-for a change to the one you are on, `Cmd K` (`Ctrl K` elsewhere) searches
-and `B` collapses the rail. Press `?` for the whole keymap.
+for a change to the one you are on, `A` annotates the design itself,
+`Cmd K` (`Ctrl K` elsewhere) searches and `B` collapses the rail. Press `?`
+for the whole keymap.
 
 A small tools widget floats over the stage and can be dragged to any
 corner, because a floating control has a habit of sitting exactly where
@@ -346,6 +370,7 @@ leglas keep <title>        Keep a winner and end the exploration
   --count <n>          (explore) How many directions, default 3
   --based-on <title>     (explore) Variants of an existing direction instead of new ones
   --based-on <title>     (add) The direction this preview is a variant of; groups the family
+  --asked-for <text>     (add) The change that was asked for, in the words that were typed
   --change <path>      (classify) A file the direction creates or wires up
   --rewrite <path>     (classify) An existing file whose behaviour must change
   --note <text>        (add) Second line under the title

package/dist/args.d.ts

@@ -17,6 +17,8 @@ export type AddPreview = {
     file: string | undefined;
     /** The direction this preview is a variant of; the rail groups them. */
     basedOn: string | undefined;
+    /** The change that was asked for, in the words that were typed. */
+    askedFor: string | undefined;
 };
 export type ClassifyChange = {
     path: string;