## Problem
previosuly if you shared a video via copy/paste URL, if that same video wasnt loaded on the first page when you later tried to click that URL, it would show "no recording selected".
## Changes
now, if theres a sessionId included in the params, fetch that in ADDITION to the first page of results.
We briefly discussed tracking page number or cursor, however, i think this isnt a good idea as cursor values can change (ie, if sorting by clicks, the sort/ranking of videos with most clicks change over time which changes the first page)
## How did you test this code?
Before (no video found)
[before_url_didnt_work.mov <span class="graphite__hidden">(uploaded via Graphite)</span> <img class="graphite__hidden" src="https://app.graphite.com/user-attachments/thumbnails/6592dcd9-be76-4e18-be5d-95189dd5b642.mov" />](https://app.graphite.com/user-attachments/video/6592dcd9-be76-4e18-be5d-95189dd5b642.mov)
After (hurray)
[loads_video_from_url.mov <span class="graphite__hidden">(uploaded via Graphite)</span> <img class="graphite__hidden" src="https://app.graphite.com/user-attachments/thumbnails/f7364532-588f-4946-bb2e-1f528efd7edd.mov" />](https://app.graphite.com/user-attachments/video/f7364532-588f-4946-bb2e-1f528efd7edd.mov)
👉 _Stay up-to-date with [PostHog coding conventions](https://posthog.com/docs/contribute/coding-conventions) for a smoother review._
## Changelog: (features only) Is this feature complete?
<!-- Yes if this is okay to go in the changelog. No if it's still hidden behind a feature flag, or part of a feature that's not complete yet, etc. -->
<!-- Removing this section does not mean the changelog bot won't pick it up, because *some people* like to not use the template, so we can't rely on it existing. -->
## Problem
This PR makes it possible to use the FF tool directly on the experiments page, since we have removed navigation.
It also adds suggestion pills for FF and experiments.
## Changes
- Added suggestions for feature flags and experiments
- Added the feature flag creation tool to the experiments page so users can create flags without navigating away
## How did you test this code?
Tests + locally
## Problem
we shipped it, delete the dead code
## Changes
<!-- If there are frontend changes, please include screenshots. -->
<!-- If a reference design was involved, include a link to the relevant Figma frame! -->
## How did you test this code?
<!-- Briefly describe the steps you took. -->
<!-- Include automated tests if possible, otherwise describe the manual testing routine. -->
<!-- Docs reminder: If this change requires updated docs, please do that! Engineers are the primary people responsible for their documentation. 🙌 -->
👉 _Stay up-to-date with [PostHog coding conventions](https://posthog.com/docs/contribute/coding-conventions) for a smoother review._
## Changelog: (features only) Is this feature complete?
<!-- Yes if this is okay to go in the changelog. No if it's still hidden behind a feature flag, or part of a feature that's not complete yet, etc. -->
<!-- Removing this section does not mean the changelog bot won't pick it up, because *some people* like to not use the template, so we can't rely on it existing. -->
## Problem
This PR introduces a new `MaxTool` to create experiments. It builds on top of the `create_feature_flag` `MaxTool` with multivariate flag support.
## Changes
- Added a new `CreateExperimentTool` that allows creating experiments via PostHog AI
## How did you test this code?
New tests + evals
## Changelog: (features only) Is this feature complete?
Yes, this feature is complete and ready to be included in the changelog.
Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
when putting a view recording button in the page we pass a status from the event that we're linking from
if the status is buffering we show the button as enabled
this makes sense since we don't know there will be no recording
but
it may be that session is buffering waiting for a trigger that it never sees, and so you click through and get not found
confusion!
despair!
bad UX!
the button already has the concept of a warning
so, let's add a warning that the recording was buffering and _might_ be watchable
## Problem
<!-- Who are we building for, what are their needs, why is this important? -->
<!-- Does this fix an issue? Uncomment the line below with the issue ID to automatically close it when merged -->
<!-- Closes #ISSUE_ID -->
Annoying to have to go for curl or Bruno to run the endpoint :)
## Changes
<!-- If there are frontend changes, please include screenshots. -->
<!-- If a reference design was involved, include a link to the relevant Figma frame! -->
## How did you test this code?
<!-- Briefly describe the steps you took. -->
<!-- Include automated tests if possible, otherwise describe the manual testing routine. -->
- locally 👁️👁️
<!-- Docs reminder: If this change requires updated docs, please do that! Engineers are the primary people responsible for their documentation. 🙌 -->
👉 _Stay up-to-date with [PostHog coding conventions](https://posthog.com/docs/contribute/coding-conventions) for a smoother review._
## Changelog: (features only) Is this feature complete?
<!-- Yes if this is okay to go in the changelog. No if it's still hidden behind a feature flag, or part of a feature that's not complete yet, etc. -->
<!-- Removing this section does not mean the changelog bot won't pick it up, because *some people* like to not use the template, so we can't rely on it existing. -->
nope
