Skip to content
Recued
Menu
← Back to recipes

Browserbase context upload intake

by recued-core v1

Approval-gated Browserbase context setup workflow. It creates one context upload slot for a project and summarizes the returned upload and encryption metadata. It never uploads user-data directories, updates contexts, deletes contexts, starts sessions, creates proxies, or calls arbitrary Browserbase routes.

How it works 3 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (3 steps)
context_upload ?
summarize ?
card to_summary
Format results as a summary card
Settings 4 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize the Browserbase context upload slot, encryption fields, and the setup follow-up. Use only the Browserbase response.
max length setting = 600
project id setting =
browserbase setting =

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

Read your Browserbase connection
Declared by the recipe — Recued grants these at install, where you review them before approving.

About

Tags

browserbase browserbasecontextsbrowser-environmentupload-intakeautomation-setuppack:browserbase

Details

3 steps 4 configurable settings recipe_id: browserbase-context-upload-intake