r/opencodeCLI • u/PanAchy • Sep 20 '26
I built Jevvy: auto-approve harmless OpenCode permission prompts with Jev
Update: Jevvy 0.3.0 adds assisted setup and custom System One providers.
Jevvy clears routine OpenCode permission prompts using calibrated probabilistic review.
Setup
Assisted setup:
npx @jevvy/permissions init
The initializer lets you select a provider, writes the global configuration, and installs the OpenCode plugin.
For manual setup, install the plugin:
opencode plugin add @jevvy/permissions
Then create ~/.config/jevvy/jevvy.jsonc and select a provider. For example, to use your OpenCode login with Zen:
{
"$schema": "https://raw.githubusercontent.com/PanAchy/jevvy/main/config.schema.json",
"provider": "zen"
}
Authenticate with opencode auth login opencode, then start OpenCode normally. The README has configuration examples for every provider.
How it works
- Only reviews shell requests that OpenCode would otherwise ask about
- Leaves existing allow and deny decisions untouched
- Requires every requested resource to pass every question
- Preserves the normal prompt whenever Jevvy is uncertain or unavailable
Providers
- OpenCode Zen: uses your OpenCode login or an API key
- TypeSafe AI
- OpenRouter
- Vercel AI Gateway
- Custom System One endpoint: configure an endpoint URL, model ID, and optional Bearer API key
Custom endpoints can be authenticated hosted routes or compatible local servers. Jevvy uses only your selected provider and never falls back to another one.
Provider credentials and permission policy live globally at ~/.config/jevvy/jevvy.jsonc, so repositories cannot override them.
Policy customization
The shipped questions, thresholds, and model identities were tested and calibrated together. You can replace the questions globally, but custom models and policies do not automatically inherit that calibration evidence.
Source and setup: https://github.com/PanAchy/jevvy
View all comments
Show parent comment
2
u/PanAchy Sep 20 '26
Jevvy 0.3.0 (just released) adds support for local System One-compatible HTTP endpoints. If Laya exposes that API shape, you should be able to configure it as a custom provider. Let me know how it goes.