dlazy-execute

name

dlazy-execute

description

Executes a plan's flat shape list end-to-end. Each shape is dispatched through /api/ai/tool in dependency order (resolved from `shape://name:<X>` refs); upstream outputs are substituted into downstream input, and `promptRefs` text is prepended to the consumer's `prompt`. IMPORTANT: only shapes whose `props.status` is `idle` actually run — any other status (`completed` / `failed` / `processing`) is treated as already-done and its existing `props.url` is reused as the producer output. To resume after a failure, set the failed shapes (and any you want re-run) back to `idle`, optionally edit their `props.input`, then call execute again. 执行 plan 输出的扁平节点列表。按 `shape://name:<X>` 引用计算依赖顺序，依次通过 /api/ai/tool 调度每个 shape；上游产物的 url 会替换到下游 input 中相应字段，`promptRefs` 引用的文本会被拼接到消费者的 `prompt` 前面。重要：只有 `props.status === "idle"` 的 shape 才会真正执行；其它状态（`completed` / `failed` / `processing`）一律视为已完成，其当前的 `props.url` 被作为产物供下游引用。若上次执行中途失败，可将失败节点（以及任何需要重跑的节点）的 status 改回 `idle`，可选地修改 `props.input`，再次调用 execute 即可从失败位置继续。

dlazy-execute

English · 中文

Executes a plan's flat shape list end-to-end. Each shape is dispatched through /api/ai/tool in dependency order (resolved from shape://name:<X> refs); upstream outputs are substituted into downstream input, and promptRefs text is prepended to the consumer's prompt. IMPORTANT: only shapes whose props.status is idle actually run — any other status (completed / failed / processing) is treated as already-done and its existing props.url is reused as the producer output. To resume after a failure, set the failed shapes (and any you want re-run) back to idle, optionally edit their props.input, then call execute again.

Trigger Keywords

• execute

Authentication

All requests require a dLazy API key. The recommended way to authenticate is:

dlazy login

This runs a device-code flow (also works in remote shells) and automatically saves your API key to the local CLI config — no manual copy/paste required.

Alternative: Set the Key Manually

If you already have an API key, you can save it directly:

dlazy auth set YOUR_API_KEY

The CLI saves the key in your user config directory (~/.dlazy/config.json on macOS/Linux, %USERPROFILE%\.dlazy\config.json on Windows), with file permissions restricted to your OS user account. You can also supply the key per-invocation via the DLAZY_API_KEY environment variable.

Getting Your API Key Manually

1. Sign in or create an account at dlazy.com
2. Go to dlazy.com/dashboard/organization/api-key
3. Copy the key shown in the API Key section

Each key is scoped to your dLazy organization and can be rotated or revoked at any time from the same dashboard.

About & Provenance

• CLI source code: github.com/dlazyai/cli
• Maintainer: dlazyai
• npm package: @dlazy/cli (pinned to 1.0.9 in this skill's install spec)
• Homepage: dlazy.com

You can install on demand without persisting a global binary by running:

npx @dlazy/cli@1.2.0 <command>

Or, if you prefer a global install, the skill's metadata.clawdbot.install field declares the exact pinned version (npm install -g @dlazy/cli@1.2.0). Review the GitHub source before installing.

How It Works

This skill is a thin client over the dLazy hosted API. When you invoke it:

• Prompts and parameters you provide are sent to the dLazy API endpoint (api.dlazy.com) for inference.
• Any local file paths you pass to image / video / audio fields are uploaded to dLazy's media storage (files.dlazy.com) so the model can read them — the same flow as any cloud-based generation API.
• Generated output URLs returned by the API are hosted on files.dlazy.com.

This is the standard SaaS pattern; the skill itself does not access network or filesystem resources beyond what the dLazy CLI already handles. See dlazy.com for the full service terms.

Usage

CRITICAL INSTRUCTION FOR AGENT: Execute dlazy execute to get the result.

dlazy execute -h

Options:
  --shapes [shapes...]                 Flat shape list to execute (typically plan.shapes). Cross-shape references inside `props.input` use either `shape://name:<name>` (resolves to the producer matching `props.name`) or `shape://shape:<id>` (resolves to the producer matching `id`); refs whose target is not in this array are dropped as if the param were absent. Each shape's `props.status` controls scheduling: only `idle` shapes run; shapes with any other status are treated as already-done and their `props.url` is reused as the producer output for downstream refs. To resume a failed run, set the failed/affected shapes back to `idle` (optionally edit their `props.input`) and call execute again.
  --projectId [projectId]              Optional project id forwarded to every downstream tool call (used for asset scoping and credit accounting).
  --sessionId [sessionId]              Optional execution session id; pass the same value across resume attempts so logs can be correlated.
  --dry-run                            Print payload + cost estimate without calling API
  --no-wait                            Return generateId immediately for async tasks
  --timeout <seconds>                  Max seconds to wait for async completion (default: "1800")
  -h, --help                           display help for command

Any flag also accepts pipe references — - (auto-pick from upstream stdin), @N (n-th output), @N.path (jsonpath into output), @* (all primary values), @stdin / @stdin:path (whole envelope). See dlazy --help for details.

Output Format

{
  "ok": true,
  "result": {
    "tool": "execute",
    "modelId": "execute",
    "outputs": [
      {
        "type": "shape",
        "id": "o_xxxxxxxx",
        "shape": {}
      }
    ]
  }
}

Async tasks (when --no-wait is passed) return outputs: [] and a task: { generateId, status } field instead. Use dlazy status <generateId> --wait to poll.

Examples

dlazy execute --prompt 'prompt content'

Error Handling

Code	Error Type	Example Message
401	Unauthorized (No API Key)	ok: false, code: "unauthorized", message: "API key is missing or invalid"
501	Missing required parameter	error: required option '--prompt <prompt>' not specified
502	Local file read error	Error: Image file/Video file not found: C:\path\to\your\file
503	API request failed (no balance)	ok: false, code: "insufficient_balance"
503	API request failed (server error)	HTTP status code error (500 server crash)
504	Asynchronous task execution failed	=== Generation Failed === / {Specific error reason returned by backend, for example "Prompt violates safety policy"}

AGENT CRITICAL INSTRUCTION:

1. If the execution result returns code: "insufficient_balance", you MUST explicitly inform the user that their credits are insufficient and guide them to recharge: https://dlazy.com/dashboard/organization/settings?tab=credits
2. If the execution result returns code: "unauthorized" or indicates missing API key, you MUST inform the user to get their API key from https://dlazy.com/dashboard/organization/api-key and save it using dlazy auth set <key> and resume the task.

Tips

Visit https://dlazy.com for more information.