signalbird CLI
Signalbird from the terminal: one package, three jobs.
signalbird-cli is a single npm package. It runs Janet on your computer, writes events to Radio from your deploy scripts, and becomes the Server Monitoring agent when installed on a server. Its source is public and it never updates itself.
Why it exists
One tool per job does not scale
An agent for the server, a curl line for scripts, another program for your laptop. Each has its own key, its own updates and its own docs, and one of them is always a version behind.
What it does
6 capabilities, one screen.
Janet: fixes the error and opens a PR
Run signalbird login once: it connects the computer to your account, finds your project folder and installs the service. From then on Radio errors go to your own agent (Claude Code, Codex or Gemini CLI) and the fix comes back as a pull request.
Sender: write to Radio in one line
Deploy, cron or backup script: anywhere with a shell, signalbird send writes an event to a Radio channel. Who gets called lives in the panel, not in the script.
Server agent: eyes on the inside
sudo signalbird agent install turns it into a systemd service that reports CPU, memory, disk, services, databases and log lines to the Servers screen. It runs no commands, it only reads.
Sign in with your account
No keys to copy on your computer: signalbird login opens the browser and you click "Connect this computer". The computer is tied to your account and works across your teams.
Never updates itself
A tool that updates itself is a polite form of remote code execution. You install new versions yourself; the panel tells you when one is out.
Output you can read
Steps are numbered and errors say what to do next. Over SSH it prints the approval link instead of opening a browser, and NO_COLOR switches to plain text.
How it works
In 3 steps.
Install
npm i -g signalbird-cli (Node.js 20+).
Connect
signalbird login on your computer, sudo signalbird agent install on a server.
Forget it
Both run as services and start on their own when the machine boots.
Connect it in code
A few lines are enough.
This call really exists in the package. Every language and surface is on the developers page.
For developers# Your computer: Janet
npm i -g signalbird-cli
signalbird login
# Deploy script: one event to Radio
signalbird send info "v2.4.0 is live" --channel deploy --key sb_secret_live_xxxxxxxx
# Server: monitoring agent (Linux, systemd)
sudo npm i -g signalbird-cli
sudo signalbird agent install --token=sba_live_xxxxxxxxSpecifications
Does it really do that?
- Package
- signalbird-cli (npm) · command: signalbird
- Requirements
- Node.js 20+
- Service
- Janet: macOS launchd, Linux systemd · Server agent: Linux systemd
- Source
- github.com/Pariette-Inc/signalbird.cli · MIT
- Price
- Free; follows the plan of the module you use (Radio, Server Monitoring)
Questions
Things you might wonder.
How is it different from the signalbird package?
signalbird is the SDK you install inside your application. signalbird-cli is a tool that runs in the terminal. Both talk to the same API: one from your code, the other from the shell.
Does it work on Windows?
The sender (signalbird send) works anywhere Node.js runs. The Janet service installs on macOS and Linux, the server agent on Linux with systemd.
Where can I see every command?
On the documentation page, each command with its explanation. signalbird help prints the same list in the terminal.
Works well with