Skip to content

jevqueue 0.2.0: installable by anyone, in Claude Code and Codex

Choose a tag to compare

View all tags
@iamvazghen iamvazghen released this 28 Oct 19:02
· 9 commits to main since this release
v0.2.0
5c0c4b5

Installable by anyone, in both ecosystems

# Claude Code
claude plugin marketplace add iamvazghen/jevqueue
claude plugin install jevqueue@jevqueue

# Codex CLI
codex plugin marketplace add iamvazghen/jevqueue
codex plugin add jevqueue@jevqueue

Both verified end to end against this repository. Claude Code also takes the one-command form
(claude plugin install jevqueue --marketplace iamvazghen/jevqueue, v2.1.292+) and the
in-session form (/plugin install jevqueue --marketplace iamvazghen/jevqueue, v2.1.275+).

The skills work in any agent that reads SKILL.md, and the MCP server works in any
MCP-capable agent — neither needs hooks.

The credential comes from the plugin's settings, and nowhere else

It used to fall back to TYPESAFE_API_KEY in the environment, which meant the plugin could
pick up a secret already sitting in your shell and ship it to a server. It now reads one
place: the typesafe_api_key setting in /config, marked sensitive. A test pins it, and a
second test walks the source to make sure no file names a credential environment variable at
all.

It says what it does with your data

PRIVACY.md is new, and it
is specific rather than reassuring: the two scripts that run, what is read, what is sent and
where, that the transcript is sent in full within the bound rather than summarised locally
first, that there is no fetch of any kind, no telemetry and no update check, and the one
small cached file that gets written. The only outbound request the plugin can ever make goes
to https://api.typesafe.ai/v1/systemone, and only when you have configured a key.

NOTICE carries the
attribution: jev-governor is MIT and by the same author, and Jev is a separately hosted
service whose terms apply when a key is configured.

Versions are pinned

/jevqueue:setup installs jev-governor==0.2.0, with a tagged git source as the fallback for
when it is not on PyPI yet. An unpinned install means the plugin's behaviour can change
underneath a user's feet without the plugin changing at all.

Other changes

  • .gitattributes is scoped to the one file that genuinely needs it (bin/jevqueue, which
    breaks on a CRLF checkout), rather than rewriting line endings across the whole repository.
  • CI validates with --strict, which is the mode the publish guidance asks for: a manifest
    that passes loosely and fails strictly breaks somebody's install.
  • The README documents the minimum Claude Code version for each install form, because a
    plugin that only installs on the newest release is not publicly available in any meaningful
    sense.

40 tests, offline: no network, no API key, no provider.

Assets 2
Loading