v1.0.0

First public launch

Postx launches as a terminal-first workflow for drafting, scheduling, and publishing social posts—designed for fast iteration from your shell.

Quick links: Install , Docs , npm , GitHub .

Highlights

  • A guided compose flow for drafting posts and choosing publish-now vs schedule.
  • Channel discovery and configuration through an interactive command surface.
  • Queue visibility plus automation-friendly processing commands for scheduled work.
  • Documentation-focused onboarding: install, connect channels, compose, and ship.

What shipped

v1.0.0 establishes the core Postx loop: install the CLI, configure the channels available in your build, compose content in a focused terminal flow, and publish immediately or schedule for later. The command set is intentionally small and composable so you can learn the tool quickly and automate the repetitive parts.

Getting started (fast path)

Install from npm, run channel setup to authenticate and select targets, then start composing. If you are new to Postx, treat the docs as the quickest path from install to a successful first publish session—especially for understanding prerequisites, credentials, and channel-specific constraints.

Publishing workflow

The default workflow is meant to reduce context switching: stay in the terminal for drafting, validation, and scheduling instead of bouncing between dashboards. When you schedule content, Postx is designed to make upcoming work visible and actionable from the CLI.

Automation and operations

Postx includes commands aimed at operational use cases: reviewing scheduled work, processing due posts in one-shot runs, and running a polling worker where that fits your environment. This makes it easier to integrate publishing with cron, CI, or a small always-on service—without turning your laptop into the scheduler.

Compatibility notes

Channel capabilities can differ by network (auth model, media limits, rate limits). As Postx adds integrations, the most reliable way to understand what your installed build supports is to use the CLI help output and the project README alongside these release notes.

What this means for users

v1.0.0 is built for teams and individuals who want a calm, repeatable publishing routine. The goal is consistent shipping: fewer broken flows, less tab overload, and a clearer path from draft to scheduled to published.