익숙한 터미널에서 바로 쓰는 Figena CLI

안전하게 로그인하고 필요한 워크플로를 실행한 뒤, 다른 도구로 전환하지 않고 명확한 결과를 확인하세요.

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?

Cilila AI는 OpenPort를 통해 도구 연결과 관리를 제공합니다. Figena CLI는 터미널, CI, Agent 워크플로에서 사용하는 명령줄 인터페이스입니다.

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.

도구 연결과 지식

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.

경계가 분명한 명령줄 워크플로

로그인, Agent 전달, 실행 가시성은 터미널에서 사용할 수 있고 민감한 규칙은 서버에 남습니다.

보안 접근

token 복사 없는 브라우저 로그인

터미널이 흐름을 시작하고, 브라우저가 신원을 확인하며, CLI는 발급된 로컬 세션만 저장합니다.

터미널

$figena auth login

$Opening browser sign-in...

Figena 인증

터미널에서 시작한 로그인 코드와 일치할 때만 승인하세요.

확인 코드

QFNZ-YC

접근 승인됨승인

Agent 전달

배포와 추적을 한 흐름에서

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

명령

figena agents list --output json

spec 검증

Figena API가 확인

버전 생성

서버에서 버전 관리

게시 및 smoke test

정책으로 제어

실행 추적

읽기 쉬운 JSON 출력

추적 가능한 출력과 함께 배포가 완료되었습니다.

보안 경계

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 checksEnterprise scenarios use synthetic records only

Command-line workflows, with the platform in control.

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

FigenaFileEditWindow

Tue, Jul 14, 11:09 PM

FIGENA CLI

# Install path

$npm install -g @figena/cli

$figena --version

›figena

›Command line access for Figena workflows

✓step complete

# Sign in

$figena config init --profile production --api-base-url https://api.figena.com/api

$figena auth login

›Opening browser sign-in...

›Logged in as Olivia Chen

›Profile: production

✓step complete

# Check health

$figena doctor --output json

$figena version --output json

{

"ok": true,

"checks": ["node", "profile", "auth", "apiVersion", "apiHealth"]

}

✓step complete

# Review an agent

$figena agents list --output json

{

"items": [],

"status": "ok"

}

✓step complete

# Review recent runs

$figena runs list --output json

{

"items": [],

"status": "ok"

}

✓step complete

# View CLI help

$figena help

›Available commands depend on your authenticated account.

✓step complete

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?

아니요. Cilila AI는 OpenPort를 통해 도구 연결, 권한 부여, 호출을 관리합니다. CLI는 운영 담당자, 스크립트, Agent 워크플로를 위한 명령줄 경험을 제공합니다.

익숙한 터미널에서 바로 쓰는 Figena CLI

안전하게 로그인하고 필요한 워크플로를 실행한 뒤, 다른 도구로 전환하지 않고 명확한 결과를 확인하세요.

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?

Cilila AI는 OpenPort를 통해 도구 연결과 관리를 제공합니다. Figena CLI는 터미널, CI, Agent 워크플로에서 사용하는 명령줄 인터페이스입니다.

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.

도구 연결과 지식

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.

경계가 분명한 명령줄 워크플로

로그인, Agent 전달, 실행 가시성은 터미널에서 사용할 수 있고 민감한 규칙은 서버에 남습니다.

보안 접근

token 복사 없는 브라우저 로그인

터미널이 흐름을 시작하고, 브라우저가 신원을 확인하며, CLI는 발급된 로컬 세션만 저장합니다.

터미널

$figena auth login

$Opening browser sign-in...

Figena 인증

터미널에서 시작한 로그인 코드와 일치할 때만 승인하세요.

확인 코드

QFNZ-YC

접근 승인됨승인

Agent 전달

배포와 추적을 한 흐름에서

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

명령

figena agents list --output json

spec 검증

Figena API가 확인

버전 생성

서버에서 버전 관리

게시 및 smoke test

정책으로 제어

실행 추적

읽기 쉬운 JSON 출력

추적 가능한 출력과 함께 배포가 완료되었습니다.

보안 경계

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 checksEnterprise scenarios use synthetic records only

Command-line workflows, with the platform in control.

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

FigenaFileEditWindow

Tue, Jul 14, 11:09 PM

FIGENA CLI

# Install path

$npm install -g @figena/cli

$figena --version

›figena

›Command line access for Figena workflows

✓step complete

# Sign in

$figena config init --profile production --api-base-url https://api.figena.com/api

$figena auth login

›Opening browser sign-in...

›Logged in as Olivia Chen

›Profile: production

✓step complete

# Check health

$figena doctor --output json

$figena version --output json

{

"ok": true,

"checks": ["node", "profile", "auth", "apiVersion", "apiHealth"]

}

✓step complete

# Review an agent

$figena agents list --output json

{

"items": [],

"status": "ok"

}

✓step complete

# Review recent runs

$figena runs list --output json

{

"items": [],

"status": "ok"

}

✓step complete

# View CLI help

$figena help

›Available commands depend on your authenticated account.

✓step complete

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?