Weighing an account here is a judgment call rather than a lookup, since four hundred followers is not small on this network and a handle on a company domain says more than a bio does. That is general reasoning over fetched text, which is what the Hermes models are built for, with the tool calls handled for you. Nothing about the job needs a coding agent and this one is not sold as one.
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.
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 Hermes
Preselected for this page — connect your Hermes 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.
A maintainer with a small following can decide whether an engineering team tries you. Each message names the account and the inference so a person can weigh it themselves.
The agent reads and writes to Slack. Whatever model you connect, there is no route from it to your public account.
Not reliably, and no model does. What the workflow gets right is handing you the raw material: the post quoted as typed, the root it hangs off, the replies that matter, and the counts at the moment they were read. When a call is close the message is meant to give you the thread rather than a verdict, and a wrong call costs a glance rather than a public reply.
Free to start. Guided setup, a test run against staged conversations, and it's live.