Agent posting safety: publish, fetch as a stranger, then assert on what's actually there
petrusenko_max · x · 2026-10-24
The author shares two rules for agents that post publicly: a failed check alerts a human and never deletes anything on its own, and a re-post is allowed exactly once, only after the old post is verified gone.
The pattern: publish, then fetch the post the way a stranger would (logged out), then assert on what's actually there. His checks cover 6 things: correct account, no URL in the body, image attached, reply threaded under the post, expected link in the reply, and no tracking params like ?sk=. Coverage tells you the code ran; a live check tells you it did the right thing.
More from coding & agent
- Polylane Launches for Cloudflare: Proactive Agents Watch Workers, Merge ~8 PRs a Day — dinasaur_404 · 2026-10-24
- Factory tested Reflection's Beam pre-launch via Together AI for day-0 support — togethercompute · 2026-10-24
- Benzi: compiler-backed coding agent hits 82.4% SWE-bench Verified for under $13 — DonkeyTheKing · 2026-10-24
- Bench shows GPT-5.6/6 Luna crush multi-agent coordination while DeepSeek V4 fails — JoshPurtell · 2026-10-24
- Payman AI launches MCP server for natural-language payments and payee management — modelcontextprotocol · 2026-10-24
- Grok Bot adds secure vault so agents can log in and pay without seeing your secrets — XFreeze · 2026-10-24