PostHog / PostHog/posthog

On the session recording interface do not automatically start the next recording when one is played through

Open
#61,349 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Feature request

Is your feature request related to a problem?

Moving around in large recordings is generally slow. If you are trying to seek to a point close to the end of a 3 hour recording, then you will load for 10s of seconds. Seeking is also imprecise and it frequently happens that I'm trying to seek, it loads then I'm very quickly moved to the next recording, which unloads all context for the recording I'm trying to seek in.

If the recording I jump to is also large, that is an other extra loader and freeze.

Describe the solution you'd like

I'd like the session recording screen to not autoplay through multiple recordings, only the one I click on. Then I can still seek on the bottom and scroll through the events on the right side even if the recording just finished.

I have no use for autoplaying all recordings but I imagine some users do, so maybe this could be a setting on the screen, but I think it should be the default.

Describe alternatives you've considered

A general performance improvement would also greatly mitigate the issue, but I imagine that to be a much bigger technological challenge.

Additional context

Good product <3

Debug info
- [x] PostHog Cloud, Debug information: Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019e8cf4-83ad-7c63-92aa-467152b39c2c?t=1304
Admin (internal): http://go/adminOrgUS/0197c573-65ee-0000-0774-2c412ab3b29a (project ID 189259)
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a file or test; start by locating the session recording screen and its playback-completion handling. Verify the current behavior with multiple recordings, then confirm that playback stops after the selected recording while seeking and event browsing remain available after it ends.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.