Pipeline Events (##>)
Lines starting with double-hash-greater-than bypass the shell and fly straight to NATS.
What you'll see
- Launch
ryshand split a worker pane withCtrl+P n. - In the worker's rysh mode, run
##pane listen orchestratorto forward the source pane's shared output. Tabto the orchestrator pane and double-Escape into rysh mode.- Emit
##>event:print:Build started at 10:30 AM-- it bypasses the PTY and publishes to the pane's NATS output topic. - Emit
##>event:print:Compiling module auth; the payload reaches listeners without an alias prefix.
Commands shown
rysh
n
##pane listen orchestrator
##>event:print:Build started at 10:30 AM
##>event:print:Compiling module auth
Keys used
EnterCtrl+pEscapeTab
Transcript
0:00Lines starting with double-hash-greater-than bypass the shell and fly straight to NATS.
0:03Start rysh and split a second pane. We'll have this worker listen to the first pane's shared output.
0:09In rysh mode, ##pane listen forwards another pane's shared output here. Event payloads arrive without an alias prefix.
0:18Hop to the orchestrator pane and switch it to rysh mode so we can emit a pipeline event.
0:34Send as many as you like. Each event is a clean line in the shared output buffer, visible to every listening pane.
Key takeaway
##> lines are pipeline events that skip the PTY and publish clean lines to NATS, visible to every listening pane.