Jev directory
CommunityJev Tools & CLIs
Jev Fabric
Single native executable that runs and supervises child processes and asks Jev a typed question only when instructed. Written in Bend, installed by curl script or npm, with no Node, Python or daemon at runtime.
- Reading time
- 2 min
- Published by
- Community
- Added
- Oct 2026
Highlights
- One binary owns process groups, deadlines, bounded logs and durable job records.
- Releases ship a macOS universal binary plus Linux x64 and arm64 builds, checksum-verified by the installer.
- Jev questions are limited to choice, noul and score; the typed answer feeds a branch you already wrote.
- Receipts keep 32 KiB tails, spools keep the first 1 MiB per stream and jobs keep their latest 64 events.
- Default timeouts: one hour for work, 30 s for Jev, wait and follow, and 5 s for watch.
Questions about this entry
Short answers drawn from the linked project or page.
The install script at the project's GitHub repository pipes to sh, verifies SHA256SUMS and places the binary in ~/.local/bin. Alternatively npx jev-fabric or npm install -g jev-fabric installs only the matching platform package, with no install-time download.
No. jev-fabric is a native executable written in Bend and the documentation states no Node, Python or daemon runs at runtime. Building from source requires Bend 2.0.38, Clang and Bun, which is used for a build-time safety gate.
Paste the documented instruction block into Codex, Claude Code or another coding agent: it installs the checksum-verified release, adds the skill with npx skills add fabric-runtime/jev-fabric, and proves the binary runs with jev-fabric -- exec /bin/echo ready.
Work defaults to one hour, Jev calls to 30 s, wait and follow to 30 s and watch to 5 s. Override per call with --timeout-ms N, or set JEV_FABRIC_TIMEOUT_MS, JEV_FABRIC_JEV_TIMEOUT_MS, JEV_FABRIC_WAIT_MS and JEV_FABRIC_WATCH_MS.
Receipts keep 32 KiB tails, spools keep the first 1 MiB per stream and each job keeps its latest 64 events. Losses are disclosed rather than silently dropped, for example through a follow.loss record during event streaming.
Releases ship a macOS universal binary and Linux x64 and arm64 binaries; the Linux builds need glibc 2.28 or newer. From npm, only the matching jev-fabric-darwin, jev-fabric-linux-x64 or jev-fabric-linux-arm64 package is installed.
Yes. Any process sharing a storage root, set by JEV_FABRIC_HOME or by .jev-fabric-native/ in the working directory, can list jobs, follow one as it runs, or pick it up after a restart. A root written by a newer store format is refused, never rewritten.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
YouTube: Ray Amjad puts Jev inside an agentic coding loop and looks at what it costs to run.
YouTube: RoboNuggets puts Jev to work inside Claude Code.
X: Decision outputs in Grep
Hacker News: jevmem keeps Claude Code project memory by asking Jev which turns are worth saving.
avinashjetwani61 pointsJevmem – automatic project memory for Claude Code, built on JevRead the thread on Hacker NewsFrom 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.