Warpcast publishing as software
Codex runs postqueen commands, reads the JSON results and verifies each step, so your Warpcast pipeline behaves like any other task it automates in CI or cron.
Point Codex at the postqueen CLI and it creates, schedules and verifies Warpcast posts as one repeatable task you can rerun any time.
Set up the CLI inside the workspace Codex uses, then describe the Warpcast 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 Warpcast posts# from notes.md and schedule them# with postqueen"Codex runs postqueen commands, reads the JSON results and verifies each step, so your Warpcast 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 Warpcast, day after day, without reminders.
Images upload in the same postqueen call, so Warpcast 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 Warpcast until you do.
Codex calls postqueen to list your connected accounts and sees what Warpcast supports, so drafts start from real capabilities, not guesses.
Give it the brief. The agent writes Warpcast-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 Warpcast 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 Warpcast 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. The built-in assistant drafts casts in a tone that fits Farcaster and keeps them inside the byte budget. You edit everything and pick its time before it publishes, and agents like Claude Code or OpenClaw can generate and queue batches through the CLI or the MCP server.
postqueen keeps a record of every cast you scheduled and when it went out, next to the calendar that produced it. Farcaster data is open by nature, so engagement and follower numbers are easy to read on Warpcast or any Farcaster client, and postqueen focuses on getting casts out on a consistent schedule rather than duplicating those stats.
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.