Command-line interface

The openpost CLI controls a running Hosted or self-hosted OpenPost instance. It follows the same workspace permissions and Publication lifecycle as the web app.

Use it when work starts in a terminal. For a long-running JavaScript or TypeScript service, use the SDK. For a visual workflow, use n8n.

Install

Install the npm wrapper, which downloads and verifies the matching release binary:

npm install -g @getopenpost/cli

You can also download the binary from GitHub Releases.

Sign in

Browser sign-in is the shortest path for an interactive shell:

openpost auth login https://app.openpo.st

For a headless shell, print the verification URL and code:

openpost auth login https://app.openpo.st --device

For CI, pass a developer token through stdin:

printf '%s\n' "$OPENPOST_TOKEN" | \
  openpost auth login https://app.openpo.st --with-token

The CLI stores named instance profiles. Use them to keep Hosted, staging, and self-hosted credentials separate:

openpost instance add hosted https://app.openpo.st
openpost instance use hosted
openpost instance health

Select a workspace

openpost workspace list
openpost workspace use personal
openpost account list

The selected workspace belongs to the active profile. You can override profile, instance, workspace, or token for one command with --profile, --instance, --workspace, or --token.

Connect new social accounts in the web app at <instance>/settings?tab=accounts. The CLI does not collect provider credentials.

Run openpost help or openpost <group> <command> --help for the installed version. New records store creation_source: "cli".

Continue

• Create and publish content
• Run scripts and CI
• Inspect and recover