6-7 loops we use everyday to make PostHog self-driving
posthog.com
PostHog’s self-driving team describes internal “loops” that turn agent and user feedback into triage reports and automatically opened pull requests. One example shows an MCP tool missing_tool complaint leading to PR #90832 being opened 8 minutes later and merged on 17:27, then landing in production by 18:56 on August 28 (AI-related engineering). These loops change how work is done by shifting detection, dedupe, and root-cause work away from humans while letting engineers review, steer, and ensure the fixes actually hold.
Why it matters
PostHog describes agent loops that turn MCP feedback, Slack reports, issue specs, anomaly alerts, session replays, and runtime logs into investigations and pull requests. Persistent validation—deduplicating evidence, keeping humans in merge gates, then checking after deployment—helps ensure fixes actually hold.