You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Open the Playground at a given session from the URL (?playground=true&session=<id>) #15747
session=<session-id> selects that session, if it exists for the flow; otherwise the Playground opens as usual.
#7270 already syncs the Playground modal with a URL parameter, so this could extend it with session. The /playground/<id>/ shareable page doesn't cover this: it needs the flow to be public and starts a new chat.
Motivation
External tools that run flows through the API can pass a session_id per run, and Langflow stores each run as its own Playground session. But there is no way to link from outside to that session: a user who follows a link to the flow (/flow/<flow-id>) has to open the Playground and look for the right session by hand, which is slow and error-prone when a flow has many sessions.
Our use case: we orchestrate workflows with LangGraph, and each workflow step calls a Langflow flow through /api/v1/run/<flow> with session_id set to the workflow run's id. Our UI shows the run and links each step to its flow. With this feature the link would open the exact conversation for that run.
Build on feat: add url parameter to playground modal #7270 (credit to @suwonthugger): keep the Playground's open state in the URL as ?playground=true. When it's closed, remove the parameter rather than leaving playground=false, and keep the fix that stops the unsaved-changes guard from firing when only the parameter changes.
Add session=<id>. When it names one of the flow's sessions, the Playground opens with that session selected; otherwise it opens as usual.
Target release-1.13.0, with a test for both parameters.
Would a PR along these lines be welcome? If #7270's author would rather carry it forward, I'm happy to leave it to them and help test instead.
Activity
seymurasadov commentedon Oct 14, 2026
I'd like to implement this. My plan:
?playground=true. When it's closed, remove the parameter rather than leavingplayground=false, and keep the fix that stops the unsaved-changes guard from firing when only the parameter changes.session=<id>. When it names one of the flow's sessions, the Playground opens with that session selected; otherwise it opens as usual.release-1.13.0, with a test for both parameters.Would a PR along these lines be welcome? If #7270's author would rather carry it forward, I'm happy to leave it to them and help test instead.