Repository navigation
list_recordings
Kelly Ferrone edited this page Oct 10, 2026
·
3 revisions
This workspace's recordings, not yet kept.
| MCP resource | workspace://files/recordings |
| HTTP | GET /files/recordings |
Newest first. One video per browser opened with record=true, filed shortly after it ended. Works after the browser is gone.
This action takes no parameters.
Every call names its workspace: an X-Workspace header, or
?workspace=<name>. Sending both is refused. See Workspaces.
| Field | Type | Notes |
|---|---|---|
workspace |
string | |
folder |
string | |
uri |
string | |
count |
integer | |
browser |
boolean | Present on downloads only: whether a browser is open to read them from. |
files |
array |
| Status | Means |
|---|---|
400 |
The request cannot succeed as sent — an unusable name, or a server with no DATA_DIR to keep files in. Do not retry it unchanged. |
401 |
Missing or wrong bearer token. |
404 |
No such browser session, or no such file in it. It ended, the Grid reaped it, or the id was never real. |
500 |
Something failed that this server did not expect. |
503 |
The Grid could not serve this — unreachable, or failing. Worth retrying after a wait. |
Over MCP the same failures arrive as a tool error.
MCP
read workspace://files/recordings
read_resource(uri="workspace://files/recordings")
HTTP
curl -X GET $SELENIUM_FLOW/files/recordings \
-H "Authorization: Bearer $TOKEN" \
-H "X-Workspace: $WORKSPACE"The action pages are generated from openapi.yaml, which is itself generated from the live MCP tool schemas — so they describe the server that shipped, not the one someone remembered. Prose belongs in wiki-notes/<tool>.md in the repo.
selenium-flow · MIT
Start here
Guides
Lifecycle
Going places
Doing things
Getting things out
Site data
Console and network