Non-Interactive Mode

Overview

All Lua CLI commands now support non-interactive mode, enabling seamless automation for:

AI IDEs (Cursor, GitHub Copilot, Windsurf, etc.)
CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
Shell scripting and automation
Programmatic agent management

Non-interactive mode bypasses all prompts by providing arguments and flags directly on the command line.

Every command now has non-interactive options with consistent naming patterns.

AI Agent Building Guide

Building with Cursor, Windsurf, or GitHub Copilot? See the complete AI Agent Building Guide for the full end-to-end workflow including authentication, testing strategies, sandbox vs production, common gotchas, and debugging.

Design Patterns

Consistent Option Naming

All commands follow these patterns:

Pattern	Description	Example
`--<entity>-name`	Select entity by name	`--skill-name mySkill`
`--<entity>-version`	Specify version	`--skill-version 1.0.5`
`--force`	Skip confirmation prompts	`--force`
`--json`	Output as JSON for parsing	`--json`
`[action]`	Positional action argument	`lua jobs view`

Action Arguments

Many commands accept an action as the first argument:

lua skills view                    # View all skills
lua skills versions --skill-name x # View versions for skill x
lua skills deploy --skill-name x   # Deploy skill x

CI/CD Mode (—ci flag)

The global --ci flag makes the CLI fail loudly on missing required arguments instead of silently prompting (which fails in non-TTY environments).

In CI/CD pipelines and non-TTY environments (piped input, background jobs), interactive prompts silently fail, causing commands to cancel without clear error messages. The --ci flag prevents this by throwing errors when required arguments are missing:

# Without --ci (fails silently in CI/CD)
lua push skill
# Silently cancels - no clear error

# With --ci (fails loudly with helpful error)
lua --ci push skill
# Error: Interactive prompt required but --ci flag is set. Provide all required flags or arguments.

Usage

The --ci flag is a global flag that must come before the command:

# Correct
lua --ci push skill --name mySkill --set-version 1.0.0 --force

# Incorrect
lua push skill --ci  # Won't work - must be global

When to Use

CI/CD Pipelines
Local Development
Scripts & Automation

Always use --ci in automated environments:

# GitHub Actions
- name: Push skill
  run: lua --ci push skill --name mySkill --set-version ${{ github.sha }} --force

# GitLab CI
script:
  - lua --ci push all --force --auto-deploy

Why: Ensures missing flags cause immediate, clear failures instead of silent hangs.

Don’t use --ci locally:

# Local - interactive prompts are helpful
lua push skill
? Select a skill: mySkill
? Enter version: 1.0.1

# CI/CD - no prompts, just errors
lua --ci push skill
# Error: missing --name flag

Why: Interactive prompts provide guidance and defaults.

Use --ci in bash scripts:

#!/bin/bash
set -e

# Fail fast if required args missing
lua --ci push skill \
  --name "$SKILL_NAME" \
  --set-version "$VERSION" \
  --force

Why: Scripts should fail fast and clearly, not hang waiting for input.

Behavior Differences

Scenario	Without —ci	With —ci
Missing required flag	Shows prompt (hangs in CI)	Throws error immediately
Non-TTY environment	Shows warning, continues	Throws error if prompts needed
All flags provided	Works normally	Works normally

Auto-Detection

Even without --ci, the CLI automatically detects non-TTY environments and shows a warning:

echo "" | lua push skill
# Warning: stdin is not a TTY. Interactive prompts may not work correctly.
# Tip: Use --ci flag in CI/CD environments to fail loudly on missing required flags.

However, this still allows the command to continue (and likely fail silently). Using --ci prevents this by failing immediately.

Complete Command Reference

Project Setup

init

Initialize a new project without prompts:

# Use existing agent
lua init --agent-id abc123

# Create agent in existing organization
lua init --agent-name "My Bot" --org-id org456

# Create agent + new organization
lua init --agent-name "My Bot" --org-name "Acme Corp"

# Create agent with a specific model
lua init --agent-name "My Bot" --org-id org456 --model openai/gpt-4o

# Override existing project
lua init --agent-id abc123 --force

# With example code
lua init --agent-id abc123 --with-examples

Option	Description
`--agent-id <id>`	Use existing agent by ID
`--agent-name <name>`	Name for new agent
`--org-id <id>`	Existing organization ID
`--org-name <name>`	New organization name
`--model <model>`	LLM model for the agent (e.g. `openai/gpt-4o`)
`--force`	Override existing `lua.skill.yaml`
`--with-examples`	Include example code

Development & Testing

test
sync
chat

Test skills, webhooks, or jobs without prompts:

# Test a skill/tool
lua test skill --name get_weather --input '{"city": "London"}'

# Test a webhook
lua test webhook --name payment-hook --input '{"query": {}, "headers": {}, "body": {"type": "payment"}}'

# Test a job
lua test job --name daily-report

# Test preprocessor
lua test preprocessor --name filter --input '{"message": "hello", "channel": "web"}'

# Test postprocessor
lua test postprocessor --name formatter --input '{"message": "hi", "response": "hello", "channel": "web"}'

Option	Description
`--name <name>`	Entity name to test
`--input <json>`	JSON input for testing

Detect and resolve drift without prompts:

# Check for drift (exit code 1 if found)
lua sync --check

# Auto-accept server state (pull server → local)
lua sync --accept

# Push local state to server without prompting
lua sync --push

Option	Description
`--check`	Check only, exit 1 if drift
`--accept`	Pull server state to local
`--push`	Push local state to server

Send messages without interactive session:

# Send to sandbox
lua chat -e sandbox -m "Hello, what can you do?"

# Send to production
lua chat -e production -m "Help me with my order"

# Default: sandbox
lua chat -m "Quick test message"

# Scoped to an explicit thread
lua chat -m "Run scenario A" --thread scenario-a

# Auto-generated thread (UUID printed at start)
lua chat -m "Isolated test" --thread

# Isolated test with auto-clear after response
lua chat -m "Run test" -t my-test --clear

# Send multiple messages concurrently (load / batch testing)
lua chat -b "Message 1" "Message 2" "Message 3"

# Batch with delay between messages (ms)
lua chat -b "Msg 1" "Msg 2" "Msg 3" -d 500

File attachments — use @<path> inside the message string:

# Attach an image
lua chat -m "@screenshot.png what's wrong with this UI?" -e sandbox

# Attach a document
lua chat -m "@report.pdf summarize this" -e production

# Multiple attachments
lua chat -m "compare @before.png and @after.png" -e sandbox

Option	Description
`-e, --env <env>`	Environment: sandbox or production
`-m, --message <text>`	Message to send (supports `@<path>` file attachments)
`-t, --thread [id]`	Scope to a thread (omit ID to auto-generate UUID)
`--clear`, `--clear-thread`	Clear thread history after response (requires `--thread`)
`-b, --batch <messages...>`	Send multiple messages concurrently
`-d, --delay <ms>`	Delay between batch messages in ms (default: 100)

Deployment

push
deploy

Push components without prompts:

# Push specific skill with version
lua push skill --name mySkill --set-version 1.0.5

# Push all components
lua push all --force

# Push and auto-deploy to production
lua push all --force --auto-deploy

# Push webhook
lua push webhook --name payment-hook --set-version 2.0.0

# Push job
lua push job --name daily-report --set-version 1.0.0

Option	Description
`--name <name>`	Entity name to push
`--set-version <ver>`	Version to set
`--force`	Skip confirmations
`--auto-deploy`	Deploy after push

Deploy to production without prompts:

# Deploy specific version
lua deploy --skill-name mySkill --skill-version 1.0.5 --force

# Deploy latest version
lua deploy --skill-name mySkill --skill-version latest --force

Option	Description
`--skill-name <name>`	Skill to deploy
`--skill-version <ver>`	Version or ‘latest’
`--force`	Skip confirmation

If the agent has already promoted an agent version, lua deploy performs a scoped promote (creates and promotes a new agent version identical to the current one, except for the deployed primitive) so the deploy is live immediately and shows up in lua version list. For CI/CD pipelines that want to snapshot and promote every primitive together instead, see lua version create --auto-push and lua version promote.

Entity Management

skills
webhooks
jobs
preprocessors
postprocessors

Manage skills without prompts:

# View all production skills
lua skills view

# View skill versions
lua skills versions --skill-name mySkill

# Deploy specific version
lua skills deploy --skill-name mySkill --skill-version 1.0.3

# Deploy latest
lua skills deploy --skill-name mySkill --skill-version latest

Action	Options Required
`view`	None
`versions`	`--skill-name`
`deploy`	`--skill-name`, `--skill-version`

Manage webhooks without prompts:

lua webhooks view
lua webhooks activate --webhook-name myWebhook
lua webhooks deactivate --webhook-name myWebhook
lua webhooks versions --webhook-name myWebhook
lua webhooks deploy --webhook-name myWebhook --webhook-version 1.0.3

# Event subscriptions
lua webhooks list-events
lua webhooks subscribe --webhook-name myWebhook --event message.delivered
lua webhooks unsubscribe --webhook-name myWebhook --event message.delivered

Action	Options Required
`view`	None
`activate`	`--webhook-name`
`deactivate`	`--webhook-name`
`versions`	`--webhook-name`
`deploy`	`--webhook-name`, `--webhook-version`
`list-events`	None
`subscribe`	`--webhook-name`, `--event`
`unsubscribe`	`--webhook-name`, `--event`

Available event types (WhatsApp):

Event	Description
`message.sent`	Message was sent to the recipient
`message.delivered`	Message was delivered to the recipient’s device
`message.read`	Recipient read the message
`message.failed`	Message failed to send
`message.played`	Recipient played a voice/video message

Manage scheduled jobs without prompts:

lua jobs view
lua jobs trigger -i healthCheck
lua jobs activate -i myJob
lua jobs deactivate -i myJob
lua jobs versions -i myJob
lua jobs deploy -i myJob -v 1.0.3
lua jobs deploy -i myJob -v latest
lua jobs history -i myJob
lua jobs delete -i oldJob

Option	Description
`-i, --job-name <name>`	Job name
`-v, --job-version <version>`	Version or ‘latest’ (deploy only)

Action	Options Required
`view`	None
`trigger`	`--job-name`
`activate`	`--job-name`
`deactivate`	`--job-name`
`versions`	`--job-name`
`deploy`	`--job-name`, `--job-version`
`history`	`--job-name`
`delete`	`--job-name`

Manage preprocessors without prompts:

lua preprocessors view
lua preprocessors activate --preprocessor-name myPre
lua preprocessors deactivate --preprocessor-name myPre
lua preprocessors versions --preprocessor-name myPre
lua preprocessors deploy --preprocessor-name myPre --preprocessor-version 1.0.3
lua preprocessors delete --preprocessor-name oldPre

Manage postprocessors without prompts:

lua postprocessors view
lua postprocessors activate --postprocessor-name myPost
lua postprocessors deactivate --postprocessor-name myPost
lua postprocessors versions --postprocessor-name myPost
lua postprocessors deploy --postprocessor-name myPost --postprocessor-version 1.0.3
lua postprocessors delete --postprocessor-name oldPost

Configuration

Manage environment variables without prompts:

# List variables
lua env sandbox --list
lua env production --list

# Set variable
lua env sandbox -k DATABASE_URL -v "postgres://localhost/db"
lua env production -k API_KEY -v "sk_live_xxx"

# Delete variable
lua env production -k OLD_KEY --delete

Option	Description
`--list`	List all variables
`-k, --key <name>`	Variable name
`-v, --value <val>`	Variable value
`-d, --delete`	Delete the variable

Manage persona without prompts:

# View current persona
lua persona production view

# List versions
lua persona production versions

# Deploy specific version
lua persona production deploy --persona-version 5

# Deploy latest
lua persona production deploy --persona-version latest --force

Action	Options
`view`	None
`versions`	None
`deploy`	`--persona-version`, `--force`

Manage features without prompts:

lua features list
lua features enable --feature-name rag
lua features disable --feature-name rag
lua features view --feature-name webSearch

Action	Options Required
`list`	None
`enable`	`--feature-name`
`disable`	`--feature-name`
`view`	`--feature-name`

Manage knowledge base without prompts:

lua resources list
lua resources view --resource-name "FAQ Document"
lua resources delete --resource-name "Old Document"

Action	Options Required
`list`	None
`view`	`--resource-name`
`delete`	`--resource-name`

Manage MCP servers without prompts:

lua mcp list
lua mcp activate --server-name filesystem
lua mcp deactivate --server-name api-server
lua mcp delete --server-name old-server

# Positional style also works
lua mcp activate filesystem

Action	Options Required
`list`	None
`activate`	`--server-name`
`deactivate`	`--server-name`
`delete`	`--server-name`

Connect and manage third-party integrations without prompts:Discovery Commands (for AI agents and scripting):

# View available integrations
lua integrations available

# Get integration details (scopes and triggers)
lua integrations info linear
lua integrations info linear --json

# List available trigger events
lua integrations webhooks events --integration linear
lua integrations webhooks events --integration linear --json

Connect with Triggers:

# Connect with triggers enabled (recommended)
lua integrations connect --integration linear --auth-method oauth --scopes all \
  --triggers task_task.created,task_task.updated

# Connect with all available triggers
lua integrations connect --integration linear --auth-method oauth --scopes all --triggers all

# Connect without triggers
lua integrations connect --integration linear --auth-method oauth --scopes all

# Connect with custom webhook URL instead of agent trigger
lua integrations connect --integration linear --auth-method oauth --scopes all \
  --triggers task_task.created --custom-webhook --hook-url https://my-server.com/webhook

# List connections
lua integrations list

# Update connection scopes
lua integrations update --integration linear --scopes "task_task_read,task_task_write"

# Disconnect
lua integrations disconnect --connection-id 6978e0294d9c2007ed5cb129

Connect Options:

Option	Description
`--integration <type>`	Integration type (linear, discord, etc.)
`--auth-method <method>`	`oauth` or `token`
`--scopes <scopes>`	Comma-separated scopes or `all`
`--hide-sensitive <bool>`	Hide sensitive data (default: true)
`--triggers <events>`	Comma-separated triggers or `all`
`--custom-webhook`	Use custom URL instead of agent trigger
`--hook-url <url>`	Custom webhook URL
`--connection-id <id>`	Connection ID (for disconnect)

Info Options:

Option	Description
`--json`	Output as JSON for scripting

Trigger Management:

# List triggers
lua integrations webhooks list

# List available trigger events
lua integrations webhooks events --integration linear --json

# Create trigger (agent wake-up mode - default)
lua integrations webhooks create \
  --connection abc123 \
  --object task_task \
  --event created

# Create trigger with custom webhook URL
lua integrations webhooks create \
  --connection abc123 \
  --object task_task \
  --event created \
  --hook-url https://my-server.com/webhook

# Create trigger with custom polling interval
lua integrations webhooks create \
  --connection abc123 \
  --object task_task \
  --event updated \
  --interval 120

# Delete trigger
lua integrations webhooks delete --webhook-id wh_xyz789

Trigger Options:

Option	Description
`--connection <id>`	Connection ID
`--integration <type>`	Integration type (for events discovery)
`--object <type>`	Object type (task_task, calendar_event, etc.)
`--event <type>`	Event: created, updated, deleted
`--hook-url <url>`	Custom webhook URL (default: agent trigger)
`--interval <mins>`	Polling interval (60, 120, 240, 480, 720, 1440, 2880)
`--webhook-id <id>`	Trigger ID (for delete)
`--json`	Output as JSON (for events command)

MCP Server Management:

lua integrations mcp list
lua integrations mcp activate --connection abc123
lua integrations mcp deactivate --connection abc123

Viewing & Debugging

logs
production
channels

View logs without prompts:

# View all logs
lua logs --type all --limit 50

# Filter by type
lua logs --type skill --limit 20
lua logs --type webhook --limit 20
lua logs --type job --limit 20

# Filter by specific entity
lua logs --type skill --name mySkill --limit 10

# Pagination
lua logs --type all --limit 20 --page 2

# JSON output for scripting
lua logs --type all --json

# Inspect logs for another agent you own
lua logs --agent-id agent-abc123 --type skill --limit 10

Option	Description
`--type <type>`	all, skill, job, webhook, preprocessor, postprocessor, user_message, agent_response
`--name <name>`	Entity name (requires —type, not for message types)
`--user-id <userId>`	Filter logs by user ID
`--agent-id <agentId>`	Target a specific agent (admin access required)
`--limit <n>`	Number of logs (default: 20)
`--page <n>`	Page number
`--json`	JSON output

View production state without prompts:

lua production overview    # Production summary
lua production persona     # Current persona
lua production skills      # Deployed skills
lua production env         # Environment variables

View channels without prompts:

lua channels list    # List all channels

Authentication & Utilities

auth
chat clear

Authentication commands with —force:

# View API key without confirmation
lua auth key --force

# Logout without confirmation
lua auth logout --force

Clear history without confirmation:

# Clear all history
lua chat clear --force

# Clear specific user's history
lua chat clear --user [email protected] --force
lua chat clear --user +1234567890 --force

# Clear a specific thread's history
lua chat clear --thread my-test-scenario --force

Marketplace

lua marketplace [noun] [action], where noun is skill or template. See the Marketplace Command reference for the full flag set.

Skill Actions
Template Actions

Publish, manage, and install skills — all in one flat action namespace:

# List a skill (public by default)
lua marketplace skill list --skill-name mySkill --display-name "My Skill"

# List a private skill (org-only)
lua marketplace skill list --skill-name mySkill --display-name "My Skill" --visibility private

# Publish a version
lua marketplace skill publish --marketplace-id xyz --version-id v1 --changelog "Bug fixes"

# Edit metadata
lua marketplace skill edit --marketplace-id xyz --display-name "New Name"

# Unlist
lua marketplace skill unlist --marketplace-id xyz --force

# Unpublish version
lua marketplace skill unpublish --marketplace-id xyz --version-id v1 --force

# View my listings
lua marketplace skill mine --json

# Search marketplace
lua marketplace skill search --query "CRM" --limit 10 --json

# View skill details
lua marketplace skill view --marketplace-id xyz --json

# Install skill
lua marketplace skill install --marketplace-id xyz --version-id v1 --force

# With environment variables
lua marketplace skill install --marketplace-id xyz --version-id v1 --env-vars "API_KEY=xxx,SECRET=yyy" --force

# Update installed skill
lua marketplace skill update --skill-name mySkill --version-id v2

# Uninstall
lua marketplace skill uninstall --skill-name mySkill --force

# List installed
lua marketplace skill installed --json

Publish and roll out agent templates — see Agent Templates for the full lifecycle:

# Create a template from the current agent (private by default)
lua marketplace template create --name support-bot --display-name "Support Bot"

# Publish a version, declaring its env contract
lua marketplace template publish --template-id tpl_abc --changelog "Bug fixes" \
  --env-contract "STRIPE_KEY=Stripe secret key"

# Install onto the current agent
lua marketplace template install --template-id tpl_abc --env-vars "STRIPE_KEY=sk_xxx" --force

# Roll a new version out to a fleet
lua marketplace template apply --template-id tpl_abc --all-installed --force

# Check the fleet ledger
lua marketplace template status --template-id tpl_abc --json

# List templates installed on this agent
lua marketplace template installed --json

# Uninstall from this agent
lua marketplace template uninstall --template-id tpl_abc --force

Example Workflows

AI IDE Workflow (Cursor, Copilot)

When an AI assistant needs to manage your agent:

# Initialize project for existing agent
lua init --agent-id agent_abc123

# Set environment variables
lua env sandbox -k OPENAI_KEY -v "sk-xxx"
lua env production -k OPENAI_KEY -v "sk-yyy"

# Discover and connect third-party integrations
lua integrations available
lua integrations info linear --json                    # Get scopes and triggers as JSON
lua integrations connect --integration linear --auth-method oauth --scopes all \
  --triggers task_task.created,task_task.updated       # Connect with triggers

# Verify integration
lua integrations list
lua integrations webhooks list

# Test a specific tool
lua test skill --name get_order --input '{"orderId": "123"}'

# Push and deploy
lua push skill --name order-service --set-version 1.0.0 --force
lua deploy --skill-name order-service --skill-version latest --force

# Check logs
lua logs --type skill --name order-service --limit 10 --json

GitHub Actions CI/CD

name: Deploy Agent

on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '20'
      
      - name: Install dependencies
        run: npm ci
      
      - name: Install Lua CLI
        run: npm install -g lua-cli
      
      - name: Configure auth
        run: lua auth configure
        env:
          LUA_API_KEY: ${{ secrets.LUA_API_KEY }}
      
      - name: Check for drift
        run: lua sync --check
      
      - name: Compile
        run: lua compile
      
      - name: Push version
        run: lua push skill --name ${{ github.event.repository.name }} --set-version ${{ github.sha }} --force
      
      - name: Deploy to production
        run: lua deploy --skill-name ${{ github.event.repository.name }} --skill-version latest --force
      
      - name: Verify deployment
        run: lua logs --type skill --name ${{ github.event.repository.name }} --limit 5 --json

Post-deploy verification (CI-friendly)

After any production deploy, run a 3-line probe to confirm the new version is healthy. This is the CI version of the canonical post-deploy debug loop:

# Push and auto-deploy in one shot
lua --ci push all --force --auto-deploy

# Send a probe message to production
lua --ci chat -m "verify production" -e production -t prod-verify --clear

# Confirm zero agent errors fired during the probe
lua logs --type agent_error --limit 5 --json | jq '.logs | length'

Wire the third line into your pipeline’s exit code so a non-zero error count fails the build:

errors=$(lua logs --type agent_error --limit 5 --json | jq '.logs | length')
if [ "$errors" -gt 0 ]; then
  echo "Production has $errors agent errors after deploy — failing build."
  exit 1
fi

Silencing post-action hints in CI. The CLI prints ✨ Tip: / 💡 Diagnose: lines and a quiet agent_error probe summary after each command. They’re useful interactively but noisy when CI captures only command output. Set LUA_NO_HINTS=1 to silence all of them:

export LUA_NO_HINTS=1
lua --ci push all --force --auto-deploy
lua --ci chat -m "verify production" -e production

Bash Scripting

#!/bin/bash
set -e

SKILL_NAME="my-skill"
VERSION=$(date +%Y%m%d%H%M%S)

echo "Deploying $SKILL_NAME version $VERSION"

# Check drift
if ! lua sync --check; then
  echo "Drift detected! Run 'lua sync' manually to resolve."
  exit 1
fi

# Compile and push
lua compile
lua push skill --name "$SKILL_NAME" --set-version "$VERSION" --force

# Deploy
lua deploy --skill-name "$SKILL_NAME" --skill-version latest --force

# Verify
lua logs --type skill --name "$SKILL_NAME" --limit 5

echo "Deployment complete!"

Multi-Component Deployment

#!/bin/bash
# Deploy all components at once

VERSION="2.0.0"

# Push everything
lua push all --force

# Or push individually with versions
lua push skill --name order-service --set-version $VERSION --force
lua push webhook --name payment-hook --set-version $VERSION --force
lua push job --name daily-report --set-version $VERSION --force

# Deploy skills
lua deploy --skill-name order-service --skill-version latest --force

# Activate webhooks and jobs
lua webhooks activate --webhook-name payment-hook
lua jobs activate --job-name daily-report

# Subscribe webhook to delivery events
lua webhooks subscribe --webhook-name payment-hook --event message.delivered
lua webhooks subscribe --webhook-name payment-hook --event message.failed

# Verify
lua production overview

Exit Codes

All commands return consistent exit codes:

Code	Meaning
`0`	Success
`1`	Error (missing args, not found, API error)

Use exit codes in scripts:

if lua sync --check; then
  echo "No drift"
else
  echo "Drift detected"
  exit 1
fi

JSON Output

Commands with --json output machine-readable JSON:

# Get logs as JSON
logs=$(lua logs --type all --limit 5 --json)

# Parse with jq
echo "$logs" | jq '.logs[].message'

# Get installed skills
skills=$(lua marketplace skill installed --json)

Best Practices

Always use --force in CI/CD

In automated pipelines, always use --force to skip confirmations:

lua push all --force
lua deploy --skill-name x --skill-version latest --force

Use --check for validation

Use lua sync --check in CI to fail builds on drift:

lua sync --check || { echo "Drift detected"; exit 1; }

Use --json for parsing

When processing output programmatically, use --json:

lua logs --json | jq '.logs | length'

Version with timestamps or git SHAs

Use dynamic versions in CI:

lua push skill --name x --set-version $(git rev-parse --short HEAD) --force

CLI Overview

All available commands

Skill Management

init, test, push, deploy details

Sync Command

Drift detection details

Environment Variables

Managing configuration

Getting Started

Core Concepts

CLI Commands

API Reference

Template & Examples

Non-Interactive Mode

Overview

AI Agent Building Guide

Design Patterns

Consistent Option Naming

Action Arguments

CI/CD Mode (—ci flag)

Usage

When to Use

Behavior Differences

Auto-Detection

Complete Command Reference

Project Setup

Development & Testing

Deployment

Entity Management

Configuration

Viewing & Debugging

Authentication & Utilities

Marketplace

Example Workflows

AI IDE Workflow (Cursor, Copilot)

GitHub Actions CI/CD

Post-deploy verification (CI-friendly)

Bash Scripting

Multi-Component Deployment

Exit Codes

JSON Output

Best Practices

CLI Overview

Skill Management

Sync Command

Environment Variables

​Overview

AI Agent Building Guide

​Design Patterns

​Consistent Option Naming

​Action Arguments

​CI/CD Mode (—ci flag)

​Usage

​When to Use

​Behavior Differences

​Auto-Detection

​Complete Command Reference

​Project Setup

​Development & Testing

​Deployment

​Entity Management

​Configuration

​Viewing & Debugging

​Authentication & Utilities

​Marketplace

​Example Workflows

​AI IDE Workflow (Cursor, Copilot)

​GitHub Actions CI/CD

​Post-deploy verification (CI-friendly)

​Bash Scripting

​Multi-Component Deployment

​Exit Codes

​JSON Output

​Best Practices

​Related

CLI Overview

Skill Management

Sync Command

Environment Variables

Overview

Design Patterns

Consistent Option Naming

Action Arguments

CI/CD Mode (—ci flag)

Usage

When to Use

Behavior Differences

Auto-Detection

Complete Command Reference

Project Setup

Development & Testing

Deployment

Entity Management

Configuration

Viewing & Debugging

Authentication & Utilities

Marketplace

Example Workflows

AI IDE Workflow (Cursor, Copilot)

GitHub Actions CI/CD

Post-deploy verification (CI-friendly)

Bash Scripting

Multi-Component Deployment

Exit Codes

JSON Output

Best Practices

Related