Skip to content
HedronitePublic

About

Bezel is a harness agnostic supplemental overlay. Jev integration, bend2 planned. current status prototype, will be written in Rust after PoC

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Bezel

Bezel product lockup

A harness overlay: skills, a Jev toolkit, and adapters.
a Hedronite setting.

CI MIT license Nix Node

What Bezel is · Quick start · Packages · Names · Jev · Skills · Platforms · Status · Contributing


Bezel supplements an agent harness you already run with skills, a Jev toolkit, and gate adapters. You keep the harness. This repository does not include harness source.

What Bezel is

Bezel is the supplement, not the harness. It ships the suite in one Nix flake: skills, the Jev toolkit, and adapters that call that toolkit.

Piece What you get
Skills Flake input inputs.skills (.agents/skills/). Each skill is a directory with SKILL.md. Lapis, Facet, Geode, and Phantom default to that skill plus the CLI. Home Manager copies each skill directory as regular files into the user directory each harness reads.
Jev jev-router asks Typesafe for one policy decision and prints one JSON verdict. Shadow, the default, logs the verdict and does not block.
Toolkit jev-router --catalog prints a small tool index. --schema NAME prints one JSON Schema. Reading a schema does not allow the tool. --check is a shadow diff check.
Cursor cursor-agent-jev runs the gate, then execs cursor-agent.
Grok Build grok-build-jev is the PreToolUse adapter. It calls jev-router and prints defer or deny. It does not install a host hook.
omp, optional Package bezel installs bezel-omp, which runs upstream omp from PATH or $OMP_BIN with Bezel's omp config overlay, so a one-line JSON skill reply is not cut. bezel-pinned points that same wrap at a fetched release binary. omapi is a symlink to bezel-omp for one release.

Bend2 is a later engine. It is not in this tree. The Jev router is still JavaScript. A Rust rewrite is a later phase.

Use overlays.default, homeManagerModules.default, or packages.<system>.*.

Quick start

From a clone:

nix build .#bezel
nix build .#jev-router
nix build .#cursor-agent-jev
nix build .#grok-build-jev

bezel-omp runs omp from PATH or $OMP_BIN. If neither is present, it exits 127 and prints how to fix that. The package attribute is bezel. The binary is not named bezel.

The pinned oh-my-pi v18.2.6 binary is opt-in (~180–240 MB):

nix build .#bezel-pinned

Flake input (Home Manager)

The product name is Bezel. The repository is VirtualMachinist/bezel. An input that still says omapi-overlay follows GitHub's redirect.

{
  inputs.bezel.url = "github:VirtualMachinist/bezel";
}

{
  nixpkgs.overlays = [ inputs.bezel.overlays.default ];
  home-manager.users.you = {
    imports = [ inputs.bezel.homeManagerModules.default ];
    programs.bezel.enable = true;
  };
}

programs.bezel.enable installs bezel (bezel-omp), jev-router, cursor-agent-jev, and grok-build-jev. It copies each skill directory as regular files into ~/.agents/skills, ~/.claude/skills, ~/.grok/skills, and ~/.cursor/skills. programs.omapi is deprecated; it renames to programs.bezel.

Packages

Package What it is
bezel Installs bezel-omp, which runs host omp or $OMP_BIN. Exits 127 if neither exists. Also installs omapi as a symlink to bezel-omp for one release, and the omp overlay (see below).
bezel-pinned Same wrap, pointed at a fetched oh-my-pi v18.2.6 binary.
jev-router Node router. Asks Typesafe for a Choice and prints a JSON verdict. Loop-stop (continue / stop / escalate), jev-router --check for a shadow diff check, shadow permission catalogs, and a small tool catalog (--catalog, --schema NAME).
cursor-agent-jev Runs jev-router, then execs cursor-agent (cursor-agent must already be on PATH). Shadow never blocks. Active honors continue and gate: auto only. --catalog and --schema print and do not exec.
grok-build-jev Grok Build PreToolUse adapter. Calls jev-router and prints defer or deny. Does not install a host hook.
nushell Interpreter for the Lapis, Facet, Geode, and Phantom skill bodies. The version is the nixpkgs pin in flake.lock.

packages.default is bezel.

The omp overlay. bezel and bezel-pinned install share/bezel/omp-overlay.yml, an omp config overlay that sets tools.outputMaxColumns: 8192 and nothing else. By default omp cuts each tool-output line at 768 bytes, so a skill's one-line JSON reply arrives cut off. bezel-omp passes --config=<that file> ahead of your own arguments. A --config you pass yourself comes later and wins. BEZEL_OMP_OVERLAY=0 passes no overlay. scripts/check-omp-overlay.sh checks all three cases against a fake omp.

Names

The flake input and the primary package attribute are bezel. packages.default is bezel.

What Name in this release
Product Bezel
Flake input / package bezel, bezel-pinned
omp wrap binary bezel-omp
omp overlay share/bezel/omp-overlay.yml in bezel and bezel-pinned. BEZEL_OMP_OVERLAY=0 turns it off.
One-release symlink omapi → bezel-omp
Same package attrs .#omapi is bezel. .#omapi-pinned is bezel-pinned.
Jev commands jev-router, cursor-agent-jev, grok-build-jev
Home Manager programs.bezel. programs.omapi is deprecated and renames to programs.bezel.
Skills paths ~/.agents/skills, ~/.claude/skills, ~/.grok/skills, ~/.cursor/skills
Env BEZEL_*. Legacy OMAPI_* is still read. The wrap sets both BEZEL_OVERLAY and OMAPI_OVERLAY. BEZEL_OMP_OVERLAY has no OMAPI_ alias.

Gate version strings stay omapi-loop-stop-policy@1, omapi-check-policy@1, and omapi-route-workflow-policy@1. Those ids are the policy contract. The typed-call host profile id stays omapi-jev-router. Changing either would change verdicts, not the product name. omp-pin and omp-runtime stay those attribute names.

Jev

Jev is a shadow-first policy gate in front of cursor-agent. Shadow logs a decision and does not block. TYPESAFE_API_KEY is runtime-only. Set it in the process environment. The flake does not store it.

# TYPESAFE_API_KEY must already be in the environment
JEV_MODE=shadow cursor-agent-jev "<intent>" -- <cursor-agent args>
Variable Role
JEV_MODE=shadow Default. Log the decision. Always run cursor-agent.
JEV_MODE=active Honor continue / gate: auto only. stop / escalate exit 2 and do not exec.
JEV_BYPASS=1 or true Skip the router and run cursor-agent. Other values (yes, false, 0) are not a bypass.
JEV_ROUTER Override the router binary.
JEV_STEP_DIGEST Optional step digest for the loop-stop decision.
TYPESAFE_API_KEY Runtime only. @typesafe-ai/sdk reads it.

Missing key: shadow continues unclassified. Active stops and waits (escalate / hold).

Loop-stop labels are continue, stop, and escalate, over the intent plus an optional digest. Thresholds live in omapi-loop-stop-policy@1 (conf ≥ 0.6, p ≥ 0.55, margin ≥ 0.15). choice: escalate with gate: hold waits for a person. It does not retry on its own. How to run: docs/SPIKE-loop-stop.md.

Shadow check

jev-router --check reads a git diff, applies an available-gate, asks for a decision, then applies code thresholds. The result is findings, parked, and notChecked. Empty findings are not approval.

JEV_MODE=shadow jev-router --check --intent "<task>"
# or: --diff-file packages/jev-router/testdata/skip-marker.diff

Skill: .agents/skills/check. How to run: docs/SPIKE-stanley.md.

Grok PreToolUse uses the same three policy ids and the same JEV_BYPASS predicate. The tool-class map, matcher (shell, write, and MCP), and the hook checklist are in docs/POLICY-MAP.md. The hook calls jev-router. It is not a second TypeSafe client. Default mode stays shadow.

Shell, write, and MCP also get a permission catalog on those same policy ids (allow → continue, deny → stop, ask → escalate, or the writer parent for writes). It defaults to shadow. Set JEV_PERMISSION_MODE=active only after that surface has been re-checked. JEV_MODE=active does not turn it on. A missing TYPESAFE_API_KEY keeps that surface on shadow. How to run: docs/SPIKE-permission.md.

Tool catalog

Every verdict carries a small tool index (catalog.kind = tiny): class, policy id, and tool names. It does not carry JSON Schema. The wrap copies that index into JEV_TOOL_CATALOG for the cursor-agent process.

jev-router --catalog
cursor-agent-jev --schema Bash

--schema dumps one tool's schema and does not exec cursor-agent. A known tool is decision: defer (autoAllow: false). An unmapped name denies (exit 2). Neither path prints {"decision":"allow"}. A schema dump is not a typed call. How to run: docs/SPIKE-catalog.md. This index does not set JEV_PERMISSION_MODE.

MCP tool intent can also be ranked into a typed call (best and top matches) on that same route-workflow policy. The router prints a tool_call payload and does not invoke the tool. This surface defaults to shadow. JEV_TYPED_CALL_MODE=active turns it on, and the flake does not set that variable. Until you export it, MCP stays ask. How to run: docs/SPIKE-calls.md.

Grok Build harness

grok-build-jev is the entrypoint Grok Build calls. It does not keep a second class map or a second TypeSafe client. hook reads a PreToolUse event and prints defer or deny. config prints the hook JSON; this repo does not install it. Modes stay shadow until you export active. JEV_BYPASS is still only 1 or true.

node packages/jev-router/harness.mjs smoke

How to run: docs/GROK-BUILD.md.

Skills

Skills are a flake input, and that input is the only skills tree Bezel installs. This repo ships them in .agents/skills/ (inputs.skills). scripts/sync-skills writes regular-file copies to .claude/skills/, .grok/skills/, and .cursor/skills/. There is no repo-root skills/ tree, no .omp/skills/, and no .codex/skills/. When you have a skills repo, change inputs.skills.url and the lock.

The tree includes bootstrap, the shadow check skill (jev-router --check), and laws. It also includes the skills for Lapis, Facet, Geode, and Phantom:

Skill What it answers How it runs
lapis Vault search and read, read-only nu lapis.nu, over lapis --json
facet Request history, read-only nu facet.nu, over facet … --json
geode Custody status, metadata only nu geode.nu, over geode --output json
phantom Code graph: where a name is defined, callers, impact, call paths, and which files change together nu phantom.nu, or a phantomq wrapper if you have one, over phantom-fractal on PATH or $PHANTOM_FRACTAL_BIN

phantom is Phantom's own skill, a byte copy of Phantom main that is never edited here. It keeps Phantom's envelope, not the shared one below. An agent may run its index whenever the index is missing or stale; it writes only to Phantom's own data directory, never to the repository. .agents/skills/README.md records the commit it was copied from.

Agent use: skills + CLI first, MCP still shipped

The default way for an agent to use Lapis, Facet, Geode, or Phantom is the bundled skill. In this repo that directory is .agents/skills/<name>/. After install, the same directory is at ~/.agents/skills/<name>/, ~/.claude/skills/<name>/, ~/.grok/skills/<name>/, and ~/.cursor/skills/<name>/. A short SKILL.md is what the harness reads to decide when to use it, plus a Nushell body (nu <name>.nu) that calls the CLI with JSON output. Every Lapis, Facet, and Geode command prints the same envelope: { ok, command, exit, data, error }. Phantom's prints { ok, command, data, meta, exit }, or on failure { ok, command, error, kind, stderr, exit }.

The MCP server for each tool (lapis mcp, facet mcp, geode mcp) stays supported and works the same as that tool ships it. Bezel does not disable MCP.

Why the skill is the default:

  • Context. An MCP server adds every tool's name, description and input schema to the model's context, often on every request, whether or not the tools are used. Many harnesses can only turn a whole server on or off. A skill costs a few dozen tokens of description until it is used.
  • Determinism. The skill body is fixed code over a versioned JSON contract, so results are the same each time.
  • Small models. Local models with short context windows feel the schema cost most.

Use the MCP server when your harness defers or filters MCP tool schemas (loading them only on demand, or letting you enable single tools), or when the client has no shell.

programs.bezel.enable puts the pinned Nushell on PATH and copies each skill directory into the four user directories above. The copies are regular files. A second activation leaves a file alone when its bytes already match, and it keeps that file's mode. If a managed file already exists with different bytes, or the path is a symlink, the activation prints a drift report and writes nothing, so a live ~/.agents/skills/lapis/lapis.nu stays in place for ~/.local/bin/lapisq. Repair with scripts/install-user-skills.sh --force .agents/skills "$HOME", which replaces the bytes and keeps the mode the file already had. --check reports drift and writes nothing.

nix build .#nushell
nu .agents/skills/lapis/lapis.nu status

These three scripts are read-only. Facet never requests history bodies, blobs, diff --bodies, or request run. Geode is metadata only and refuses every other command.

Platforms

Declared systems: aarch64-darwin, aarch64-linux, x86_64-linux. Intel macOS is not supported: nixpkgs 26.11 dropped it.

System Pinned binary (oh-my-pi v18.2.6) Availability
aarch64-darwin omp-darwin-arm64 Pin present. No hosted runner in this workflow.
aarch64-linux omp-linux-arm64 Pin present. No hosted runner in this workflow.
x86_64-linux omp-linux-x64 Pin present. GitHub Actions evaluates all three systems and builds overlay packages here.

If a later release drops a platform build, packages/omp-pin.nix throws for that system. A skipped CI row is a skip with a reason, not a pretend build.

nix flake check and nix build .#bezel .#jev-router .#cursor-agent-jev .#grok-build-jev do not download the pin. nix build .#bezel-pinned does.

Status

  • Overlay packages evaluate on all three declared systems.
  • CI on this repo runs the x86_64-linux job. The other two matrix rows skip (no matching hosted runner).
  • bezel-pinned is opt-in (180–240 MB download).
  • Jev defaults to shadow. jev-router --check is the shadow diff check. Empty findings are not approval. Loop-stop is shadow-first. Active stop and escalate do not exec.
  • The tool catalog is a small always-on index of the existing policy ids. Full schema is jev-router --schema NAME and is not an allow. Permission catalogs stay shadow.
  • grok-build-jev adapts those controls for Grok Build. Default modes stay shadow. The harness does not install a host hook.
  • Skills ship as .agents/skills, the flake's only skills tree. Lapis, Facet, and Geode are read-only skills there, and Phantom's code-graph skill is a byte copy of Phantom main: skill plus CLI is the default, and MCP remains supported. Nushell is pinned by the nixpkgs lock.
  • bezel-omp passes an omp config overlay that widens tool-output lines to 8192 bytes. BEZEL_OMP_OVERLAY=0 turns it off.
  • Nix packaging stays. The router stays JavaScript.

Contributing

Issues and pull requests are welcome. Match CI from a clone:

nix flake check -L
nix build -L .#bezel .#jev-router .#cursor-agent-jev .#grok-build-jev

Do not commit secrets. TYPESAFE_API_KEY and other keys belong in the process environment, not the flake.

License

Built by VirtualMachinist. A Hedronite setting. The lockup is in docs/brand/.

MIT. bezel-pinned downloads published binaries from oh-my-pi v18.2.6. This overlay does not include that project's source. Install a host omp binary from omp.sh, or set OMP_BIN.

Bezel is not Omarchy.

About

Bezel is a harness agnostic supplemental overlay. Jev integration, bend2 planned. current status prototype, will be written in Rust after PoC

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages