REPOSITORY ANALYSIS

switchboard

Switchboard is a local Claude Code and Codex router. It assesses a new conversation's task with Jev, applies deterministic confidence rules to select the model and reasoning effort, and pins that route through follow-ups, tool calls, and resume to avoid unnecessary prompt-cache disruption.

E2 · source reviewedPublic material or source evidence was reviewed. A fixed-version source review requires checking a pinned revision; this is not a reproduction, performance endorsement, or safety guarantee.
Stars
7
Forks
0
License
Apache-2.0
Last commit
2026-09-22

What Jev does here

Jev classifies the task's capability tier, whether context is sufficient, and the lowest adequate reasoning effort for the candidate model. Application code applies confidence floors, maps the result to a model and effort, and persists that pair for later turns and tool continuations.

Adds structured choices or scores to the workflow; performance and cost benefits have not been independently verified.

The cited question builder and README were checked for model-specific reasoning effort and conversation route pinning. No CLI integration or cache measurement was run here. A pinned route preserves a model choice; it does not guarantee a provider cache hit.

What task does this project fit?

Select model capability and per-model reasoning effort while preserving a conversation's chosen route.

Material analysed:

From input to action

  1. Build task-type, context-sufficiency and candidate-specific effort questions.
  2. Normalize TypeSafe or Gateway responses.
  3. Apply owner policy and pin the model/effort pair for the conversation.

Implementation details that matter

Capability and effort are separate axes

buildJevQuestions asks effort relative to each eligible model. A stronger model does not automatically need greater effort, and the selected model's answer is the one policy uses.

Inspect the supporting source ↗

Conversation pinning is a cache-preservation choice

The README keeps the initial route stable and permits native manual overrides. This avoids automatic switching churn but does not guarantee a provider cache hit.

Inspect the supporting source ↗

When to choose it

Consider it when routing explainability and conversation stability matter. Do not equate confidence in a task category with probability that the chosen model will succeed.

How to inspect it yourself

Inspect the questions and Gateway metadata normalization, then use explain output to compare route reason, fallback and selected-model effort without changing a live conversation.

Limits of this review

  • No CLI integration run or cache measurement was performed.
  • Pinned routing may remain suboptimal when a task materially changes.
Primary material used in this analysis