PostHog Session Replays in Every Bug Report
Callout auto-detects PostHog on your site and attaches session replay links to every bug report. See exactly what the user did before they hit “Report Bug.”
Automatic session
replay detection.
No API keys, no config, no code changes. Callout handles everything.
Callout detects PostHog
When the Callout widget loads, it checks for the PostHog library on the page. If PostHog is present and session replay is enabled, Callout reads the current session ID automatically.
Session ID captured
Callout captures the active PostHog session ID at the moment the user submits a bug report. This ensures the replay link points to the exact session where the bug occurred.
Replay link in the issue
The session replay link is included in the GitHub Issue alongside the annotated screenshot, console errors, and device details. Click it to jump straight into the PostHog replay.
The complete picture
of every bug.
Screenshots tell you what happened. Replays tell you how it happened.
Screenshots + Replays
A screenshot shows the broken state. A session replay shows the sequence of actions that led to it. Together, they eliminate guesswork and back-and-forth with reporters.
Console Errors + Context
Console errors pinpoint the technical failure. Combined with device details and the page URL, your team can reproduce the bug on the first try instead of asking for more information.
No Manual Linking
Without Callout, developers have to manually search PostHog for the right session. Callout attaches the direct replay link automatically — saving minutes per bug report.
Faster Resolution
Teams using session replays alongside annotated screenshots resolve bugs faster because they start with full context. No clarification needed, no reproduction steps missing.
Not just PostHog.
Callout auto-detects all major session replay tools. Zero config for all of them.
PostHog
Auto-detected session replay links
LogRocket
Auto-detected session replay links
Hotjar
Auto-detected session replay links
FullStory
Auto-detected session replay links
Common
questions.
Does Callout require any PostHog configuration?
No. Callout automatically detects PostHog on the page and captures the current session ID. There is no configuration, API key, or setup step required. If PostHog is running, Callout will find it and attach the replay link.
What does the session replay link look like in a bug report?
Callout generates a direct link to the PostHog session replay for the current session. The link is included in the GitHub Issue body alongside the annotated screenshot, console errors, and device details. Click it to jump straight to the replay in PostHog.
Does Callout work with other session replay tools besides PostHog?
Yes. Callout auto-detects PostHog, LogRocket, Hotjar, and FullStory. If any of these tools are running on the page, Callout captures the session ID and generates a replay link automatically. No configuration needed for any of them.
Do I need PostHog Session Replay enabled for this to work?
Yes. PostHog Session Replay must be enabled in your PostHog project for Callout to capture a replay link. Callout detects the PostHog library and reads the current session ID, which requires an active recording session. If session replay is disabled, Callout will still capture all other details like screenshots, console errors, and device information.
Get session replays in every bug report
Free forever. Auto-detected. Zero configuration required.
Get Started Free