muuuuse 5.0.0 → 5.0.1

package/README.md

@@ -1,56 +1,44 @@
 # 🔌Muuuuse
 
-`🔌Muuuuse` is a tiny terminal relay.
+`🔌Muuuuse` is a tiny terminal relay with flexible routing.
 
 It does one job:
-- arm terminal one with `muuuuse 1`
-- arm terminal two with `muuuuse 2`
-- have seat 1 generate a session key and seat 2 sign it
-- additional isolated pairs work the same way: `3/4`, `5/6`, `7/8`, ...
-- choose per-seat relay mode with `flow on` or `flow off`
+- arm any number of terminals with `muuuuse <N>`
+- each seat can route to any other seats with individual flow modes
 - watch Codex, Claude, or Gemini for local assistant output
-- inject that output into the other armed terminal
+- relay that output to configured targets with per-target flow control
 - keep looping until you stop it
 
 The whole surface is:
 
 ```bash
 muuuuse 1
-muuuuse 1 flow on
-muuuuse 1 flow off
-muuuuse 1 flow off continue 5
 muuuuse 2
-muuuuse 2 flow off
-muuuuse 2 flow on continue 3
-muuuuse 3
-muuuuse 3 flow on
-muuuuse 4
-muuuuse 4 flow off continue 1
+muuuuse 3 link 1 flow on 2 flow off
+muuuuse 4 link 3 flow on
 muuuuse status
 muuuuse stop
 ```
 
-## Flow
+## Routing
 
-Terminal 1:
+Any seat can route to any targets. Syntax:
 
 ```bash
-muuuuse 1 flow on
+muuuuse <seat> link <target1> flow <on|off> [<target2> flow <on|off> ...]
 ```
 
-Terminal 2:
+Example: Seat 3 routes to seat 1 with full output (flow on) and seat 4 with final answers only (flow off):
 
 ```bash
-muuuuse 2 flow off
+muuuuse 3 link 1 flow on 4 flow off
 ```
 
-Now both shells are armed. `muuuuse 1` generates the session key, `muuuuse 2` signs it, and only that signed pair relays. Every odd/even adjacent pair works the same way in parallel: `3/4`, `5/6`, `7/8`, and so on. Use those shells normally.
+Each seat defines its own routing targets. When that seat gets an answer from Claude/Codex/Gemini, it sends to all configured targets with their respective flow modes.
 
-`flow on` means that seat relays commentary and final answers. `flow off` means that seat relays and accepts final answers only. Mixed calibration is allowed per seat.
+`flow on` means relay both thinking/commentary and final answers. `flow off` means relay final answers only.
 
-`continue <seat>` forwards that seat's relayed output into another armed seat without changing the signed odd/even pair law. This lets you build local loops like `1 -> 2 -> 3 -> 4 -> 1` while every adjacent pair still keeps its own session keypair.
-
-If you want Codex in one and Gemini in the other, start them inside the armed shells:
+If you want Codex in one and Gemini in another, start them inside the armed shells:
 
 ```bash
 codex
@@ -60,7 +48,7 @@ codex
 gemini
 ```
 
-`🔌Muuuuse` tails the local session logs for supported CLIs, relays according to each seat's flow mode, types that output into the other seat, and then sends Enter as a separate keystroke.
+`🔌Muuuuse` tails the local session logs for supported CLIs, relays according to each target's flow mode, types that output into the target seat, and then sends Enter as a separate keystroke.
 
 Check the live state from any terminal:
 
@@ -77,8 +65,9 @@ muuuuse stop
 ## Notes
 
 - state lives under `~/.muuuuse`
-- only the signed armed pair can exchange relay events
-- `continue <seat>` is a separate local forwarding lane and can target any armed seat number
+- each seat defines its own routing targets independently
+- any seat can route to any other seat number
+- flow modes are per-target (not per-seat)
 - supported relay detection is built for Codex, Claude, and Gemini
 
 ## Install

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "muuuuse",
-  "version": "5.0.0",
+  "version": "5.0.1",
   "description": "🔌Muuuuse arms terminals with flexible routing to any targets - pure message relay graph.",
   "type": "commonjs",
   "bin": {