> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iblueprint.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# iBlueprint CLI command reference: list, execute, status

> Complete reference for every iBlueprint CLI command: list, get, execute, and status — with flags, usage, and copy-pasteable output examples.

The iBlueprint CLI exposes four commands that cover the core blueprint workflow: discovering blueprints, inspecting their configuration, running them with inputs, and tracking the resulting execution. All commands communicate with the iBlueprint API over tRPC, and all require the `IBP_API_URL` environment variable to be set.

***

## `iblueprint list`

Lists all blueprints your account can access, rendered as a table in your terminal.

**Usage**

```bash theme={null}
iblueprint list
```

**Example output**

```
┌────────────────────────────────────┬─────────────────────────┬──────────┐
│ id                                 │ name                    │ status   │
├────────────────────────────────────┼─────────────────────────┼──────────┤
│ 3f2a1b4c-…                         │ Customer Onboarding Flow│ active   │
│ 9e8d7c6b-…                         │ Support Triage          │ draft    │
└────────────────────────────────────┴─────────────────────────┴──────────┘
```

The table displays each blueprint's `id`, `name` (title), and `status`. Copy an `id` value to use with the `get` or `execute` commands.

***

## `iblueprint get <id>`

Fetches the full details of a single blueprint and prints them as formatted JSON.

**Usage**

```bash theme={null}
iblueprint get <id>
```

**Arguments**

| Argument | Description                        |
| -------- | ---------------------------------- |
| `id`     | The UUID of the blueprint to fetch |

**Example**

```bash theme={null}
iblueprint get 3f2a1b4c-0000-0000-0000-000000000001
```

**Example output**

```json theme={null}
{
  "id": "3f2a1b4c-0000-0000-0000-000000000001",
  "title": "Customer Onboarding Flow",
  "status": "active",
  "nodes": [...],
  "edges": [...]
}
```

<Note>
  The exact fields returned depend on the blueprint's configuration. Use this command to inspect node definitions and edge connections before executing.
</Note>

***

## `iblueprint execute <id>`

Triggers a blueprint chain execution and returns the execution ID you can use to track progress.

**Usage**

```bash theme={null}
iblueprint execute <id> [--inputs <json>]
```

**Arguments**

| Argument | Description                          |
| -------- | ------------------------------------ |
| `id`     | The UUID of the blueprint to execute |

**Flags**

| Flag              | Short       | Description                                               |
| ----------------- | ----------- | --------------------------------------------------------- |
| `--inputs <json>` | `-i <json>` | A JSON string of input variables to pass to the blueprint |

**Examples**

Execute with no inputs:

```bash theme={null}
iblueprint execute 3f2a1b4c-0000-0000-0000-000000000001
```

Execute with input variables:

```bash theme={null}
iblueprint execute 3f2a1b4c-0000-0000-0000-000000000001 \
  --inputs '{"customer_name": "Acme Corp", "tier": "enterprise"}'
```

**Example output**

```
Execution started, ID: exec_7a9b2c3d-0000-0000-0000-000000000099
```

<Warning>
  The `--inputs` value must be valid JSON. The CLI passes it directly to `JSON.parse()`, so a malformed string will cause the command to exit with an error.
</Warning>

***

## `iblueprint status <execId>`

Checks the current status of a blueprint chain execution.

**Usage**

```bash theme={null}
iblueprint status <execId>
```

**Arguments**

| Argument | Description                                       |
| -------- | ------------------------------------------------- |
| `execId` | The execution ID returned by `iblueprint execute` |

**Example**

```bash theme={null}
iblueprint status exec_7a9b2c3d-0000-0000-0000-000000000099
```

**Example output**

```
Status: { id: 'exec_7a9b2c3d-…', status: 'completed', completedAt: '2026-05-12T14:30:00Z' }
```

***

## End-to-end workflow example

A typical workflow using all four commands:

<Steps>
  <Step title="Find your blueprint">
    ```bash theme={null}
    iblueprint list
    ```

    Identify the blueprint you want to run and copy its `id`.
  </Step>

  <Step title="Inspect the blueprint">
    ```bash theme={null}
    iblueprint get 3f2a1b4c-0000-0000-0000-000000000001
    ```

    Review the blueprint's nodes and required inputs before executing.
  </Step>

  <Step title="Execute the blueprint">
    ```bash theme={null}
    iblueprint execute 3f2a1b4c-0000-0000-0000-000000000001 \
      --inputs '{"customer_name": "Acme Corp"}'
    ```

    Copy the execution ID from the output.
  </Step>

  <Step title="Check execution status">
    ```bash theme={null}
    iblueprint status exec_7a9b2c3d-0000-0000-0000-000000000099
    ```

    Poll this command until the status shows `completed`.
  </Step>
</Steps>