Self-driving product
A product whose usage data drives an agent loop: find what to fix, open a pull request, measure the change, while engineers set limits and approve merges.
The term comes from PostHog, which describes it as autonomy from user instruction, not from the engineer. A general coding agent has your code but not your context; product analytics, session replays and errors supply it. Agents look for small wins such as bugs and interface friction, propose a change, and the result is checked against a metric, often behind a feature flag or an A/B test. Nothing merges without the team’s approval.
Related terms
- Session replay: A reconstruction of what a user saw and did on a site: clicks, scrolls, page changes and errors, played back like a video.
- Feature flags: Switches in code that turn a feature on or off for some or all users without a new deploy.
- A/B test: Showing two versions to randomly split users and measuring which one moves a chosen metric.
- Software factory (AI agents): A pipeline where agents write and fix most of the code while people write specs, set guardrails, design the checks and decide what ships.
