Pipelit ecosystem CLI
Supported platforms: Linux (native), macOS (via Docker), Windows (via WSL2).
cargo install plitThis installs two binaries: plit (the CLI) and plit-gw (the gateway server).
# 1. Interactive setup: configure Pipelit, your LLM provider, and credentials
plit init
# 2. Start the gateway, Pipelit, and workers
plit startThat's it. You're running.
Interactive wizard. Walks you through:
- Connecting to your Pipelit instance
- Configuring an LLM provider
- Creating initial credentials
Run this once before anything else.
Start and stop the full stack: gateway, Pipelit, and background workers. Managed via honcho.
plit start
plit stopInteractive REPL for chatting with your configured agent.
plit chat my_credential --chat-id session-1One-shot message. Pipe-friendly.
plit send my_credential --chat-id session-1 --text "Hello"
echo "summarize this" | plit send my_credential --chat-id session-1Output is plain text on a TTY, JSON when piped. Pass --json to force JSON anywhere.
Stream incoming messages as JSONL over WebSocket. Useful for scripting and log tailing.
plit listen my_credential --chat-id session-1
plit listen my_credential --chat-id session-1 | jq .Manage gateway credentials.
plit credentials list
plit credentials create --name my-bot
plit credentials activate <id>
plit credentials deactivate <id>Check gateway and backend health.
plit healthRemove configuration and stop running services.
plit uninstall| Variable | Description |
|---|---|
GATEWAY_URL |
Gateway base URL (e.g. http://localhost:8080) |
GATEWAY_TOKEN |
Token for standard API access |
GATEWAY_ADMIN_TOKEN |
Token for admin operations (credentials, health) |
These override values from the config file written by plit init.
plit adapts its output to context:
- TTY — human-readable, formatted
- Piped — JSON automatically
--json— force JSON regardless of context
plit is a thin CLI wrapper around plit-gw. Installing plit gives you both the command-line interface and the gateway server in a single cargo install. The gateway handles protocol adapters, message routing, and backend connections. The CLI handles setup, process management, and user-facing interaction.
For gateway configuration, adapter setup, and backend protocol details, see the plit-gw repository.
Apache 2.0. See LICENSE.