cosmo doppler

CLI · 04

A Doppler is any process that subscribes to the channel as a passive, read-only consumer. cosmo doppler is the built-in one - it tails every envelope, applies filters, and renders to stdout (or the Prism browser UI with --prism, documented below). Pass --json to emit one JSON object per line for piping to jq. Give it a --url and a --namespace (the same shape as cosmo synapse); the legacy --synapse=url/namespace form is still accepted.

$ cosmo doppler --help

Attach a read-only Doppler to a Synapse namespace and stream Signals.

Usage
  cosmo doppler --url <url> --namespace <ns> [filters] [output]

Options
  --url <url>             Synapse URL, e.g. cosmo://127.0.0.1:7070
  --namespace, -n <ns>   Namespace to observe.       Default: dev
  --synapse <url/ns>      Legacy combined form (path-encoded namespace).
  --type <TYPE>            Filter to specific signal types. Repeatable.
  --trace <trc_…>          Filter to a single trace_id.
  --neuron <id>            Filter to a single neuron id.
  --json                   Output one JSON object per line (CLI mode).
  --payload                Show a payload preview alongside each signal.
  --prism                  Launch the Prism browser visualization instead of stdout.
  --port <n>              Local port for the Prism server. Default: 7071

Examples

$ cosmo doppler --url=cosmo://127.0.0.1:7070 -n quickstart
  REGISTER      neuron=hello-neuron
  TASK          trace=trc_…  neuron=hello-neuron
  AGENT_OUTPUT  trace=trc_…  neuron=hello-neuron

$ cosmo doppler --url=cosmo://127.0.0.1:7070 -n dev --type=AGENT_OUTPUT --type=ERROR
$ cosmo doppler --url=cosmo://127.0.0.1:7070 -n dev --trace=trc_01JV…
$ cosmo doppler --url=cosmo://127.0.0.1:7070 -n dev --json | jq 'select(.type=="ERROR")'

Have a feature in mind?

The protocol, SDKs, and CLI are still pre-1.0. If something here is missing, ambiguous, or wrong - open an issue and propose a change. Every breaking change is debated in DECISIONS.md first.

Run the quickstart →Re-read the envelope spec