Figena CLI, right in your terminal.

npm

npm install -g @figena/cli
figena --version

pnpm

pnpm add -g @figena/cli

yarn

yarn global add @figena/cli

Why Figena CLI

The CLI provides a controlled command-line experience for approved workflows.

Browser sign-in

Users authenticate through Figena in the browser instead of copying long-lived user tokens into their terminal.

Controlled access

Use documented commands and authenticated sessions without exposing internal platform behavior.

Agent operations

Work with supported agent operations through documented, reviewable commands.

Service automation

Automation access is available only for approved use cases and credentials.

Need integration access?

OpenPort remains the service integration path. Figena CLI complements it for terminal, CI, and agent workflows.

See OpenPort Contact us

What the CLI supports now

The CLI supports documented access, diagnostics, delivery, and visibility workflows.

Access and diagnostics

Browser-based figena auth login, plus logout, refresh, and status.
figena config and profile commands for API base URLs and local context.
figena doctor checks Node, profile, credentials, store permissions, API version, and health.
figena version reports CLI/API compatibility and server capabilities.

Agents and runs

figena agents list, get, create, version create, publish, and deploy.
Use documented delivery commands and review the result before relying on a change.
figena run and figena runs wait support repeatable execution flows.
figena runs trace helps inspect run and published invocation context.

OpenPort and knowledge

Supported integration commands are documented when they become available.
Administrative commands require an authenticated, authorized user.
Supported knowledge workflows are documented in the CLI help.
Validate supported specifications with the current CLI command documentation.

Automation safety

JSON output for scripts, agents, and CI jobs.
Pagination, retry, timeout, and backoff behavior in the API client.
Local config files use restrictive permissions.
The published package is designed to avoid source maps, test artifacts, private config, and server-side implementation details.

Command-line workflows, clearly bounded

Sign-in, agent delivery, and run visibility stay usable from the terminal while sensitive rules remain server-side.

Secure access

Browser sign-in without token copying

The terminal starts the flow, the browser handles identity, and the CLI stores only the issued local session.

Terminal

$figena auth login

$Opening browser sign-in...

Figena authorization

Confirm only when the code matches the login you started from the terminal.

Verification code

QFNZ-YC

Access approvedAuthorize

Agent delivery

Deploy and trace from one flow

The CLI submits an approved request and displays reviewable progress and results.

Command

figena agents list --output json

Validate spec

Checked by Figena API

Create version

Versioned server-side

Publish and smoke test

Policy controlled

Trace run

Readable JSON output

Deployment completed with traceable output.

Safety boundary

Controlled command-line access

The public CLI exposes documented commands without publishing internal platform design.

CLI

Authenticated service

Reviewable result

Internal implementation details are not part of the public interface

Authenticated accessPermission checksNo customer data in examples

Command-line workflows, with the platform in control.

Install, sign in, check status, and run documented workflows from the terminal.

FAQ

Is Figena CLI a finished product?

CLI availability and supported commands are described in the current public documentation.

Does the CLI run AI or core business logic locally?

The CLI provides documented commands for approved workflows; internal platform design is not part of the public interface.

What can it do today?

Use the built-in help and current public documentation to see the commands available to your account.

Can it work in CI and server environments?

Approved automation scenarios require credentials and permissions issued for that purpose.

Is this the only way to integrate?

No. OpenPort remains the service integration path. The CLI adds a command-line experience for operators, scripts, and agent workflows.

Bring Figena to the command line

Use Figena CLI to bring secure terminal workflows into scripts, operations, and AI agent workflows.

Request CLI access Explore OpenPort

Figena