​
Overview

PlayerZero connects user-facing issues directly to the underlying code by analyzing network calls, error traces, and code context to surface the specific files and functions involved. By leveraging embeddings, PlayerZero matches runtime context with the most relevant parts of the codebase—so technical support can skip the manual investigation and jump straight to fixing the problem. In this guide, we will cover how to initiate the AI chat session from either the single pane of glass debug mode or an externally sourced error, let PlayerZero create a workspace to collate relevant files, and map the specific causal code.

​
Prerequisites

​
Source Control Management (Codebase)

Connect your codebase to PlayerZero enables PlayerZero to map runtime errors, traces, and sessions back to the exact lines of code in your repository.

This is the foundational integration — all other data sources (traces, tickets, sessions) rely on it to establish full context across your stack.

→ To set this up, navigate to the SCM Setup Guide.

​
Web SDK

Instrumenting your frontend with PlayerZero captures user actions, DOM snapshots, and network activity for full-session context. It bridges frontend events with backend telemetry when available.

For complete session capture, ensure that backend telemetry is also connected.

→ To set this up, navigate to the Web SDK Setup Guide.

​
Process

​
Starting from a PlayerZero Debug Session

This workflow starts from the single pane of glass debug mode, where you sourced an error in the DevTools tab that you want to explore. Read the capture session context guide for more details on how PlayerZero creates a workspace from relevant files and maps the specific causal code for deeper debugging.

​
1. Initiate Root-Cause AI Chat

In a specific network call, click “Find in my code.” This will kick off the AI chat experience, and PlayerZero will use not only this specific call but also the entire session to build context around how to locate the responsible code.

​
2. Watch PlayerZero Create the Workspace

PlayerZero will create a new workspace, pulling in all relevant files that it will use to answer the question. These cited sources can range from code files to PR commits made in the past.

​
3. Map the Specific Causal Code

PlayerZero will investigate the responsible code and present a thorough breakdown, using diagrams, markdown, and other explanatory elements that clarify how everything works.

​
Starting from an Externally Source Error

This workflow starts from signals that were captured outside of the PlayerZero Platform, prompting you to initiate the AI chat session, let PlayerZero create a workspace, and finally map the specific causal code for deeper debugging.

​
1. Initiate Root-Cause AI Chat

From the input field on the homepage, copy and paste the relevant error along with any relevant context.

​
2. Watch PlayerZero Create the Workspace

PlayerZero will create a new workspace, pulling in all relevant files that it will use to answer the question. These cited sources can range from code files to PR commits from the past.

​
3. Map the Specific Causal Code

PlayerZero will dig into the responsible code and write out a breakdown, including diagrams, markdown, and anything else that helps clarify how the code works.

​
Summary and Next Steps

By analyzing network calls, error traces, and code context, PlayerZero automatically isolates the root cause behind user-facing issues and removes the need for manual codebase searches. This direct mapping capability delivers immediate insights, allowing engineers to focus on fixes rather than extended discovery.

Generate Code Fixes – Dive deeper into automatically creating targeted patches based on the identified errors.