@cordfuse/llmux 0.13.5 → 0.13.7

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 +18 -15
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -13,23 +13,26 @@ shared state. Drive any of them from a terminal (`llmux session attach`),
13
13
  a REST or WebSocket API, or a phone browser over Tailscale. Sessions
14
14
  survive daemon restarts; attach is raw-TTY (`Ctrl+]` to detach).
15
15
 
16
- ### `claude -p` is metered. llmux isn't.
16
+ ### Headless ≠ `claude -p`
17
17
 
18
- Every major agent CLI ships a one-shot mode `claude -p "prompt"` and
19
- the codex / gemini / qwen / amp equivalents. The catch: even when you
20
- authed via OAuth on a flat-rate subscription (Claude Pro/Max, ChatGPT
21
- Plus, Gemini Advanced, …), `-p`-style calls now route to the **metered
22
- API billing bucket** — real per-token dollars on top of your monthly
23
- subscription. Script a few hundred `-p` calls a day and the subscription
24
- stops mattering.
18
+ The obvious way to script Claude Code is `claude -p "prompt"` (and similar
19
+ non-interactive modes in codex, gemini, etc.). Each call spawns a fresh
20
+ short-lived child no shared conversation, no in-session OAuth, no
21
+ `/commands`, no persistent tool state, no MCP context.
25
22
 
26
23
  llmux drives the **interactive** agent process — the same TUI a human
27
- launches — over `tmux send-keys`. Interactive use stays on the
28
- subscription billing path: same OAuth, same flat rate, no per-token API
29
- surcharge. Spawn `claude` once, fire prompts at the same live agent
30
- forever from any client (CLI, REST, WebSocket, web). The agent runs
31
- unmodified and doesn't know it's being driven headlessly. Tool state and
32
- conversation persist across prompts; resume from any client.
24
+ launches — over `tmux send-keys`. Spawn `claude` once, fire prompts at the
25
+ same live agent forever from any client (CLI, REST, WebSocket, web).
26
+ The agent runs unmodified and doesn't know it's being driven headlessly.
27
+ Tool state persists across prompts. Conversations are resumable from any
28
+ client.
29
+
30
+ That same surface is the substrate higher-level orchestration sits on top
31
+ of — spec-driven development (SDD) pipelines, multi-agent chains,
32
+ scheduled jobs, evals harnessed against live agents — all just `llmux
33
+ session prompt <name> "..."` calls. No special agent build, no headless
34
+ SDK, no mode flag. If a human can drive the agent, llmux can drive it
35
+ the same way.
33
36
 
34
37
  ### OAuth from your phone, on a headless box
35
38
 
@@ -46,7 +49,7 @@ toolbar (Esc / Tab / Ctrl / arrows / shell chars), watch tool calls
46
49
  stream in. No "mobile app" — it's the same daemon serving a real
47
50
  terminal over a WebSocket.
48
51
 
49
- > **Status:** v0.13.5 — daemon + CLI client consolidated into one binary
52
+ > **Status:** v0.13.7 — daemon + CLI client consolidated into one binary
50
53
  > (`llmux`). Auth, tokens, mobile picker, conversation resume, Claude Code
51
54
  > history adapter shipped. See [CHANGELOG.md](./CHANGELOG.md).
52
55
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@cordfuse/llmux",
3
- "version": "0.13.5",
3
+ "version": "0.13.7",
4
4
  "description": "tmux-based AI agent dispatcher — REST/WS daemon + CLI client in one binary",
5
5
  "license": "MIT",
6
6
  "type": "module",