CLI Capabilities

Snapshot basis:

  • API snapshot: agenticflow-cli/src/agenticflow_cli/openapi.json

  • Public operation count: 59

  • Rule in current CLI code: no security and not /v1/admin

Capability Matrix

Goal
What Agents/Users Can Do
Primary Commands

Discover platform surface

List and inspect currently exposed public operations

ops list --public-only, ops show <operation_id>

Plan task execution

Export and rank candidate operations for a task

catalog export --public-only --json, catalog rank --task "..." --public-only --json

Execute any public endpoint

Invoke by operation id or raw method/path

call --operation-id ..., call --method GET --path /v1/health

Node and schema discovery

Inspect node types and searchable node metadata

node-types list, node-types get --name ..., node-types search --query ...

Runtime safety

Enforce allow/block and spend guardrails

policy init ..., policy show, --dry-run

Runtime readiness

Validate configuration, auth, and endpoint health

doctor --json

High-Value Public Use Cases

1) Agent-Native Discovery Loop

Use in planning agents before execution:

agenticflow catalog export --public-only --json > catalog.json
agenticflow catalog rank --public-only --task "run an anonymous workflow and poll status" --json

2) Public Workflow Runtime

Validate and run anonymous/public workflows:

3) Public Agent Runtime

Fetch public agent metadata and stream responses:

4) Upload-Assisted Runs

Support file inputs in anonymous flows:

5) Public Workforce/MAS Orchestration

Run public workforce flows and inspect thread/event updates:

What This Enables for Agents

  • Autonomous capability discovery before spending tokens/calls.

  • Deterministic operation selection from machine-readable catalogs.

  • End-to-end public workflow and agent runtime interaction.

  • Safer execution with local policy controls and dry-run previews.

  • CI-friendly operational checks with JSON output.

Current Boundaries

As of February 19, 2026:

  • The public surface is driven by a bundled snapshot. If server APIs change, local command mappings may drift.

  • Some endpoints in the snapshot are operational/internal in practice (for example webhook sinks, diagnostics, auth callback helpers).

  • High-level wrappers that do not have public-snapshot equivalents are intentionally blocked with explicit unsupported-command errors:

    • workflow create|update

    • agent create|update

    • node-types dynamic-options

    • connections list|categories

Practical Recommendation

For production automations today:

  1. Discover with ops/catalog.

  2. Execute with call --operation-id.

  3. Gate with policy.

  4. Preflight with doctor.

Last updated