All resourcesPostHog × Replicas

How to build a PostHog AI product analyst cloud agent with Replicas

Give a Replicas cloud coding agent access to PostHog and your repository. It can investigate product behavior, trace the relevant code, make a change, run checks, and return a reviewable pull request or technical report.

A coding agent with product context, not another analytics dashboard.

One continuous run

From a dropped funnel
to a reviewable pull request

A Replicas workspace holding the agent chat, the diff it wrote, the changed files, and its terminal.

Definition

What is a PostHog AI product analyst?

A PostHog AI product analyst is a cloud coding agent that uses product analytics as engineering context. It can inspect PostHog projects, events, insights, dashboards, feature flags, and recordings, then connect that evidence to the repository where the product behavior is implemented.

Replicas remains a coding agent throughout the workflow. The goal is not another dashboard summary. The goal is a verified code change, a pull request, or a technical investigation that tells an engineer exactly what to do next.

What users did

Events, funnels, dashboards, feature flags, and session recordings from the connected project.

Why it happened

The route, component, handler, or flag in the repository that produced that behavior.

Workflow

From product signal to reviewable software work

Product analytics explains what users did. The codebase explains why the product behaved that way. A coding agent can work across both sides of that boundary.

01

Start with a product question

Ask why a funnel step dropped, where users get stuck, whether an experiment changed behavior, or which feature path needs investigation.

02

Inspect PostHog evidence

The agent queries the connected PostHog account for the relevant events, insights, dashboards, flags, or recordings available to it.

03

Trace behavior into code

Replicas searches the repository for the routes, components, handlers, analytics events, and feature-flag logic behind the signal.

04

Change and verify

When the evidence supports a fix, the agent edits the code, runs the relevant checks, and returns a pull request. Otherwise it returns a technical report with its evidence and next steps.

Engineering jobs

What can a PostHog coding agent work on?

The best tasks begin with a specific product signal and end with an engineering output that a human can review.

01

Conversion drops

Investigate a funnel step that fell and identify the responsible product flow and code path.

02

Rage clicks and dead ends

Trace repeated clicks or abandoned sessions to a confusing or broken interface.

03

Experiment cleanup

Compare results, inspect the feature-flag implementation, and prepare the winning cleanup change.

04

Instrumentation gaps

Audit missing or inconsistent analytics events and fix the instrumentation in the repository.

05

Post-deploy regressions

Explain an unexpected behavior change after a deployment and prepare a targeted fix.

06

Inconclusive evidence

Return a technical report instead of a change when the evidence does not justify touching code yet.

FAQ

Using PostHog with a coding agent

With the PostHog plugin installed, an agent can inspect projects, events, insights, dashboards, feature flags, and session recordings available to the connected account.