CLI
A sigx CLI plugin for observing actors: hosts, latency, errors and cluster topology, from a terminal.
Installation
pnpm add -D @sigx/actors-clisigx actors # the dashboard
sigx actors top --url http://host:7311 # …against a running host
sigx actors stats --json | jq '.cluster.totals' # a snapshot, for piping
sigx actors health --url http://host:7311 # exit code by readiness
Requires @sigx/cli ≥ 0.9 and @sigx/terminal ≥ 0.11. On older versions the plugin's version
guard warns and the dashboard never learns its pane size.
Two ways to reach a host
Embedded (the default) loads your project's actor app module in-process and reads it directly. Zero config, no secret, and it sees strictly more than the wire can — full latency histograms, the whole activation list, the cluster placement itself.
It also starts a host. That host is real: it joins membership, claims actors and ticks reminders. Fine pointed at a dev app, wrong pointed at production.
HTTP (--url) polls a running host's ops() endpoint. It
loads no user code and holds no host, so it is the mode for anything you did not just start
yourself. --url wins over a local module.
The same five tabs, in a browser
The dashboard's five tabs — Overview, Hosts, Actors, Cluster, Health — draw the data layer in
@sigx/actors-monitor, and
@sigx/actors-dashboard draws the same layer in
a browser as embeddable sigx components. One data layer, two renderers: the numbers agree
because neither derives them.
Why the commands might not be there
The sigx binary discovers plugins from the dependencies of the project you run it in. It
reads ./package.json, looks for a sigx-cli field in each dependency's manifest, and calls
the plugin's detect(cwd). Two things must be true in that directory:
@sigx/actors-cliis in itsdependenciesordevDependencies;- it depends on
@sigx/actors— that is whatdetectlooks for.
$ sigx actors top
error: Unknown command 'actors'
That is not a broken install. It is the CLI correctly declining to offer actor commands in a
project that has no actors — sigx --help lists what it did find. Run it from the package
that owns the host, or in a monorepo:
pnpm --filter my-app exec sigx actors top
Next steps
- Installation — flags, exit codes and the app-module convention.
- API reference — the
/sourcesubpath andembeddedSource. @sigx/actors-dashboard— the web rendering.- The ops endpoint — what HTTP mode reads.
