> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corbado.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Corbado Observe Debugger

> Inspect the live Corbado Observe event stream, session ID and user references with the Corbado Observe Debugger extension for Chrome DevTools.

[**Corbado Observe Debugger**](https://chromewebstore.google.com/detail/corbado-observe-debugger/jgdklbfboneaminmclgacnhocbecibhl) is a Chrome DevTools extension: it adds a **Corbado** panel to Chrome DevTools showing exactly what **Corbado Observe** sends from the browser while you use your application. It is the fastest way to verify an integration, because it inspects the outgoing event traffic rather than your code, so it works for both [Autocapture](/corbado-observe/get-started/autocapture) and [custom events](/corbado-observe/get-started/custom-events).

<Note>
  This is a diagnostic tool, not part of your integration: it reads what your own browser sends on the page you have open and collects nothing itself. Nothing needs to be deployed for it, and because it inspects outgoing traffic, it works just as well on your production site as in development. It also runs independently of [`debug: true`](/corbado-observe/get-started/verify#1-the-three-tools), so you can use both in parallel.
</Note>

## 1. What it shows

**Observe Data** gives you the tracking context of the page: the current **session ID** used to correlate one journey, with copy, refresh and reset actions and every **user reference** seen so far with first and last timestamps. Resetting the session starts a clean journey without clearing all browser state.

<Warning>
  The session ID shown here is **Corbado Observe's tracking session ID**, used to correlate the events of one journey. It is not your application's own session, and resetting it has no effect on your users' authentication state.
</Warning>

**Observe Events** is a live, filterable stream:

| Row type     | Content                                                                                                                                                                                                     |
| ------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Events**   | Modeled authentication events with their key fields inline, for example `flow_started flowName=login touchpoint=account_login` or `subflow_step_finished subflowType=password-login stepName=post-response` |
| **Lows**     | Low-level interaction signals such as `focus`, `blur` and `input` with timings                                                                                                                              |
| **Requests** | Which network request each event was delivered in, so you can see batching                                                                                                                                  |

Controls include a free-text filter across name, type and data, chips to show only events or only lows, a recording toggle and a clear action.

## 2. Requirements

| Requirement | Detail                                                                                                                                     |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| Browser     | Google Chrome 102 or later                                                                                                                 |
| DevTools    | Must stay **open** while the page makes requests. The panel only captures network activity while DevTools is attached.                     |
| Page        | Any page sending Corbado Observe events, whether through Autocapture or the SDK. The panel listens for Observe event requests on any host. |

## 3. Install

<Steps>
  <Step title="Get the extension">
    Install [Corbado Observe Debugger](https://chromewebstore.google.com/detail/corbado-observe-debugger/jgdklbfboneaminmclgacnhocbecibhl) from the Chrome Web Store.
  </Step>

  <Step title="Open the panel">
    Open DevTools on your application, with Command-Option-I on macOS or F12 on Windows and Linux, then switch to the **Corbado** tab.
  </Step>
</Steps>

## 4. Typical workflow

Clear the stream, walk one journey from start to finish without navigating away, then read the sequence: it should start with a flow event, contain the subflow steps you expect and end with a finish event. Gaps and duplicates are obvious in the stream.

Then repeat with a deliberate failure, such as cancelling a passkey dialog. Silent cancellations produce no backend request at all, so this is the case worth checking explicitly.

## 5. Next steps

<CardGroup cols={2}>
  <Card title="Verify your integration" icon="circle-check" href="/corbado-observe/get-started/verify">
    The full verification workflow.
  </Card>

  <Card title="Tracking reference" icon="diagram-project" href="/corbado-observe/tracking/overview">
    What the event names and fields mean.
  </Card>
</CardGroup>