Threads Mentions Agent with Codex
One mention in, one Slack message out, on a fixed skeleton: the mention quoted, one or two lines of what led up to it, then a draft under four hundred characters or the words NO REPLY with a reason. Codex likes a task with a hard boundary drawn around it, and the boundary here is a single conversation and a hard character limit.
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.
does this work if half the team is on Android, the last one we tried did not
The fourth reply in a thread somebody else started about tools for small design studios, now 61 replies long. She has 4,200 followers, runs a three person studio in Bilbao, and has never mentioned us before. The reply directly above hers says our onboarding was the easiest of the four she tested.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Threads
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.
Voice notes
How the account sounds and what it bothers replying to, in your own words: paste two or three real replies you were happy with, name the subjects you stay out of, and say who signs off on anything sensitive.
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
Four hundred characters, hard
The draft has to be sendable without editing, which means fitting the platform rather than nearly fitting it. Bounded output is straightforward work for this harness.
Fetch, fetch, look up, write
The post, the conversation, the replies, the profile. Four reads with an obvious ending and no state carried between one mention and the next.
Before you fork
What does it need from our Threads account?
Read access to your mentions and replies through the Meta app the account sits behind, plus the Slack channel the drafts land in. No publishing permission is requested, which is worth confirming on the Meta side too, since a broader scope would come from the app rather than from the agent.
Run it with a different agent
Put Threads Mentions Agent to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.