postqueen CLI 2.0 is on npm

The postqueen command line interface is published on npm as postqueen, at 2.0.15 as of this release and 2.0.21 today. It runs against the same public REST API the web app uses, so a post you schedule from a terminal lands in the same calendar the rest of your team is looking at. Nothing you do from the CLI is a side channel.

What shipped in 2.0

Version 2.0 is the release that turned the CLI into a real way to drive postqueen instead of a convenience wrapper around a couple of endpoints. Three things carry most of the weight:

• Scheduling. Create a post for one channel or several at once, set the publish time, or send it straight away.
• Media upload. Push images and video from local files, so a post and its assets go up in the same step.
• Structured JSON output. Commands return JSON instead of formatted text, which is the part that makes the CLI callable by a program rather than only by a person.

That last one is the reason 2.0 exists. An agent (OpenClaw, Hermes, Claude Code, ChatGPT, Codex, Cursor) can shell out to a binary much more easily than it can hold a browser session, but it needs output it can parse without guessing. A pretty printed table is a bad contract for that. A result object is a good one.

How to try it

Install it globally from npm. You will need an API key from your postqueen account, cloud or self-hosted, and the help output covers where the CLI expects to find it.

# install the CLI
npm i -g postqueen
 
# confirm the version
postqueen --version
 
# list the commands
postqueen --help

If you self-host, point the CLI at your own instance instead of the cloud API. The commands are the same either way, because the API is the same either way.

The CLI is part of the open source project under AGPL-3.0. If a command is missing, or the JSON shape is awkward for the agent you are wiring up, that is worth an issue: https://github.com/GkhanKINAY/postqueen-app