PostHog Jev Integration Status

Prerequisites

• Treat issue 5187 as a feature request, not released documentation.
• Review the live issue state before planning an implementation.
• Define privacy and retention rules before sending AI telemetry.
• Keep Jev credentials and request payloads outside browser code.

Implementation steps

1. 1Track the open PostHog issue for a supported TypeSafe wrapper.
2. 2Do not install or call an integration that has not been released.
3. 3If an application uses generic manual capture, define and validate its own event schema and privacy controls.
4. 4Keep manual telemetry separate from claims of first-party @posthog/ai support.
5. 5Update this page only after first-party release evidence becomes available.

Production checks

• The issue names captureAiGeneration as a manual alternative; that generic event path is not a Jev wrapper.
• Automatic Jev cost mapping is part of the request and is not currently available.
• Review inputs, outputs, trace identifiers, errors, and retention for sensitive data before any manual instrumentation.
• No installation command or executable Jev integration sample is shown while the request remains open.

Limitations and verification notes

PostHog issue 5187 is open with no assignee, no milestone, no first-party Jev wrapper, no automatic pricing mapper, and no known release date. Generic captureAiGeneration instrumentation remains an application-owned manual alternative.