oc-plugins
OpenCode plugin collection whose oc-auto-perms package uses Jev to check tool-call intent against natural-language permission rules.
Overview
oc-plugins is a monorepo of OpenCode V2 plugins by Ope Oginni, each released as an independent npm package. The relevant one is oc-auto-perms, described as universal intent-aware permissions powered by TypeSafe's Jev: per the list summary, it checks a tool call's intent against natural-language rules to decide whether the agent may proceed. Other packages, oc-ping (iMessage notifications) and oc-invaders (a TUI game), are works in progress.
The top-level README covers development with Bun, testing, and releasing with Changesets; the details of oc-auto-perms's rules and thresholds are in its own package directory and not in the excerpt. It suits OpenCode users who want fewer permission prompts without blanket approval.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | Does this tool call's intent comply with the permission rule?(inferred) | yes · no |
How it works
- OpenCode agent proposes a tool call.
- oc-auto-perms asks Jev whether the intent matches the natural-language rules.
- Allow automatically or fall back to asking the user.
Strengths
- Intent-aware permissions instead of fixed patterns.
- Independently versioned npm packages.
Caveats
- Rule and threshold details not in the top-level README.
- Other plugins in the repo are WIP.
Getting started
bun install && bun run build in the monorepo, or install the oc-auto-perms npm package into OpenCode.At a glance
- Type
- Plugin
- Status
- prototype
- Language
- TypeScript
- Runtime
- OpenCode plugin, Bun
- Has code
- yes
- Has tests
- yes
Use cases and integrations
How curated lists describe it
The oc-auto-perms plugin in an OpenCode plugin collection uses Jev to check tool intent against natural-language rules.
logicrw/awesome-jev-projects
Frequently asked questions
Which plugin uses Jev?
oc-auto-perms, for intent-aware tool permissions.
Which agent does it work with?
OpenCode V2.
Are the other plugins related to Jev?
No, oc-ping and oc-invaders are unrelated works in progress.
Related projects
OpenJev for Claude Code: plugin and MCP server giving Claude jev_choice, jev_noul, jev_score and jev_ask tools on the live API.
MCP serverbetaTypeScriptEffect-based safety gate for coding-agent shell commands: fast rules first, then Jev decides allow/deny plus eleven risk checks.
ProjectbetaTypeScriptLocal guard layer for coding agents that blocks dangerous tool calls by deterministic rules, with optional Jev judgments.
CLIbetaTypeScriptSecurity hook giving Codex, Copilot, Gemini, Cursor, pi, OpenCode and ACP an auto-mode-like guard via three Jev questions.
LibrarybetaTypeScriptCoding-agent plugin that has Jev auto-approve shell permission requests it judges harmless and abstains on anything uncertain.
PluginbetaTypeScriptOpenCode 2 plugin that asks Jev six questions about every shell command (local or remote via FarHand) and prompts unless clearly safe.
MCP serverbetaTypeScript