The Warpcast scheduler that runs itself

Single casts, casts with image or link embeds, casts aimed at a specific Farcaster channel, and full threads. Compose the parts in order and postqueen publishes them as a native reply chain, no manual follow-up needed.

A Farcaster account and an approved signer. Farcaster accounts are onchain, so you register the FID once inside a Farcaster client, then approve postqueen as a signer that can cast on your behalf. You can revoke that signer at any time without touching the account itself.

Yes. Pick the channel when you compose and the cast lands there instead of only in your followers' home feed. Channels are where most Farcaster conversation actually happens, so it is worth choosing deliberately per post rather than defaulting to the home feed.

Yes. Write once, select every network, and edit each version before it ships. Farcaster counts bytes rather than characters, so a cast that looks short can still run over once emoji are in it. postqueen lets you trim that version on its own.

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.

The usual causes are a revoked signer key, a cast that went over the 1,024 byte limit once emoji were counted, or more than 2 embeds attached. postqueen shows the error on the post so you can fix it and reschedule.

Yes. Every cloud plan starts with a 7-day free trial with unlimited posts, and you can cancel anytime. Self-hosting the open source version is free forever.