tirsa-factory-cli

Tirsa Factory CLI — run AI-powered software factory pipelines straight from your terminal. The CLI is a thin HTTP client: commands dispatch to Command Center, which handles project creation, pipeline scheduling and human-gate approvals server-side. Pipeline execution runs wherever your factory is deployed — Trigger.dev cloud or a local worker you run yourself (for agents that need to read and write to your local filesystem using your own coding-CLI subscriptions).

Website · Docs · Source

Install

npm install -g tirsa-factory-cli

Requires Node.js 20 or newer.

Quick start

# 1. Authenticate — opens a browser to pick a workspace & factory.
tirsa-factory login

# 2. Start a brand-new project from a market signal.
tirsa-factory from-scratch "Meal planning app for busy parents"

# 3. Track progress and human gates.
tirsa-factory status
tirsa-factory pending
tirsa-factory approve <run-id> --comment "looks good"

Commands

| Command | Description | |---|---| | tirsa-factory login | Browser-based login. Adds a profile keyed by <tenant>/<factory>. | | tirsa-factory logout | Remove the active profile. | | tirsa-factory whoami | Show the currently active profile. | | tirsa-factory profiles | List every saved profile. | | tirsa-factory use <name> | Switch the active profile. | | tirsa-factory from-scratch "…" | Create a new project and dispatch the full pipeline. | | tirsa-factory continue <slug> | Resume a paused project. | | tirsa-factory evolve <slug> … | Run a shorter sustentation cycle (fix / feature / improvement). | | tirsa-factory stop <slug> | Pause a running project after its current step. | | tirsa-factory status [slug] | List projects, or show detail + agent runs. | | tirsa-factory pending | Every human gate waiting for approval across your factory. | | tirsa-factory approve <run-id> | Approve a pending gate (optional --comment / --instructions). | | tirsa-factory reject <run-id> | Reject a pending gate (optional --comment). | | tirsa-factory clean <slug> | Delete a project and all its events, runs and artifacts. | | tirsa-factory doctor | Check local prerequisites (Node, Claude Code, Aider, Codex…). |

CI / non-interactive mode

Set these environment variables in your CI runner — the CLI skips the saved profile and uses them directly:

TIRSA_API_KEY=sk_live_…          # generate at /api-keys in the Command Center
TIRSA_TENANT=acme                # your workspace slug
TIRSA_FACTORY=main               # the factory slug to operate on
TIRSA_COMMAND_CENTER_URL=https://tirsa-factory.vercel.app   # optional override

A factory-scoped API key limits the blast radius — a leaked key can only operate within that factory.

License

UNLICENSED — Tirsa Software. Contact Tirsa Software for usage terms.