JevTO / Documentation

Use JevTO with Claude Code, Codex, and Cursor

Each integration covers a named route. Listing JevTO as an MCP server does not automatically filter every native tool result.

Claude Code: automatic project routing

From the project you want to use, preview the change, inspect it, then apply it:

Terminal

jevto init-claude-auto --workspace .
jevto init-claude-auto --workspace . --apply

The project PreToolUse hook rewrites supported simple Bash/PowerShell commands through jevto run. A UserPromptSubmit hook records your prompt locally as the session goal. Tests, builds, lints, searches, and supported git diff/log/show commands can be routed. Pipes, redirects, substitutions, and unsupported shell shapes stay native.

Recorded live evidence used Claude Code 2.1.283, including passing and failing verifier routes. This is a tested version, not a guarantee about every future client. The hook does not set a permission decision. A configured OpenRouter key can enable goal-aware remote ranking in auto mode; read the outbound-data behavior first.

Already using RTK? Choose one command-rewriting hook per project. Claude rewrites do not chain. The installer warns about an RTK hook; review the preview rather than assuming both filters will compose.

Keep a session rules-only

Set the environment variable before starting Claude Code. Use the command for your shell:

Terminal

# PowerShell
$env:JEVTO_MODE = "rules"
claude

Terminal

# Bash / Zsh
export JEVTO_MODE=rules
claude

Remove the managed hook

Terminal

jevto disable-claude-auto --workspace .
jevto disable-claude-auto --workspace . --apply

Installers keep ownership records and backups. Removal targets the entries JevTO owns; review the preview, especially if you later edited the configuration by hand.

Codex: Windows PowerShell route

Terminal

jevto init-codex-pre-hook --workspace .
jevto init-codex-pre-hook --workspace . --apply
jevto disable-codex-pre-hook --workspace . --apply

Live pilot evidence used desktop-bundled Codex CLI 0.158.0-alpha.2.1 on Windows with allowlisted simple PowerShell commands. Do not infer automatic macOS/Linux Codex support from that test. Use the explicit wrapper when a host route is unavailable.

Cursor: explicit, narrow integration

jevto init-cursor-rule prepares a project rule for one exact verifier. jevto init-cursor-runner prepares an opt-in exact-command MCP runner. These are not universal tool interception. Run either command with --help, review its required workspace/program configuration, and inspect the preview before adding --apply.

The historical Cursor coding pair had unequal holdout outcomes and is excluded from successful-task savings claims.

Read-only MCP tools

jevto init codex, jevto init claude, and jevto init cursor prepare read-only recall, review, and status tools. Use the command's help and preview before applying it. Registration alone does not reroute your agent's shell commands.

Any supported shell: explicit wrapper

Terminal

jevto run --mode rules -- cargo test --workspace
jevto doctor --json

The command wrapper is the smallest integration to diagnose. Consult doctor for the current mode and recorded host coverage. For issues, include the exact host version, route, and sanitized command rather than saying only “Claude” or “Codex.”