Bluesky Mention Monitor with Codex
An app password grants posting rights at the protocol level, so the protection here is that no writing operation exists in the workflow and the instructions rule out posting, liking, quoting and following in plain words. Following is the one people forget, because it is public on this network and reads as endorsement. Codex treats a prohibition list like that as hard edges rather than preferences.
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.
has anyone here actually run this in production behind a corporate proxy
Posted 25 minutes ago, 18 likes and 9 replies, moving through a self hosting feed that a few thousand infrastructure people read daily. She maintains a Python client our own docs link to and carries 1,900 followers. Her post sits as a reply inside a thread about egress costs, and two people below her say they hit the same wall last month and gave up on it.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect BlueSky
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.
Watch terms
Everything the sweep should look for: the company and product names, the domain you own, the handles people tag instead of typing a name, and any competitor you want to hear about. Terms are searched literally, so add the shortened forms and the wrong spellings your community actually types.
Ping policy
When a post is worth interrupting a working day and when it belongs in the once daily line instead: the accounts or communities that always count, the kinds of question you want reaching you fast, your quiet hours, and the channel all of it lands in.
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
Reading operations only
Search, notifications, thread, profile. Nothing in that set can leave a mark on your account or on anybody else's.
A follow would be visible
An account that follows everyone complaining about it becomes a story of its own. Restraint costs nothing and keeps every public gesture something a person chose.
Before you fork
What exactly does the app password let it reach?
Technically an app password can do more than this workflow uses, which is worth knowing rather than glossing over: the containment is the absence of write operations, not a permission boundary on Bluesky's side. You can revoke the app password from your account settings whenever you like and the sweeps stop. Nothing else in the account is exposed by it.
Run it with a different agent
Put Bluesky Mention Monitor to work on Codex
Free to start. Guided setup, a test run against staged conversations, and it's live.