Operate publishing from scripts and terminals

Social media command-line interface

Use the Delulu CLI to connect accounts, upload media, draft, schedule, publish, retry, and review social posts with safe defaults and machine-readable output.

Start using Delulu See pricing

How it works

From setup to a finished workflow

1
Log in and select
Complete device or loopback authorization, then bind the intended workspace.
2
Prepare content
Connect accounts, upload local or remote media, and create a draft or schedule with explicit selectors.
3
Confirm the terminal state
Inspect posts and targets, approve eligible reviews, publish prepared work, or retry a failed destination.

Capabilities

What you can do

Device login and loopback PKCE authorization
Workspace selection and live overview
Account list, connect, and disconnect commands
Local-file and remote media upload
Draft, schedule, publish-now, edit, list, inspect, retry, and delete commands
Review queue and approval or rejection commands
Pretty terminal output plus JSON and compact piped output modes
Local operation journal and stable idempotency keys for mutations

Best fit

Who it is for

Developers scripting repeatable publishing work
Operators who prefer terminals to dashboards
Agent workflows that need non-interactive commands and structured results

Examples

Upload a local video, create a draft for selected accounts, and inspect the returned post ID.
List only scheduled posts in machine-readable output for a deployment check.
Approve a pending review from an authorized workspace role before publishing.

Safe defaults for unattended work

The CLI does not pause for interactive prompts. Browser steps are emitted as URLs and codes, unknown flags fail, destructive actions require confirmation, and draft is the default unless immediate publishing is explicitly requested.

Mutations use an operation journal and stable idempotency keys so a retry is less likely to create duplicate work. Exit codes separate syntax, authentication, permission, validation, conflict, network, partial-target, and timeout failures.

Requirements and limits

What to know before you start

The published CLI requires Node.js 20 or newer and a successful Delulu authorization flow.
Commands operate within the selected workspace and its live role, scope, quota, and review rules.
Scripts must inspect exit codes and final target states; a timed-out wait is not proof that publishing failed or succeeded.

Questions

What people ask about social media command-line interface

Does the CLI open interactive terminal prompts?

No. It is designed for scripts and agents. Browser authorization is reported as a URL or code, and commands fail clearly when required input is missing.

What happens if I run a post command without a publish flag?

Draft is the safe default. Immediate publishing requires explicit intent, and scheduling requires a valid future timestamp.

Can I use the output in a script?

Yes. Terminals default to readable output, while piped use can return compact structured output. JSON is also available explicitly.

Can the CLI upload local media?

Yes. The upload and post journeys accept local media, while completed media IDs can be reused in later operations.

How are partial publishing failures reported?

The CLI uses a distinct partial-target exit code and presents post and target results so automation can separate full success from a mixed destination outcome.