Jevvy Permissions 0.8.0

New providers

• #53 3294e69 - Add OpenAI Decisions (gpt-6-luna) and experimental Microsoft-Decision-1 via Azure Foundry. Non-Jev models require their own calibration.

Permission behavior

• #67 f66ac99 - Let Jevvy Permissions review selected shell ask rules with permissions.reviewAskPatterns. Nominations are exact and host-scoped. Other host asks and finalized allow/deny decisions stay unchanged. Claude inspects visible settings only.

Configuration

• #64 892a954 - Enable private local review history for both hosts with "metrics": { "enabled": true } in global configuration. Off by default, POSIX-only and best effort; it never changes permission decisions. Verbatim commands and raw answers may contain secrets. Disabling history does not erase records.

• #63 0673cbf Thanks @futafi! - Explicitly reuse an OpenCode API key with providers.<name>.opencodeCredential after global credentials and environment variables. OAuth connections are skipped; Claude credentials are unchanged.

Reliability

• #67 f66ac99 - Update the OpenCode SDK to 2.1.3, retaining OpenCode 2.0.27+ support. Claude-only use does not require OpenCode.

Fixes

• #53 3294e69 - Fix custom-question encoding and Microsoft deployment calibration. Add provider-name filtering during setup.

Jevvy Permissions 0.7.0

Breaking changes

• #61 cf41ba2 - Zen now defaults to paid jev-1.13. Set providers.zen.model to "jev-1.13-free" to use the limited-time free route. Paid Zen does not inherit the free route's calibration attribution.

Configuration

• #61 cf41ba2 - Choose a model with providers.<provider>.model for Zen, TypeSafe, OpenRouter, or Vercel. Jevvy Permissions sends the exact identifier without fallback and preserves it during setup. Unverified models can use shipped questions without inheriting calibration attribution.

• #60 3312d21 - Set permissions.timeoutMs to change the provider timeout in either harness. The default remains 5000 ms. Host deadlines may end reviews sooner; timeout leaves host permission handling unchanged.

• #40 74b785e - Use Jevvy Permissions consistently in setup and help. Clarify that OpenCode 2.0.27 is required only for the OpenCode integration, starting in 0.6.0.

• #41 4a275d7 - Explain permission handling with plain-language documentation and readable light and dark diagrams, including the npm README.

Reliability

• #45 8bb92f5 - Improve setup with Unicode-safe layouts, masked credentials, clean cancellation, and support for Windows .cmd harness installers.

• #46 06b03c5 - Check selected harness CLIs before saving setup. Warn about unsupported or unrecognized OpenCode versions and require an explicit override to continue.

• #44 c9f3f81 - Release Claude Code settings inspection on timeout or interruption while preserving host asks and linked-worktree settings.

• #43 4d08c2e - Load global configuration through Effect filesystem services while preserving credential-file permissions and setup diagnostics.

Fixes

• #59 ad50af2 - Send Zen API keys as Bearer tokens so paid-model requests authenticate correctly.

• #42 7143594 - Execute provider judgments during calibration. Preserve interrupted runs, record invalid responses as errors, and refuse to overwrite existing calibration artifacts.

Jevvy Permissions 0.6.0

Configuration

• #36 99446f5 - Add independent persistent review controls for OpenCode and Claude Code through /jevvy. Each harness's enabled setting is stored in the global jevvy.jsonc; existing configurations remain enabled by default.

• #36 99446f5 - Make /jevvy available in OpenCode's web and terminal interfaces. Confirmations do not start a model request. The web UI displays them in its native Updates rows; live indicators and arbitrary plugin notifications are not currently supported there.

Permission behavior

• Turning Jevvy OFF skips new reviews and cached judgments without changing the host's permission handling. Reviews already started finish normally. Turning Jevvy back ON resumes review.

• #36 99446f5 - Treat Claude Code's exact Bash and Bash(*) catch-all ask rules as invitations to Jevvy review, matching OpenCode's shell catch-all behavior. Other matching configured asks remain with the host. Abstention leaves native prompting or automatic acceptance unchanged.

Reliability

• Show a text-only green/red Jevvy indicator in both terminals, with a brief blink when the setting changes. Reflect changes from other sessions and configuration edits without restarting.

• Serialize configuration updates across processes and initialization, keep credential-bearing writes private, and recover expired writer locks.

Fixes

• #36 99446f5 - Fix loading on OpenCode 2.0.27 by aligning the plugin and bundled runtime with Effect 4.0.1.

Breaking changes

• Requires OpenCode 2.0.27 or later. For earlier OpenCode v2 versions, pin @jevvy/permissions@0.5.1.

Jevvy Permissions 0.5.1

Fixes

• #32 0664375 - Restore OpenCode shell review when the winning permission rule is exactly shell / * / ask. Specific asks remain human-only, existing allows bypass review, and denies stay blocked. Jevvy approves only the current action; uncertainty or provider failure leaves the human prompt intact.

Configuration

• Show the required catch-all shell ask rule after interactive setup so commands can reach Jevvy for review.

Reliability

• Update the OpenCode plugin dependency to 2.0.26, with real-host shell review checks on OpenCode 2.0.18 and 2.0.26.

Jevvy Permissions 0.5.0

Jevvy 0.5.0 adds Laya as a provider and keeps explicit host-configured shell asks in the human permission flow.

New providers

• #28 b8a6350 - Add Laya with a default local endpoint, configurable server URL, checkpoint and Bearer-key settings, and routed-checkpoint verification. Its policy is scoped to Laya and bound to a checkpoint rather than inheriting Jev's thresholds. Calibration records both the verified checkpoint and Laya's reported model family.

Permission behavior

• #26 b206d12 - Preserve visible configured shell asks as human prompts in OpenCode and Claude Code. Review eligible shell requests as complete final commands, including OpenCode plugin rewrites; when Jevvy does not approve, leave the host's permission flow unchanged.

Jevvy Permissions 0.4.0

Jevvy 0.4.0 adds Claude Code permission review, multi-harness setup, and Node.js 22 support while preserving each coding agent's native permission flow whenever Jevvy abstains.

New harnesses

• #24 5073e5d - Add a Claude Code plugin that reviews Bash PermissionRequest events and grants one-action approval only when every Jevvy inquiry passes. All uncertain and unavailable outcomes leave Claude Code's remaining permission flow unchanged.

Configuration

• #24 5073e5d - Let jevvy init install OpenCode, Claude Code, or both from one multi-select setup flow.

• #24 5073e5d - Report invalid Jevvy configuration and missing provider credentials when a Claude Code session starts, without changing any permission decision.

Reliability

• #24 5073e5d - Support Node.js 22.19 and newer for setup, provider review, and Claude Code hooks.

Fixes

• #24 5073e5d - Correct the MIT license attribution in the repository and published package.

Breaking changes

• #24 5073e5d - Stop reading OpenCode login credentials for OpenCode Zen. Every harness now uses the selected provider's API key from the global Jevvy configuration or its native environment variable.

Jevvy Permissions 0.3.0

Jevvy 0.3.0 adds assisted setup and custom System One providers, with explicit provider selection and clearer setup guidance.

New providers

• #21 1c18ec3 - Connect Jevvy to any System One-compatible HTTP endpoint with a configurable endpoint URL, model ID, and optional Bearer API key. This includes authenticated hosted routes and compatible local servers.

Configuration

• #21 1c18ec3 - Add jevvy init, an interactive setup workflow that configures a provider, stores credentials in the protected global Jevvy file, and installs the selected harness integration.

• #23 aeb5760 - Clarify that missing provider setup can be completed with either jevvy init or a manually created global configuration file.

Breaking changes

• #21 1c18ec3 - Remove automatic provider selection. Jevvy now requires an explicit provider in ~/.config/jevvy/jevvy.jsonc. Existing installations using provider: "auto" must run npx @jevvy/permissions init or select a provider manually. Until configuration and required credentials are available, OpenCode reports Jevvy as failed and its remaining permission flow continues unchanged.

• #21 1c18ec3 - Custom approval policies now use a numeric threshold directly on each question. Replace an atMost threshold object with its numeric value. Custom Inquiries must describe reasons for human review, so lower answers pass. Rewrite and recalibrate policies that previously used atLeast.

Jevvy Permissions 0.2.0

Jevvy 0.2.0 expands provider choice and strengthens provider failure handling without changing its abstention-first permission behavior.

New providers

• #17 582c7bd - Add OpenRouter as a configurable Jev provider through its TypeSafe-compatible System One endpoint.

• #18 0e50d79 - Add Vercel AI Gateway as a supported provider.

Reliability

• #10 ed85087 - Use one Effect runtime throughout provider evaluation, permission review, OpenCode integration, and calibration, with typed provider failures that preserve native permission prompts when Jevvy cannot decide.

• #12 1bf3bf8 - Report structured provider failures in OpenCode server logs and apply bounded provider cooldowns after rate limits or exhausted credits while preserving native permission prompts.

Provider infrastructure

• #13 a1047a4 - Send provider requests through Effect HTTP with Schema-backed JSON encoding and decoding, and document a copyable TypeSafe API key configuration.

Jevvy Permissions 0.1.0

Minor Changes

• e2e88ed - Release Jevvy's OpenCode permission reviewer with calibrated harmless-command approval, global provider configuration, custom policy calibration, and abstention-safe failure behavior.