Openclawssy is an alternative to OpenClaw for the sensible, thinking gentleman 🎩🚬.
A strategically important Ussyverse protocol for disciplined operators: single-binary runtime, predictable control planes, strict capability gates, and artifact-first execution designed for traceability over vibes.
Openclawssy exists as an OpenClaw alternative for operators who want command discipline, auditable behavior, and explicit blast-radius control from day one.
Predictable architecture > agent chaos. The protocol emphasizes deterministic control-plane behavior, bounded execution, and artifacts you can inspect after every run.
Built-in command set for init, setup, ask, run, serve, cron, and doctor so operators can move from local prep to production-like drills without changing tools.
Supports OpenAI, OpenRouter, Requesty, ZAI, and any generic OpenAI-compatible endpoint for flexible model routing under one protocol contract.
Shell execution is explicitly gated by capability policy and sandbox constraints before commands are allowed to run.
Trigger and monitor workloads from HTTP endpoints or Discord workflows depending on where your operators already live.
Dashboard for status, config, and secret ingestion; HTTP on loopback by default and HTTPS when TLS is enabled.
Each run emits artifact bundles and trace metadata so handoffs and postmortems stay deterministic.
Capabilities are closed unless explicitly granted. Policy is the gate, not a suggestion.
Default network posture favors loopback binding and tokened endpoints to reduce accidental exposure.
Control-plane artifacts are handled as protected assets so operational mutation requires explicit intent.
Encrypted secret values are accepted for runtime use and never returned in API or UI payloads.
# Install latest build
$ go install github.com/mojomast/openclawssy@latest
# Setup local control plane
$ openclawssy setup
# Verify environment + capabilities
$ openclawssy doctor -v
# Serve API/dashboard with token auth
$ openclawssy serve --token "change-me-now"
# Run a tool call using the harness runtime
$ openclawssy run --agent default --message '/tool time.now 'PROTOTYPE IN DEVELOPMENT. This protocol is still volatile and interfaces may change without notice.
Do not use in production yet. Not production-ready; you probably shouldn't use this (or OpenClaw) in production yet.
Treat Openclawssy as an experimental harness for lab environments, rehearsals, and operator training drills only.
Protocol page and listings are wired. Grab the binary, run drills, and report findings.
Need the broader map? Return to the Ussyverse homepage.