:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Contributing to PostHog
We love contributions big and small. The PostHog desktop app is the IDE for understanding how users interact with your product -- and we want the community involved in shaping it.
[!NOTE] This code lives at
products/desktopinside posthog/posthog. If you already have that repo checked out, work there instead of cloning separately.
Getting started
- Fork the repo and clone it locally
- Follow the Development setup below
- Create a branch (
feat/my-change,fix/that-bug) - Make your changes and open a pull request
Issues labeled good first issue are a great place to start!
If an issue does not yet exist for your change, please create one first so we can align on the approach before you invest time.
Development setup
# Prerequisites: Node.js 22+, pnpm 10.23+
pnpm install
cp .env.example .env
pnpm dev
See docs/LOCAL-DEVELOPMENT.md for connecting to a local PostHog instance.
Before submitting
- Run
pnpm typecheck,pnpm lintandpnpm testlocally - Resolve merge conflicts before requesting review
- Keep changes focused -- one logical change per PR
- Add tests where they meaningfully improve confidence
- Follow existing patterns and conventions in the areas you touch (see AGENTS.md for architecture rules and code style)
What to expect
- PRs are triaged and assigned to the relevant team
- Expect acknowledgement within a few days. Thorough reviews may take longer depending on load
- We sometimes close PRs that are out of scope or would add long-term maintenance burden. You're always welcome to reopen with updates
Issues
Spotted a bug? Something broken? Raise an issue for the fastest response.
Feature requests
Request features on our public roadmap. Give us as much context on the why as possible -- we love hearing about the problem you're trying to solve.
If you're unsure whether something fits, open an issue first and we'll get back to you quickly.