Question 1

What exactly leaves my machine when I interrupt an agent?

Accepted Answer

For every mid-turn message the hook sends the message text, up to 2,000 characters, and the start of the current task, up to 500 characters. No transcript, no files, no tool output. Logs stay local, and JEV_ROUTER_LOG_PROMPTS=false keeps message text out of them. The API key itself goes in the system keychain on the plugin path, or you can leave it empty and set TYPESAFE_API_KEY.

Question 2

Why does it need 0.9 confidence before it will hold my message?

Accepted Answer

Because queue and interrupt both change what happens to work already in flight, and the README says only confident answers change behaviour. Queue and interrupt each need probability at or above 0.9, and interrupt additionally needs an explicit stop signal. Anything else, including an unsure answer, an error or a timeout, falls back to the client's native injection, which is the same thing that happens today.

Question 3

Will this actually stop a long-running command?

Accepted Answer

No. The hook can only act at tool boundaries, so a running command finishes first, and a turn that is only producing text cannot be stopped. The interrupt path swallows the message and sets continue:false, which the next tool hook reads. That limit is inherent to where the client offers hooks, not something the thresholds can fix.

Question 4

Does it work with Codex as well as Claude Code?

Accepted Answer

There is a Codex folder, tested on 0.156.1, but the README marks it soft: Codex can only be nudged, not blocked, so a queue or interrupt cannot be enforced the way it is in Claude Code. The two clients have different hook contracts, which is why each lives in its own self-contained folder rather than sharing one integration.

Question 5

What three timings does the hook classify messages into?

Accepted Answer

steer (change the running task now), queue (a separate request to do afterwards) and interrupt (stop the task); only confident answers change behaviour, with queue and interrupt needing probability at least 0.9.

Question 6

What modes does the Jev steer-or-queue plugin offer?

Accepted Answer

shadow, the default, only logs decisions, while active queues and stops for real; start in shadow to read the log for a few days, then switch to active and change it later in /config.

Question 7

What are the hook's known limitations?

Accepted Answer

It can only stop at tool boundaries, Esc fires no hook so queued messages are listed and dropped on the next prompt, held messages do not appear as user messages, and Jev can be wrong on colloquial Chinese and negations.

Jev_steer_or_queue

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev community