Posting with the CLI

Use openpost post for single posts, openpost thread for markdown threads, and openpost media for uploads.

Choose Accounts or Social Sets

Use --accounts for one-off account selection:

openpost post create --accounts x,linkedin --content 'Shipping today.'

Use social sets for reusable groups:

openpost set create launch --accounts x,linkedin --default
openpost post create --set launch --content 'Shipping today.'

If neither --accounts nor --set is passed, post create and thread create use the workspace default social set when one exists. If no default set exists, the post remains a draft with no destinations.

Manage sets with:

openpost set list
openpost set create <name> --accounts x,linkedin --default
openpost set add <name> --accounts bluesky
openpost set remove <name> --accounts linkedin
openpost set default <name>
openpost set delete <name> --yes

Schedule Posts

Natural language and RFC3339 are supported:

openpost post create --accounts x --content 'Shipping today.' --schedule 'tomorrow 2pm'
openpost post create --accounts x --file launch.md --schedule '2026-06-15T09:00:00+01:00'

Use the next available workspace posting slot:

openpost post create --content 'Shipping today.' --schedule next-slot

When a social set is selected or inherited as the default, next-slot asks the server for the next slot for that set:

openpost post create --set launch --content 'Shipping today.' --schedule next-slot
openpost thread create launch.md --set launch --schedule next-slot

Attach Media

Upload media first, then pass the returned media ID to a post command:

openpost media upload ./image.png --alt 'Product screenshot'
openpost post create --accounts x --content 'New queue view is live.' --media <id> --schedule 'next monday 9am'

--media also accepts a local file path and uploads it before creating the post.

Create Threads

Create a markdown file with optional front matter and --- separators:

---
set: launch
schedule: next-slot
---

We shipped the OpenPost CLI today.

---

It supports browser login, device mode for SSH hosts, token-based automation, social sets, and next-slot scheduling.

Then create the thread:

openpost thread create launch.md

Schedule Inputs

Input	Resolution
now	The next one-minute boundary, so the publish worker can pick it up.
draft	No scheduled time; the post remains a draft.
next-slot / next slot / slot	The next available posting schedule slot from the server.
2pm	Today at 14:00 if still in the future, otherwise tomorrow at 14:00.
tomorrow 2pm	Tomorrow at 14:00 in the resolved workspace/profile/local timezone.
in 3 hours	Three hours after the command runs.
next monday 9am	The next Monday after today at 09:00.
2026-06-15T09:00:00+01:00	The exact RFC3339 instant with the supplied offset.
2026-06-15 09:00	The local date and time in the resolved workspace/profile/local timezone.

today or tomorrow without a time is rejected so scheduled posts do not land at an accidental default time.