Organization repository on GitHub
Repo-native governance kernel for bounded, convergent, proof-backed agent work.
- Forks
- 23
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.Homepage
CommunityJev Agents & MCP
Decapod
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.
- Stars
- 236
- Language
- Rust
- License
- MIT
- Published by
- Community
- Author
- DecapodLabs
- Last verified
- Oct 2026
About this project
cargo binstall decapod && decapod init. Decapod Repo-native governance kernel for bounded, provable, shippable AI coding work. Work in Cursor, Claude Code, Codex, Antigravity, Grok, or any harness you prefer. Decapod governs the work without replacing the agent or its harness. One command installs the kernel. One command prepares the repository. You keep speaking naturally. Agents call Decapod at the points that matter: before acting, before inference, at validation boundaries, and before publication.
Quoted from the project's README. Read the full README.
Used inJev for Software & DevTools
- Languages
- Rust
Highlights
- No daemon by design: every CLI or RPC invocation is ephemeral and durable execution state lives in `.decapod/` inside the repository.
- Optionally asks Jev one bounded question during `assurance.evaluate`, whether the trajectory meets the declared intent, and records a typed probability.
- The provider is off by default, and unavailable, unconfigured, timed-out, or invalid responses record `no_observation` and leave the governance rules unchanged.
- Each assurance result, failed observations included, appends to `.decapod/governance/jev.json`, which is validated before publication and committed with the PR.
Watch out
MIT licensed and written in Rust. The Jev path is optional and adds a network call plus token spend on every assurance evaluation, and its usefulness is unquantified: the README documents the wiring but no measurement of how well the returned probability tracks real intent. The live evaluation corpus is opt-in and asserts no threshold. 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.
Only a typed probability on one bounded question, never prose and never an approval. Decapod remains the authority for boundaries, interlocks, policy, and completion, and a failed or invalid call records `no_observation` rather than changing any of those rules.
No. Normal local operation does not need Jev, a network, or a key. You opt in by setting the decision provider to jev in `.decapod/config.toml`, and the key is read from `TYPESAFE_API_KEY` in the machine environment rather than committed to that file.
No. It is explicitly not an agent, model, orchestration framework, daemon, prompt library, coding assistant, project-management system, or harness replacement. It governs work an agent performs, so you keep using Cursor, Claude Code, Codex, or whatever you already run, and the repository preserves state across harnesses.
Each assurance call appends its typed result to `.decapod/governance/jev.json`, keyed by the active trajectory run, validated before publication, and committed with the PR so the full history is recoverable through Git. Starting a new trajectory run clears the working-tree ledger but leaves the committed history intact.
cargo binstall decapod, then decapod init. One command installs the kernel from crates.io and one prepares the repository. Decapod deliberately runs without a daemon: each CLI or RPC invocation is ephemeral and durable state lives in the repository, with agents calling it before acting, before inference, at validation boundaries and before publication.
decapod init --refresh reopens the initialization questionnaire with your current configuration as the defaults; press Enter to keep a value or pick a different option, including the decision provider. It preserves repository state and does not need --force, only an existing .decapod setup. In a non-terminal environment it keeps the current configuration without prompting at all.
Yes, and it is deliberately developer-only. DECAPOD_RUN_JEV_EVAL=1 with a key runs cargo test --test decision_provider_live -- --ignored --nocapture, emitting one machine-readable JSON record per case with the human expectation, observation status, probability, latency and token usage where available. It asserts no threshold and does not affect ordinary tests or CI.
More Jev resources like this
330GitHub stars
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.
Jev Agents & MCP#community#jevbest
Community
codejunkie99/keelRust
codejunkie99/keelRust235GitHub 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/AlbatrossRust112GitHub stars
Rust CLI that searches a live source tree by describing what you want, returning files and line ranges with calibrated probabilities instead of building an index.
Jev Agents & MCP#community#jevbest
Community
can1357/jegrepRust
can1357/jegrepRust35GitHub stars
Rust terminal tool that asks Jev noul, choice and score questions about piped text or files and returns calibrated probabilities with stable exit codes for shell scripts, CI jobs and agents.
Jev Agents & MCP#community#jevbest#catalog-import
Community
shaharia-lab/jev-cliRust
shaharia-lab/jev-cliRust12GitHub stars
Single-binary linter whose YAML rules are plain-language questions sent to the Jev model as yes-no judgments with probabilities, fitting CI jobs and pre-commit hooks.
Jev Agents & MCP#community#jevbest#catalog-import
Community
virolea/lintusRust
virolea/lintusRust17GitHub stars
Command Code mod that asks Jev at every agent stop whether a nudge would help, continuing unfinished work while leaving waits for the user alone.
Jev Agents & MCP#community#jevbest#catalog-import
From the Jev community
Posts from builders shipping with Jev right now.