COMMAND LINE INTERFACE
The Waxell CLI provides a unified interface for observing and operating agent systems.
It allows developers to view execution state, inspect telemetry, manage agents, apply governance actions, and run tests without switching between dashboards or tooling layers.
This makes the command line a first-class control surface rather than a thin wrapper around web interfaces.
As agent usage grows, development workflows become fragmented.
Engineers are forced to move between terminals, dashboards, logs, and internal tools to understand system behavior and make changes. This slows iteration and increases the risk of operating on stale or incomplete information.
The CLI exists to collapse those surfaces into a single, authoritative interface aligned with the runtime itself.
A live view into the runtime
The CLI exposes real-time execution data directly from the Waxell runtime.
Developers can observe running agents, inspect recent executions, view telemetry, and trace decision paths without leaving their development environment. This makes runtime behavior visible where development work actually happens.
Operational insight becomes continuous rather than something accessed only after failures occur.
The CLI is not an ungoverned control channel.
All actions taken through the CLI are subject to the same policies, budgets, and approval rules that apply to every other interface. Kill-switches, execution halts, and configuration changes flow through the governance plane.
This ensures that operational convenience never becomes an implicit backdoor around system controls.
Integrated testing and iteration
The CLI provides a direct interface to Waxell’s testing framework.
Developers can run local or remote test executions, inspect structured results, replay scenarios, and compare behavior across versions without switching tools. Test outcomes are recorded as first-class telemetry.
This makes experimentation, debugging, and validation part of a single continuous workflow rather than separate phases.
The CLI is designed for developers who are building systems that must remain operable in production.
It makes live state visible, surfaces actionable controls, and enforces governance constraints without requiring direct access to internal dashboards or privileged infrastructure.
This keeps development velocity high while preserving the operational integrity of production systems.
POLICY A
POLICY B
POLICY C
POLICY D
Designed to scale
