Demo chat
← All resources

GUIDE / AGENTS AND THEIR ARCHITECTURE

Murphy Knows Your Users Better Than You Do.

A Prosus engineering article explains how Murphy turns product session data into behavioral personas for browser based agent evaluation.

Maintained in JetskibayPublic information
Three phase diagram showing discovery of behavioral traits from user sessions, scoring of sessions, and clustering into personas
Overview

Murphy Knows Your Users Better Than You Do

This Prosus AI Tech Blog article is for product teams and agent engineers who want browser tests to reflect observed user behavior. Murphy is an open source website evaluation agent that explores a site, creates test scenarios, executes them in a browser, and asks a separate model to judge outcomes. The article focuses on replacing preset test personas with profiles derived from product analytics.

The proposed pipeline has three stages. First, it condenses PostHog sessions into behavioral timelines, asks a model for open ended observations, then groups those observations into trait dimensions. Next, it scores another set of sessions against those dimensions. Finally, it clusters the score vectors into personas with instructions for the browser agent and questions for the judge. The article also describes comparing Murphy's test traces with the real session clusters to see where the simulated behavior drifts. Its pipeline diagram gives a quick map of the architecture.

To explore the implementation, start with the repository README. It documents local setup with Python, uv, Chromium, and an LLM provider key. A basic run targets a site with uv run murphy --url https://example.com; the generated plan pauses for review before execution. Persona discovery is an optional --discover-personas mode and requires PostHog credentials and compatible event data. Use the article to understand the research design, then inspect the repository before applying it to your own product.

These personas are behavioral approximations, not representatives who can explain their intent. The author reports that fidelity weakened on more complex goals, so check the action trace and judge rationale before treating a pass or failure as a user finding. The article says sensitive fields are removed before model analysis; teams should still verify their own event collection, filtering, and access controls.

Example use cases

  • Suggested application — onboarding review: Discover patterns such as hesitation or repeated backtracking, then test whether an agent following that pattern can finish sign up.
  • Suggested application — abandonment testing: Ask a persona to leave a checkout or creation flow midway and inspect saved state and recovery cues.
  • Suggested application — evaluation audit: Compare an agent's actions with the session cluster it was assigned, and flag tests whose behavior diverges before using their verdicts.

Sources

Source image: Kevin Ngo / Prosus AI Tech Blog.

Maintained by Jetskibay. Reviewed 2026-09-29T00:00:00Z.

if you liked this…

Follow the trail.

  1. Read nextAssistant BenchmarkA public, evidence-linked scorecard for comparing textable assistants on real-world tasks and examining how they handle online workflows.
  2. Use nextwappCreate on-demand WhatsApp assistants, share pairing codes, and manage their activity through MCP.
  3. See nextSlidesA presentation workspace that brings your slide brief and visual editor together.