Facebook Page Comment Agent with Codex
The loop is short and it comes round constantly: confirm the comment is not one of the page's own, read the post it sits under, answer from the rules or hand it to Slack, hide what the rules call spam. Codex moves through bounded work like that quickly, which matters when a question under a promoted post is worth answering inside the hour. Nothing in the sequence asks for invention, and invention is the one thing that would hurt.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Aurelia CostaCafe Nordeste
Can you do the mushroom one without cream? I am booking a table for six on Saturday and my sister cannot have any dairy at all.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Facebook
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Moderation rules
The questions you are happy to see answered in public and the answers themselves, what counts as spam or abuse on your page, which posts to stay out of completely, and where hidden comments and escalations should be reported.
Runs on Codex
Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Codex for this agent
The self check comes first
Anything the page wrote, including its own earlier replies, is skipped before the post is even read. Without it, each reply raises the event that produces the next one, in public.
Answers while the reach is live
Comments under a promoted post come from strangers you paid to reach. A fast turn is the difference between using that reach and watching it expire.
Before you fork
Could it end up replying to its own reply?
That is the loop the first rule exists to stop, and it is worth understanding because the failure would be public rather than silent. Events raised by the page's own comments are dropped on sight, before anything else happens. One reply per person per post is the second guard, so even an odd event sequence cannot become a thread of the page talking to itself.
Run it with a different agent
Put Facebook Page Comment Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.