Skip to content

v0.2.0: Jev through OpenRouter and Vercel AI Gateway

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Sep 14:32
· 34 commits to main since this release
v0.2.0
d35eb58

Package name. The npm package is published as @french-castle/jev-code; the @francoischastel scope shown in earlier drafts was never used. v0.2.0 itself was not published to npm; install v0.2.1 or later.

Jev now works through OpenRouter and Vercel AI Gateway as well as directly on TypeSafe, and getting set up is one command.

npx -y @french-castle/jev-code setup

Highlights

  • Bring the key you already have. TYPESAFE_API_KEY, OPENROUTER_API_KEY, or AI_GATEWAY_API_KEY: the key's prefix (ts_, sk-or-, vck_) picks the host, whichever variable holds it. All three hosts serve Jev behind the same System One API, so the tools, the skill, and every harness adapter are unchanged.
  • setup asks for a key. Run it in a terminal with no key exported and it asks for one with hidden input, writes it into the harness configs, and prints the export line Pi and the CLI need. --no-prompt opts out.
  • doctor names the host. It shows which host and key variable are in use, warns when several keys are set (JEV_CODE_PROVIDER picks one), and refuses a key and base URL that disagree before any request is made.

Security

  • A key is only ever sent to the host that issued it. A base URL on another known host is refused; a proxy base URL applies to TypeSafe keys unless JEV_CODE_PROVIDER states the intent.
  • setup copies only the key in use into harness configs, scrubs it from a harness CLI's output, and redacts it in printed commands. The MCP server logs the host in use to stderr once, where harnesses keep their logs.
  • Details and the reporting policy: SECURITY.md.

Also in this release

  • Clearer API errors: the host's own message instead of a JSON blob (TypeSafe nests it under detail, OpenRouter under error).
  • OpenRouter requests carry the optional app attribution headers.
  • The missing-key error now reads No API key found and lists the three accepted variables.
  • The release workflow creates the GitHub release even when npm publishing is skipped, and says why.

Upgrading from 0.1.0

Nothing changes for TypeSafe users. If you matched the exact text TYPESAFE_API_KEY is not set anywhere, update it. When you switch hosts, re-run jev-code setup so the harness configs carry the new key.

Not in this release

Cloudflare Workers AI also serves Jev but uses a different request envelope; support is a planned follow-up.

Full details: CHANGELOG.md.

Assets 2
Loading