PostHog Python is a Python SDK that lets you send usage data from your Python code to PostHog. It is useful for instrumenting applications so PostHog can collect and analyze events, with documentation available for Python, Django, Flask, and related integrations like OpenFeature.
Project status
- Actively maintained, with an upstream push on November 4 and updates through November 3, 2026.
- Recent updates are frequent, with several SDK and OpenFeature provider updates landing on some days.
AI summary generated
Recent updates
openfeature-provider-posthog-v0.1.150
This is a patch release of openfeature-provider-posthog that upgrades its PostHog dependency to 7.86.0. The bundled SDK also changes MCP event classification, session IDs, FastMCP behavior, and string truncation; these details are present in the diff's posthog/CHANGELOG.md but are not in the supplied provider release notes.
BreakingFeaturesposthog-v7.86.0
PostHog Python 7.86.0 updates MCP analytics behavior, makes the `posthog.mcp` API and event schema stable across minor and patch releases, and fixes FastMCP middleware and schema-lookup issues. It also corrects manual-capture session identity and ensures truncated strings stay within their configured length limits.
BreakingFeaturesopenfeature-provider-posthog-v0.1.149
Release 0.1.149 updates the bundled `posthog` dependency from 7.84.3 to 7.85.0. The dependency update also changes MCP tool schemas, tool annotations, and the injected context description; these behavior changes are not described in the provider release notes, although they are detailed in the bundled `posthog` changelog.
Breakingposthog-v7.85.0
PostHog Python 7.85.0 changes the advertised MCP definitions for `get_more_tools` and `send_feedback`, shortens the injected `context` description, and makes injected `llm_model` optional. The release also updates the OpenFeature provider package version to track PostHog 7.85.0.
openfeature-provider-posthog-v0.1.148
Release 0.1.148 updates the PostHog Python SDK dependency to 7.84.3. The included SDK change also suppresses definition-load warnings for client-runtime flags, without changing local flag evaluation.
posthog-v7.84.3
PostHog Python 7.84.3 changes definition-load warning classification so client-only feature flags are excluded from warnings about experience continuity and unsupported definitions. Local evaluation and the loaded feature flag definitions remain unchanged.
openfeature-provider-posthog-v0.1.147
Release 0.1.147 updates the bundled PostHog Python SDK from 7.84.1 to 7.84.2. The SDK changes feature flag request retry behavior so connection-refused errors are raised immediately instead of being retried with backoff.
posthog-v7.84.2
This patch changes how `/flags` requests handle connection refusals: they now fail immediately instead of waiting through retry backoff. This makes flag errors surface sooner.
openfeature-provider-posthog-v0.1.146
This patch updates the bundled `posthog` dependency to 7.84.1 and bumps the provider package to 0.1.146. The code also revises descriptions advertised for several MCP tools and parameters, which may change how AI clients interpret them even though the release notes mention only the dependency update.
posthog-v7.84.1
PostHog Python 7.84.1 changes the advertised descriptions for MCP conversation and model fields and the `get_more_tools` and `send_feedback` tools, making them descriptive rather than behaviorally instructive. The runtime diff shows no function signature or public API implementation changes; it also updates package versions and reference metadata.
openfeature-provider-posthog-v0.1.145
The release notes describe a patch release that updates the provider's PostHog SDK dependency to 7.84.0. The code diff also introduces transactional email capabilities and fixes LangChain token accounting, neither of which is mentioned in the supplied release notes.
Featuresposthog-v7.84.0
PostHog Python 7.84.0 adds support for sending transactional emails using content rendered by the application, with new email options, retry and idempotency handling, and provider migration attribution. It also fixes LangChain token accounting for non-streamed ChatAnthropic calls that use prompt caching.
Featuresopenfeature-provider-posthog-v0.1.144
The release notes document an update to the PostHog dependency, from 7.83.2 to 7.83.3. The supplied diff also adds extensive Python SDK benchmark tooling and CI reporting, changes not described in the release notes.
posthog-v7.83.3
This patch fixes HTTP status reporting for failed streaming Gemini calls. The status from google-genai errors, such as 429 or 503, is now recorded in `$ai_http_status` instead of being reported as 0.
openfeature-provider-posthog-v0.1.143
This patch release updates the provider to version 0.1.143 and its PostHog Python SDK dependency to 7.83.2. The dependency includes a local feature-flag evaluation fix for feature enrollment; the supplied provider release notes do not describe that behavior change.
posthog-v7.83.2
This patch fixes local evaluation of feature flags that use early access feature enrollment. Local evaluation now matches the flags service for enrolled people, using the `$feature_enrollment/<flag key>` person property when provided and otherwise falling back to the flags service.
openfeature-provider-posthog-v0.1.142
This patch updates the provider to PostHog Python SDK 7.83.1. The code also fixes MCP SDK 2.x tool-schema handling so tool objects receive the context parameter, and expands CI coverage for MCP 2.x without FastMCP.
posthog-v7.83.1
PostHog Python 7.83.1 fixes MCP context injection for MCP SDK 2.x Tool objects, allowing `$mcp_intent` to be captured in that case. The code also adds MCP SDK 2.x test coverage both with and without FastMCP, and updates package versions and generated reference documentation.
openfeature-provider-posthog-v0.1.141
The provider release notes announce a dependency update to posthog 7.83.0. The diff also changes sync and async flag requests to use /flags?v=4 and brings in behavior changes from that dependency, including typed flag values, more granular handling of malformed flag records, and a change to missing metadata defaults.
posthog-v7.83.0
This release updates the SDK to request `/flags?v=4` and consume typed flag values, reasons, and metadata internally, while remaining compatible with older server responses and preserving existing values for valid flag records. Missing `FlagMetadata.id` and `FlagMetadata.version` now produce `None` instead of `0`, and malformed known fields cause only their flag record to fail.
Breaking