Jev directory
CommunityJev Tools & CLIs
Jev DevTools
npm package (v0.5.4) pairing a React drawer with a Node server adapter that inspects TypeSafe Jev requests, showing request history, context, questions, typed answers, transport attempts, and raw snapshots.
- Reading time
- 2 min
- Published by
- Community
- Added
- Oct 2026
Highlights
- Package version 0.5.4, marked experimental pre-1.0 with APIs that may change before 1.0.
- Requires React and React DOM 18.x or 19.x, Node 22.12+, TypeSafe SDK 0.7.x, and TypeScript 5.4+.
- The React drawer subscribes over same-origin SSE, receiving an initial snapshot then changed traces.
- History is bounded to 50 calls in memory by default; only calls through the instrumented client are captured.
- API keys stay server-side, and known credential fields are always redacted from DevTools captures.
Questions about this entry
Short answers drawn from the linked project or page.
Install from npm with pnpm add jev-devtools @typesafe-ai/sdk using ESM imports. Mount the JevDevtools React component once at the root and create a shared Node adapter with createJevDevtools; React and React DOM are required peers even for server-only installs.
React and React DOM 18.x or 19.x, Node 22.12+, and TypeSafe SDK 0.7.x. TypeScript consumers need 5.4+ plus compatible React and Node types. The /server and /flow entry points run only on Node.
API keys remain server-side. Captures include bounded and redacted context and answers, not hidden model reasoning, and known credential fields are always redacted. An optional prop controls display-only masking of email, phone, postal address, SSN, and card-number fields.
History is bounded to 50 calls in memory by default. Only calls made through the instrumented client created by the DevTools adapter are captured, so other clients in the same app are not shown.
Live calls require a Node backend. Browser-only applications can instead point at a local Vite sample server, and the setup skill includes no-key sample verification so the drawer can be exercised without real inference.
API routes and inspector endpoints must share one adapter instance; distributed processes and edge runtimes are not supported. Without an authorize option the middleware accepts only loopback connections, and Web Request handlers must run on 127.0.0.1.
Yes. A version-matched setup-jev-devtools SKILL.md ships inside node_modules and covers React/Node/Vite and Next.js App Router wiring, including server capture, root drawer mounting, and troubleshooting, readable by agents without web access.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: Text-to-screenshot (Malay Vasa)
X: Google's MediaPipe Decision Maker, tested in the browser
X: Playwright CLI + Jev vs Playwright MCP
X: jev-ultrafast splits every browser decision into operation, target and value. JEV passed 18,000 stars in its…
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.