Session Replay: make recording-list filter results understandable and reliable
@pauldambra is already working on this.
Since Sep 18, 2026.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Why
People use the Replay list to find a recording to watch. Today, the experience can feel unreliable even when individual filters and recordings are behaving as designed. Existing GitHub issues and internal Support reports describe parts of this; this issue groups them by what people experience.
Experience groups
1. Unexpected recordings in results
“I filtered for X, but these recordings do not look like X.”
Support:
Related GitHub issues:
- #83499
- #33113
2. Expected recordings are missing
“I know this recording exists, but I cannot find it in the list.”
Support:
Related GitHub issues:
- #91388
- #32533
- #55410
3. The same search feels inconsistent
“The same filters give a different-looking answer between people, times, or list states.”
Support:
4. I cannot use the search result
“The search fails, the result does not open, or it does not take me to the moment I need.”
Support:
Related GitHub issue:
- #46077
Scope
This is an experience-level umbrella. It does not assume that the groups have one cause or require one shared solution.
Desired outcome
A person can use Replay search and filters to find a recording to watch, understand the result they receive, and tell when an expected recording is unavailable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.