DEMO / RECORDING
Overview & Result
Runs as a wrapper around Claude Code. Checks every file modification and shell command against defined security policies, ensuring compliance without interrupting developer workflow.
How Jev fits in the loop
- Hook into Claude Code tool invocation lifecycle.
- Submit command parameters to Jev policy model.
- Approve safe actions instantly; prompt for human confirmation on policy anomalies.
How to reproduce
- Inspect the source implementation at https://github.com/clownware/bouncer.
- Configure local Jev API credentials and register required tool/model bindings.
- Execute test prompts and observe decision latency and routing outputs.
Why this build matters
Makes coding agent deployment safe for production codebases at negligible cost.
Reported performance
Reported by authorCost: ~$0.04/day
Author reported running continuous daily policy checks for roughly 4 cents per day.
Limitations
- Metrics are author-reported from the initial release unless independently verified.
- Requires access to the respective agent framework or runtime environment.
- Generative model execution remains external to the Jev decision step.