Question 1

What does Sabi route between?

Accepted Answer

It sits between a coding harness (Claude Code, Codex, controller-backed OpenCode and more) and the models the harness can call. The harness keeps its own loop, tools, permissions, history and approvals; Sabi decides what serves the next inference or task transition.

Question 2

How is Sabi different from an agent harness or editor?

Accepted Answer

The README calls it a host-agnostic routing layer, not another agent harness or editor. Adapters are optional bridges to the execution seams each host exposes, so the harness experience stays intact.

Question 3

What is the difference between inference routing and controller handoffs?

Accepted Answer

Inference routing picks the model and provider per round; controller handoffs decide continue, delegate or spawn. The README keeps these boundaries explicit — for example, a hook install is not model switching.

Question 4

How do I install it?

Accepted Answer

At user scope, not per worktree: npm install --global @vizuh/sabi-controller, then sabi setup, sabi doctor and sabi serve to run the local proxy on http://127.0.0.1:8787/v1. Use sabi setup --no-hooks for the daemon without changing host configuration.

Question 5

What evidence feeds the routing decision?

Accepted Answer

Trajectory evidence: tool calls, tool results, failures, context pressure, capabilities and provider state. That lets it pick cheap or strong capacity for the specific round rather than committing one model to the whole task.

Question 6

Can an AI agent install it for me?

Accepted Answer

Yes — the README provides a host-AI installation flow that asks for the harness and route explicitly and collects only an OpenRouter key on proxy paths. A skill is available via npx skills add vizuh/sabi --skill sabi.

Question 7

Does Sabi relate to Jev, and what should I be skeptical about?

Accepted Answer

The reviewed README excerpt documents no Jev or TypeSafe integration; its presence here comes from the awesome-jev-projects listing. The README itself warns that a catalog listing is not plan entitlement and a mock pass is not a savings benchmark.

Sabi

Highlights

Quickstart

Questions about this entry

From the Jev guides

From the Jev AI model community