Run Luma image and video jobs, and track their files, from the terminal
Connect Luma Labs and your team can see what a generation is doing without opening a browser. Check job state, failure details, and output URLs. List the files in the account, newest first, and inspect ingest or moderation state. Submitting a paid image or video job, or deleting a file, is previewed and held for approval first.
11 tools: 3 read, 8 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Luma Labs run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as delete file, edit image, edit video, extract image layers, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Luma Labs — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.