Threads publishing as software
Codex runs postqueen commands, reads the JSON results and verifies each step, so your Threads pipeline behaves like any other task it automates in CI or cron.
Point Codex at the postqueen CLI and it creates, schedules and verifies Threads posts as one repeatable task you can rerun any time.
Set up the CLI inside the workspace Codex uses, then describe the Threads 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 Threads posts# from notes.md and schedule them# with postqueen"Codex runs postqueen commands, reads the JSON results and verifies each step, so your Threads pipeline behaves like any other task it automates in CI or cron.
Tell Codex when your followers are most active and it schedules posts into that window on Threads, day after day, without reminders.
Images upload in the same postqueen call, so Threads posts arrive with their media in place instead of a bare link.
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 followers on Threads until you do.
Codex calls postqueen to list your connected profiles and sees what Threads supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Threads-shaped posts and proposes publish times that match when your followers 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 Threads posts reliably.
Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the posts it creates, so your followers see them at the right moment.
Only if you ask it to. Tell it to save drafts and nothing is scheduled: the posts 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 Threads posts 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 drafts and rewrites copy in the conversational tone Threads favors and keeps drafts within the 500 character limit. Nothing publishes until you schedule it, and agents can drive the same flow through the CLI or the built-in MCP server.
postqueen tracks how each published post performs and how your follower count develops over time, right next to the calendar that produced the posts. That makes it easy to spot which topics and time slots are working.
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.