Loading video...

Video Failed to Load

Go Home

Jev + Vercel Sandbox Mod in Claude Code This Mod spins up a sandbox on Vercel, while Jev classifies which commands should run inside the sandbox and which ones should run locally Install: npx claude-code-templates@latest --mod security/jev-vercel-sandbox Link: Mods are a great way to customize your Claude Code workflows...

16,889 views • 5 days ago •via X (Twitter)

10 Comments

Sebastian Hardy's profile picture
Sebastian Hardy5 days ago

Full shell access on day one is how agents wipe folders.

Bessi S's profile picture
Bessi S4 days ago

Jev classifying sandbox vs local.

Anishek Kamal's profile picture
Anishek Kamal5 days ago

Splitting what runs in a sandbox versus locally based on command risk is a nice pattern. Saves you from sandboxing everything just to be safe.

Richard E. Greene's profile picture
Richard E. Greene4 days ago

claude code getting a whole sandbox mod is kinda sick

David Qu's profile picture
David Qu5 days ago

Keeping the bulk edits in a separate patch is useful when you've already got uncommitted work. Way easier to tell what the agent actually changed

Lee Wyatt Corp's profile picture
Lee Wyatt Corp5 days ago

A Jev sandbox mod on day one. The ecosystem is not waiting around.

Kizuno18's profile picture
Kizuno185 days ago

dynamic command routing between local and sandbox is the cleanest security pattern: isolating only risky commands preserves local speed. in our pipeline targeting brazil, classifiers route untrusted fetches to sandboxes while ffmpeg and piper run on bare metal for $0. fast & safe

Shahid🇵🇸's profile picture
Shahid🇵🇸5 days ago

read the page. a default i'd flip: with confirmSandbox on, a claude -p run has nobody to answer, so even untrusted_code (curl | sh) falls through to local. headless runs are where nobody reads the command, so that case should go to the sandbox

TobiasJames.ΞTH ᵍᵐ's profile picture
TobiasJames.ΞTH ᵍᵐ5 days ago

Oh that’s sick

Michael Waitze's profile picture
Michael Waitze5 days ago

This is a clever way to use Jev for security. We actually went deeper on the Cloudflare Clef models that are also pushing the boundaries of decision models here:

Related Videos

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

202,492 views • 15 days ago

how to use claude code mods like a top 1% user, step by step: give this to your agent before everyone catches on👇 1. set up Jev connect Jev to the model registry you want to use. check that the connection works and the listed models are available. 2. build your claude code mod open claude code 2.1.287 or later and paste this prompt: “build a mod called run-ledger. load plugin-authoring and use the API types for my installed version. create a dashboard that shows: - estimated cost per run, model, and source plugin where known - which model handles each task - each subagent’s status, latest action, and elapsed time include token counts, cache usage, and reported retries. count each request once. keep background tasks linked to their original run. use dated prices. label costs as API estimates, not subscription charges. show unknown when data is missing. connect the mod to my existing Jev setup. give Jev the task, available models, prices, budget, and relevant past results. ask it to recommend a model and explain why. start with recommendations. make automatic routing optional for eligible subagents. show the recommended model, actual model, result, and cost. include Jev’s own cost. keep state across hot reloads. add details and export. the dashboard itself must make no model calls. validate the plugin. test rendering, costs, attribution, and duplicate counting. give me steps for a live test.” 3. test the setup allow hot reload when prompted. run a simple task, a subagent task, and a mod-triggered model call. check that the dashboard updates, each request counts once, and Jev’s recommended model can actually run the task. 4. install the working mod ask claude to copy it out of the temporary folder and install it as a persistent plugin. see the cost. choose the model. check the result.

Avid

47,276 views • 4 days ago