Waxell

Product

Compare

START FREE

Waxell

COMMAND LINE INTERFACE

Operating agent systems from a single control surface

Waxell CLI is a command line interface for observing and operating AI agent systems in production — it provides real-time access to execution state, telemetry, governance controls, and the testing framework from a single terminal session, without switching to dashboards or external tooling.

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.

start free

Free during beta.

Why do AI agent development workflows break at scale?

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.

How does the Waxell CLI handle governance?

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.

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.

Composing agents from the command line

The CLI integrates directly with the Agent Composer.

Developers can create new agents from intent, adapt experimental logic into Waxell’s runtime model, and formalize prototypes into deployable systems using a consistent command surface.

This enables agentic development workflows where agents are built, tested, and deployed through a single governed interface.

Composing agents from the command line

The CLI integrates directly with the Agent Composer.

Developers can create new agents from intent, adapt experimental logic into Waxell's runtime model, and formalize prototypes into deployable systems using a consistent command surface.

Agents can be built, tested, and deployed through a single governed interface — intent to production without switching tools.

The problem isn't that the information isn't available — it's that it's in four different places and one of them is always stale. The Waxell CLI puts execution state, telemetry, governance controls, and testing in a single interface that's live against the runtime. What you see is the current state of the system.

START FREE

Composing agents from the command line

The CLI integrates directly with the Agent Composer.

Developers can create new agents from intent, adapt experimental logic into Waxell’s runtime model, and formalize prototypes into deployable systems using a consistent command surface.

This enables agentic development workflows where agents are built, tested, and deployed through a single governed interface.

What does a Waxell CLI session look like?

An execution fails in production. From the terminal: pull the execution record, inspect the decision path, see which policy fired and why. Run a local replay with adjusted parameters. Check telemetry across the adjusted run. Push the corrected configuration.

Every step in the same session. No dashboard, no context switching, no stale data retrieved after the fact. The CLI is live against the runtime — what you see is the current state of the system.

Built for production environments

Most development tools optimize for speed in isolation — they become liabilities when the system they're operating is running in production.

The Waxell CLI keeps development fast without loosening the controls that production systems depend on. Live state is visible. Governance actions are available. Every operation runs through the same constraints as the rest of the system.

POLICY A

POLICY B

POLICY C

POLICY D

Designed to scale

Centralized, reference-based policies scale cleanly across workflows, teams, and environments.

They are suitable for systems where execution is continuous, changes are expected, and governance must remain consistent over time.

Policies do not become harder to manage as automation expands. They become more important.

CallSine automatically finds and researches each prospect by analyzing their website, LinkedIn profile, and company information. Get comprehensive insights instantly without spending hours on manual research. It even works with your existing database.

From here

Waxell is available now.

Install the SDK, connect to your instance, and start capturing what your agents actually do. Governance, policy enforcement, cost tracking, and full telemetry — running from the moment you initialize.

start free

Free during beta. 2-line setup.

FAQ

What is the Waxell CLI?

Waxell CLI is a command line interface for observing and operating AI agent systems in production. It gives developers real-time access to execution state, telemetry, governance controls, and the testing framework from a single terminal session — without switching between dashboards, logs, or separate tooling layers.

What can developers do with the Waxell CLI?

Developers can observe running agents, inspect recent executions, view telemetry, trace decision paths, apply governance actions such as kill-switches and execution halts, run local and remote test executions, replay scenarios, and create new agents through the Agent Composer integration — all without leaving the terminal.

Does the Waxell CLI bypass governance controls?

No. All actions taken through the Waxell 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. Operational convenience never becomes an implicit backdoor around system controls.

How does the Waxell CLI integrate with Agent Composer?

The CLI integrates directly with Waxell Agent Composer, allowing developers to create new agents from intent, adapt existing logic into Waxell's runtime model, and formalize prototypes into deployable systems from the command line — the same governed interface used for observation and operations.

Can the Waxell CLI be used for debugging production issues?

Yes. Because the CLI is live against the Waxell runtime, developers can pull execution records, inspect decision paths, identify which policy fired and why, run local replays with adjusted parameters, and push corrected configurations — all in a single terminal session against current system state, not stale dashboard data.