Question 1

Do I need both an OpenRouter key and a chat model?

Accepted Answer

You need one account and two models. The plugin reads OPENROUTER_API_KEY, or an api_key passed to setup, for the Decisions endpoint where Jev classifies the intent. The actual work goes through a separate chat endpoint, defaulting to openai/gpt-4o-mini with a quick/deep tier pair for general_question. Jev never writes your code; it only picks the handler.

Question 2

What happens if Jev is unsure or the API is unreachable?

Accepted Answer

Below confidence_threshold, 0.6 by default, the on_uncertain callback fires with the intent and confidence so you can handle it. For read_file the plugin then falls back to a vim.ui.select picker, and the same fallback covers an unavailable API. on_error gets every failure, and the per-request timeout defaults to 30,000 ms. edit_code additionally falls back to a full-file rewrite when the chat model returns no structured edits.

Question 3

How much of my codebase ends up at the provider?

Accepted Answer

It is bounded. Injected context is the active buffer, the file tree and key files such as README.md, capped by default at 200 files and 20,000 characters. read_file sends at most 100 candidate paths, taken from open buffers and git ls-files, and it falls back to find when git is missing. Per-buffer conversation history is kept at six turn pairs by default so follow-ups like 'now refactor it' route correctly.

Question 4

Is the threshold something I should leave at the default?

Accepted Answer

It is the main knob. At 0.6 the plugin acts on the route Jev picked; below that it notifies and, for read_file, hands you a picker. Raising it trades convenience for fewer wrong-file opens at the cost of more interruptions. The threshold, timeout, model aliases, context caps and per-intent route_handlers overrides are all in setup, and handlers can be replaced without touching the classification layer.

Question 5

What commands does the plugin add?

Accepted Answer

:JevAsk routes a prompt, :JevAskBuffer optionally routes the current buffer with a prompt, and :JevClear clears the conversation. A bounded six-turn-pair history is kept per buffer so a follow-up like 'now refactor it' still routes correctly.

Question 6

How does each of the four intents actually act?

Accepted Answer

read_file resolves the file semantically over open buffers plus git ls-files and opens it in a vertical split with line numbers. run_command previews one generated command in vim.ui.input before running it in a bottom terminal. general_question streams into a floating window, and edit_code applies changed hunks behind a vimdiff preview.

Question 7

Can I replace the built-in handlers or clients?

Accepted Answer

Three seams do it without touching the classification layer: chat_backend for non-streaming chat, chat_stream_backend for streaming, and file_provider for file discovery. Any of the four intents can also be overridden through route_handlers in setup.

Jev Router.nvim

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev community