jevqueue

A decision queue in front of your agent's tools.

Your agent picks a tool. Before it runs, jevqueue asks a decision model whether it should — and refuses the call when the answer is no.

   agent decides to call Bash ──► jevqueue ──► decision model
                                        │
                    ┌───────────────────┴───────────────────┐
                    ▼                                       ▼
              allow the call                    refuse the call, with a reason

An ordinary agent loop asks one model to do two unrelated jobs: decide what to do next, and write the thing. The two share a pass, so two things go unchecked. The wrong tool runs, because nothing verifies the selection against anything. And the agent reports success on work that never happened, because the model that decides to stop is the model claiming it finished, and a model is a poor witness to its own reliability.

jevqueue moves the decision out of that pass and gives it a place to be enforced.

---

One package, two guarantees

Both live here, in one install, with no dependencies.

	What it is	Who it is for
The decision layer	The provider is constrained to a named tool, and the result is checked against it. A provider that ignores the constraint raises before anything executes.	People building an agent
The gate	A pre-tool hook that refuses a step the decision layer says should not run, and escalates a risky one.	People running an agent

They are different guarantees and it matters which one you have. A hook cannot constrain a provider's generation — the provider is not yours to constrain from a hook. What it can do is refuse a step, and that is worth a great deal. See Which guarantee do you need?.

---

Install

As a plugin — Claude Code

claude plugin marketplace add iamvazghen/jevqueue
claude plugin install jevqueue@jevqueue

In one command, on Claude Code v2.1.292 or later:

claude plugin install jevqueue --marketplace iamvazghen/jevqueue

Or from inside a session, on v2.1.275 or later:

/plugin install jevqueue --marketplace iamvazghen/jevqueue

As a plugin — Codex CLI

codex plugin marketplace add iamvazghen/jevqueue
codex plugin add jevqueue@jevqueue

As an extension — Gemini CLI and Qwen Code

gemini extensions install https://github.com/iamvazghen/jevqueue --consent

Qwen Code takes the same format, but asks which plugin to install when the URL points at a marketplace, so name the plugin and pass --consent:

qwen extensions install iamvazghen/jevqueue:jevqueue --consent

Both install from the published GitHub release, so a new version appears with gemini extensions update jevqueue rather than a reinstall.

As a plugin — opencode

opencode reads opencode.json from your project, so add the plugin there:

{ "plugin": ["https://github.com/iamvazghen/jevqueue"] }

Everywhere else

Cursor, Windsurf, Kiro, Cline, OpenClaw, GitHub Copilot and the agents.md standard all read a rules file, and this repository ships one for each — copy the one your agent looks for, or point it at the jevqueue skill. Every agent that speaks MCP gets the portable core as a tool called jevqueue_decide — registered for you by Claude Code, Codex and GitHub Copilot when the plugin installs — and the rules file tells the agent when to use it and what to do when it says no.

Where it runs, and what that buys you

Agent	Mechanism	What it gets
Claude Code	PreToolUse hook	The gate refuses the call before it runs
Codex CLI	PreToolUse hook	The gate refuses the call before it runs
Gemini CLI / Qwen Code	extension: MCP server, skills, BeforeTool hook	The queue is available to ask, and the hook is configured
opencode	tool.execute.before plugin	The gate refuses the call before it runs
Cursor, Windsurf, Kiro, Cline, OpenClaw, Copilot	rules file + AGENTS.md	The agent is told to ask the queue first
Any MCP agent	jevqueue_decide tool	The agent can ask about any step before taking it

Two dialects, one decision layer: Claude Code and Codex speak PreToolUse, Gemini speaks BeforeTool, and the same gate script answers both. Where an agent has hooks, the refusal happens before the tool runs. Where it does not, the rules file makes the agent ask first.

One honest caveat. Gemini CLI 0.45 loads an extension's hooks from hooks/hooks.json — the same path Claude Code uses — and the two dialects cannot both live in one file. The repository therefore keeps them apart: hooks/claude-hooks.json for Claude Code and Codex, hooks/hooks.json in Gemini's dialect. Claude Code still inspects hooks/hooks.json, finds an event it does not know, and reports one harmless warning while ignoring it; the hook Claude Code actually runs is the one its manifest declares.

As a library — in the agent you are building

pip install "jevqueue @ git+https://github.com/iamvazghen/jevqueue.git"

The package is not on PyPI, so the install names the repository. There are no required dependencies. httpx is needed only for the hosted decision model, and is an extra:

pip install "jevqueue[hosted] @ git+https://github.com/iamvazghen/jevqueue.git"

If you would rather work from a checkout, pip install -e . does the same thing without the network round-trip.

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗