8.21.0
Minor Changes
-
#5407
6405dfdThanks @eli-r-ph! - With posthog-node 6.x.x, every AI event is sent throughcaptureAion the capture v1 AI lane, andenableFullAiCaptureonly controls truncation and media redaction. With posthog-node 5.x.x, nothing changes: AI events usecaptureunlessenableFullAiCaptureis set.
(2026-11-17) -
#5407
6405dfdThanks @eli-r-ph! - Add per-event options for posthog-node:posthogOptionson wrapped provider calls andwithTracing(), andoptionson the LangChain, OpenAI Agents, Claude Agent SDK, Google ADK and Genkit integrations. An event with no distinct id still has person processing turned off. On posthog-node 6.x.x, AI events carry person processing only as theprocess_person_profileoption. On posthog-node 5.x.x, each option that version knows is sent in the form it reads, and other keys are dropped. OpenAI Agentsinstrument()now passes every processor option, includingoptionsandonError, to the processor it registers.
(2026-11-17)
Patch Changes
-
#5407
6405dfdThanks @eli-r-ph! - Genkit spans and@posthog/mcpevents with no user distinct id set theprocess_person_profile: falseevent option on posthog-node 6.x.x, so a registered or contextprocess_person_profile: trueoption no longer creates a person for each trace or session. Genkit also counts an empty or whitespace-only distinct id as missing.
(2026-11-17) -
#5407
6405dfdThanks @eli-r-ph! - Export the table of per-event options and the event properties posthog-node 5.x.x reads instead, so posthog-node,@posthog/aiand@posthog/mcpshare one copy.
(2026-11-17) -
#5407
6405dfdThanks @eli-r-ph! -@posthog/ainow recognizes posthog-node 6.x.x by itsregisterOptionsmethod instead of bygetLibraryVersion(). A posthog-node 6.x.x client whose version a wrapper or subclass overrides, for example@posthog/mcp, no longer sends its AI events to the analytics endpoint. posthog-node 5.x.x clients still usecapture()unlessenableFullAiCaptureis on.
(2026-11-17) -
#5407
6405dfdThanks @eli-r-ph! - Supports posthog-node 6.x.x. Exception autocapture passes an options object tocaptureExceptionwhen the client is posthog-node 6.x.x, and positional arguments for posthog-node 5.x.x.
(2026-11-17) -
#5407
6405dfdThanks @eli-r-ph! - An AI event with no user distinct id now also sets theprocess_person_profile: falseevent option, so with posthog-node 6.x.x it stays personless even when a context or registered option turns person processing on. An empty or whitespace-only distinct id now counts as missing in every integration, so the event uses the trace or run id and stays personless.
(2026-11-17) -
Updated dependencies [
6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd,6405dfd]:- @posthog/core@1.69.0
- posthog-node@6.0.0