leglas-mcp 0.5.0 → 0.6.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +16 -6
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -66,12 +66,15 @@ and sessions that clean up after themselves.
66
66
  precise request for your agent, file path included. The composer
67
67
  carries its own agent picker, the way every chat you already use
68
68
  carries a model picker: the CLIs found on your machine (Claude Code,
69
- Codex, Cursor) are one click away next to the send button, each asked
70
- for its login status so a signed-out CLI says so before a run instead
71
- of failing one. Not on that list? Type the command that runs your
72
- agent once, in the same menu, and Leglas hands it each request; or
73
- connect an agent Leglas can't spawn (an IDE panel, an MCP host) with
74
- the copy-paste MCP wiring behind "Connect another agent". Each run
69
+ Codex, Cursor) are one click away next to the send button. Leglas checks
70
+ your shell path and the conventional per-user install locations, then asks
71
+ each CLI for its login status so a signed-out agent says so before a run
72
+ instead of failing one. Claude Code and Codex can optionally override effort
73
+ for this project, remembered separately for each agent; `Agent default`
74
+ leaves the CLI's own setting untouched. To
75
+ work from an IDE panel or chat host, choose
76
+ "Connect agent via MCP" for the exact setup and a live confirmation
77
+ once the agent uses a Leglas tool. Each run
75
78
  reports in a card above the field: who is working, what file they
76
79
  are touching, how long it has been, a stop button while it runs and
77
80
  retry when it fails. Your agent, your subscription, no keys.
@@ -207,6 +210,13 @@ wrong. `npx leglas watch` in another terminal is the same loop with the
207
210
  agent's own output in view, and it needs no flag once an agent has been
208
211
  picked in the interface.
209
212
 
213
+ To use a CLI that is not in the picker, keep the custom command explicit
214
+ in the terminal:
215
+
216
+ ```sh
217
+ npx leglas watch --run "my-agent {prompt}"
218
+ ```
219
+
210
220
  ### MCP server
211
221
 
212
222
  For agent hosts that cannot run shell commands, `leglas-mcp` exposes the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "leglas-mcp",
3
- "version": "0.5.0",
3
+ "version": "0.6.0",
4
4
  "description": "Stdio MCP server exposing Leglas to agent hosts that cannot run a shell.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -15,7 +15,7 @@
15
15
  "dependencies": {
16
16
  "@modelcontextprotocol/sdk": "^1.30.0",
17
17
  "zod": "^3.25.76",
18
- "leglas": "^0.5.0"
18
+ "leglas": "^0.6.0"
19
19
  },
20
20
  "license": "MIT",
21
21
  "repository": {