# PostHog/posthog

Source: [GitHub](https://github.com/PostHog/posthog)  
Feed7 permalink: https://feed7.dev/p/posthog-1dwbj56  
Published: Unknown  
Trust: Needs Review (needs_review)

## Why Included

PostHog combines product telemetry, LLM tracing, and agent-driven diagnosis in one platform, with MCP access for Claude Code, Cursor, and other compatible agents.

## Source Summary

PostHog combines analytics, replay, flags, experiments, errors, logs, surveys, pipelines, and **AI observability**. Its self-driving mode turns product signals into researched reports and pull requests for review.

## Practical Implication

Connect its **MCP** to Claude Code, Cursor, or another compatible agent when you want coding workflows grounded in product behavior, errors, traces, latency, and cost rather than repository context alone.

## Agent-Ready Context

PostHog combines analytics, replay, flags, experiments, errors, logs, surveys, pipelines, and **AI observability**. Its self-driving mode turns product signals into researched reports and pull requests for review.

Connect its **MCP** to Claude Code, Cursor, or another compatible agent when you want coding workflows grounded in product behavior, errors, traces, latency, and cost rather than repository context alone.

The hobby deployment is unsupported, recommends **4GB memory**, and is intended for roughly **100k events per month** before migration to PostHog Cloud is advised. The ee directory also has separate licensing.

## Connected Context

Feed7 judgment across 542 accumulated Signals:

This moves coding-agent context from planned code and model traces into observed product behavior, creating a possible feedback path from errors, usage, latency, and cost to reviewed code changes. It reinforces the emerging production-loop direction, while narrowing the self-hosted option through explicit operating limits and leaving autonomy, access control, and licensing as separate deployment decisions.

- [Firetiger joins Cursor](https://feed7.dev/p/firetiger-06hv2bc) — Firetiger’s planned rollout monitoring and incident investigation point toward the same closed production loop; PostHog supplies an existing product-signal and pull-request path that makes that direction more concrete.
- [Agent Runs now available in the Vercel MCP and CLI](https://feed7.dev/p/agent-runs-vercel-mcp-cli-06cfo04) — Vercel Agent Runs exposes an agent’s own reasoning and tool traces, while PostHog adds product and application outcomes; together they cover complementary sides of diagnosing agent-driven changes.
- [cursor/plugins](https://feed7.dev/p/plugins-0vuoqp2) — Cursor’s manifest-based MCP packaging offers a distribution route for integrations like PostHog, but also makes its production-data access part of the plugin trust boundary.
- [Set up coding agents in one command with AI Gateway](https://feed7.dev/p/set-up-coding-agents-in-one-command-with-ai-gateway-0wmcqce) — AI Gateway centralizes model-side budgets, policy, and traces across clients, whereas PostHog contributes downstream product evidence; adopting both still requires an explicit policy linking those signals to agent authority.

## Context Map

- Layer: tools
- Domains: coding, data
- Topics: observability, mcp, coding-agents

## Uncertainty

- The hobby deployment is unsupported, recommends **4GB memory**, and is intended for roughly **100k events per month** before migration to PostHog Cloud is advised. The ee directory also has separate licensing.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.