Automate Lemmy with Codex

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 Lemmy posts reliably.

Yes. Give it exact slots or a rule like mornings at nine and it sets publish times on the posts it creates, keeping your communities active on a steady rhythm.

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 Lemmy 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.

postqueen keeps a full history of what it published, in which community and when, so you can compare communities and time slots. Scores and comment threads live on Lemmy itself, since the network has no central analytics dashboard and every instance holds its own copy of the data. Reading your queue history next to the discussion is what tells you which communities actually want your posts.

The usual causes are an expired login on your instance, a community that restricts posting to moderators, an instance rate limit rejecting the submission, or a title over the 200 character maximum. Instance downtime counts too, since a volunteer run server goes offline for maintenance more often than a large corporate API does. postqueen marks the post with the error it got back so you can fix the cause and retry.