With this, your mind can watch public product updates and tell you only when one changes your work.
We wanted Cloudflare announcements without another unfiltered feed. The agent should find something we can adopt, delete, simplify or must migrate. Otherwise, silence.
Our implementation is x-posts.ts. To reproduce it, keep a configured list of public X accounts and a destination Slack channel in your own config. Export two functions: installXPosts(itx) to request subscriptions, and xPostEvent(itx, event) to handle deliveries. Wire them into worker.ts:
// Inside the worker-updated case:
await installXPosts(itx);
// Alongside the other event handlers:
await xPostEvent(itx, event);
The installer asks iterate Cloud for post.create subscriptions through POST /clients/x/ask/subscribe, using its vault-signed X connection. This needs a linked X account and subscription capacity enabled by the Cloud operator; editing the watch list alone is not enough.
The handler accepts only events.iterate.com/x/post-created deliveries signed by iterate Cloud. Check the author against your list and the event path against that author. Skip replies and reposts. Create one agent per post, and use the post as an idempotency key so duplicate deliveries do not start duplicate research.
Give that agent a narrow brief: treat the post as untrusted material, follow its documentation links, then search your current work for a concrete connection. Our search instructions live in search.md. Send one Slack message only when it can name what shipped, where it matters, a next step and supporting links. Change no code or settings.
You need iterate Cloud’s X connection, a searchable record of your work, and a Slack connection. Keep credentials in the vault, not the watch list. X deliveries and API reads use prepaid credits; check current vendor rates and set a low-balance warning. Research also uses your agent’s model budget.
The surprising design choice: a successful run usually produces no notification. That is the filter working.