User repository on GitHub
Local-first macOS coding workspace with local Laya and optional Jev decision selection
- Forks
- 45
- Last pushed
- Updated Sep 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Agents & MCP
Keel
A local-first macOS coding workspace that runs Claude Code, Codex, Cursor, Grok, Hermes, and pi over ACP, with a local Laya or hosted Jev selector choosing routes that the host then validates.
- Stars
- 330
- Language
- Rust
- License
- MIT
- Published by
- Community
- Author
- codejunkie99
- Last verified
- Oct 2026
About this project
A local-first macOS coding workspace. Keel runs the coding agents you already use. A local Laya selector or an optional hosted Jev selector chooses a route. The host checks each choice before Keel applies it. Getting started · Build from source · Architecture · Roadmap · All documentation. Keel 0.2.0 puts the editor workspace, provider connections, task routing, and decision records into one Rust/GPUI app. It uses an Avid-derived interface.
Quoted from the project's README. Read the full README.
Used inJev for Software & DevTools
- Languages
- Rust
Highlights
- Route selection only applies to a fresh, unpinned task; pinned and resumed sessions keep their existing route.
- Every decision leaves a receipt in the transcript, and keel decisions export writes one replay case per receipt as JSONL.
- Needs Apple Silicon and macOS 15 or later for the packaged Laya model, and publishes no downloadable app releases.
- Headless and daemon modes exist through keel headless and keel daemon install, with keel status reporting the saved mode.
Watch out
The README publishes no downloadable app releases and says packages are ad hoc signed development builds without Developer ID signing or notarization. It also states that decision records support evaluation but automatic training is not implemented, and that build checks do not establish better coding outcomes. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
You build from source or use a local development package you already have, because the repository does not currently publish downloadable app releases. The light package fetches Laya only when you choose Download and activate Laya; the full package already contains the pinned checkpoint.
No, and the README says so plainly: a local selector does not mean your coding worker runs locally. Each coding provider keeps its own authentication, model configuration, and tool loop, and external ACP agents keep their own internal loops.
The host validates every choice, and a rejected, stale, or expired choice falls back to the ordinary route. Each decision leaves a bounded receipt recording candidates, result, validation, fallback, and the observed outcome.
Not yet, and the README is candid about it. Automatic training is not implemented, build checks do not establish better coding outcomes, and keel decisions replay, which would run a baseline against a candidate on exported cases, is still on the roadmap.
Exactly one backend runs per decision. Laya is the default local selector, Jev is opt-in and hosted by TypeSafe using an existing protected local credential, and Normal makes no selector call at all, using your ordinary harness route.
No. It applies only to a fresh, unpinned task; pinned routes and live or resumed sessions keep their existing route, and external ACP agents keep their own internal tool loops.
Yes. keel headless runs the engine without a UI and keel daemon install runs it as a service, while keel decisions export writes one replay case per receipt as JSONL and keel decisions report prints counts by backend, stage, validation, and fallback.
More Jev resources like this
235GitHub stars
Rust terminal coding harness with one TUI across local and cloud providers, per-turn cost on the status line, routed plans scored by explicit policy, real undo, and forkable session paths.
Jev Agents & MCP#community#jevbest
Community
morganlinton/AlbatrossRust
morganlinton/AlbatrossRust2GitHub stars
Rust client that lets Jev choose the model and privacy tier for NEAR AI Cloud calls. A client-controlled monthly cap in cents is combined with Jev scores for complexity and sensitivity and nouls for private TEE, risk and urgency, then the NEAR catalog is filtered to what survives that choice.
Jev Agents & MCP#community#jevbest#catalog-import
Community
iJ03l/jearRust
iJ03l/jearRust1.5kGitHub stars
Open-source platform that puts ACP-compatible agents such as Claude Code, Codex, and Pi inside the team's Slack, Telegram, Discord, and GitHub workflows, with reusable Jev decisions for routing, response gating, and reviewer selection.
Jev Agents & MCP#community#jevbest
441GitHub stars
A four-layer agent toolkit for Claude Code, Codex, Factory, and Reasonix: 43 agents, 62 skills, 78 hooks, 147 scripts, and a Jev-backed router that gates dispatch on intent alignment.
Jev Agents & MCP#community#jevbest
Community
notque/vexjoy-agentPython
notque/vexjoy-agentPython488GitHub stars
A coding agent built on pi that hands its non-code decisions — what enters the context, whether a command is safe, whether the work is done — to a small judge model at 35 decision points per turn.
Jev Agents & MCP#community#jevbest
Community
qybaihe/muTypeScript
qybaihe/muTypeScript236GitHub stars
Rust governance kernel that sits between your coding agent and the repository, turning intent into bounded specifications, recorded state, and proof-backed publication across many separate invocations.
Jev Agents & MCP#community#jevbest
Community
DecapodLabs/decapodRust
DecapodLabs/decapodRustFrom the Jev community
Posts from builders shipping with Jev right now.