jev-tool-runner

# Jev native tool router

Jev selects a native Codex tool call **before the coding model is invoked**. Codex executes that call through its own tool runtime, approvals and sandbox. The result stays in Codex's conversation. The coding model handles reasoning, edits and the final answer.

The router does not open repository files, execute commands, or conduct a separate investigation. TypeSafe receives the current user goal, a small set of tool choices, and completion metadata—not source-file output.



## Run it

Requires Node.js 22+, an authenticated Codex CLI, and a TypeSafe key in a private env file. Verified with Codex CLI 0.153.4.

```sh
npm ci
npm run build

# Start a normal interactive Codex session in your project:
node /absolute/path/to/jev-tool-runner/dist/router-cli.js \
  --key-file /absolute/path/to/private.env -- \
  -C /absolute/path/to/your/project
```

Ask a task that names source files, for example:

> Read src/access.mjs and test/access.test.mjs, then explain the access check.

For an existing session, pass `resume SESSION_ID` after `--`. The wrapper supplies a local model provider for that process; it does not modify global Codex configuration or change the selected model, reasoning effort, permissions, or hook trust.

[Daily use](docs/DAILY-USE.md) · [Architecture](docs/ARCHITECTURE.md) · [Live validation](docs/evidence/native-routing.json)

## Current coverage

The Codex adapter offers bounded, numbered reads of relative source paths explicitly named in the current user message. Jev chooses among at most eight offers or hands control to the coding model. Codex executes at most four selected calls before handoff. Completed calls are excluded. Unsupported requests, missing tool support, provider failures and timeouts fall back to the ordinary coding-m