Medium publishing as software
Codex runs postqueen commands, reads the JSON results and verifies each step, so your Medium pipeline behaves like any other task it automates in CI or cron.
Point Codex at the postqueen CLI and it creates, schedules and verifies Medium stories as one repeatable task you can rerun any time.
Set up the CLI inside the workspace Codex uses, then describe the Medium outcome you want in the task prompt.
# Inside a Codex sessionnpm install -g postqueenexport POSTQUEEN_API_KEY=your_api_key # Then prompt:# "Create this week's Medium stories# from notes.md and schedule them# with postqueen"Codex runs postqueen commands, reads the JSON results and verifies each step, so your Medium pipeline behaves like any other task it automates in CI or cron.
Tell Codex when your readers are most active and it schedules stories into that window on Medium, day after day, without reminders.
Codex hands postqueen the full draft, formatting included, and it lands on your Medium publications as complete stories, ready for readers.
Ask Codex for drafts only. They sit on the postqueen calendar unscheduled, so you can edit them and pick the time yourself, and nothing reaches your readers on Medium until you do.
Codex calls postqueen to list your connected publications and sees what Medium supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Medium-shaped stories and proposes publish times that match when your readers are around.
Look over the queue on the postqueen calendar and change anything you want. postqueen publishes each post at its time, and Codex can pull the results after.
Codex reads these limits from postqueen before it composes, so a draft that would be rejected never reaches the queue.
Scheduling, AI drafts, analytics and team roles, in one guide.
Install the postqueen CLI where Codex runs commands and export your API key. Every command returns JSON, so the agent can create, schedule and list Medium stories reliably.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the stories it creates, so your readers see them at the right moment.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the stories wait on the calendar until you set a time. Tell it to schedule, and they go out at the times you can see, which is the setup most people move to once they trust the output.
Yes. postqueen connects 30 channels, so Codex can turn the same brief into Medium stories plus adapted versions for every other channel you run.
No. The agent uses your regular API key and plan limits: unlimited posts on every plan, and channel counts from 5 on Creator up to uncapped on Ultimate.
Yes. It can turn a rough outline into a full draft, tighten a long section, or rewrite the opening in a tone that fits Medium's editorial feel. You always read it over before the story goes on the calendar.
Medium's own stats pages show how each story performs with readers, including views and reads. postqueen keeps the operational side: publish history, queue status and the cross-channel calendar, so you always know what shipped where.
Queue this week's posts in minutes, or hand the whole thing to your favorite AI. postqueen keeps publishing either way.
Seven days free. Cancel in one click from settings.