REPOSITORY ANALYSIS

openchamber

OpenChamber’s optional automatic model router uses Jev to classify a message before selecting a configured model and reasoning level.

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
10,398
Forks
1,145
License
MIT
Last commit
2026-09-23

What Jev does here

Jev selects a task category; local category mappings determine the model configuration.

Keeps routing categories and their model assignments explicit.

Only the optional routing module was inspected; cost or quality improvements for model combinations were not verified.

What task does this project fit?

Inspect model-category routing and a separate permission advisory path in an OpenCode interface.

Material analysed:

From input to action

  1. Build category criteria from enabled routes and send history/request.
  2. Accept only a known category above minConfidence.
  3. For permission checks, compare the ask Noul against a separate hold threshold.

Implementation details that matter

Unknown and weak routes have explicit reasons

decideRouting returns no category for malformed, unknown or low-confidence answers. Those states should not be reported as a successful model selection.

Inspect the supporting source ↗

Permission and routing are separate decisions

buildPermissionRequest sends permission type, patterns and metadata; decidePermission maps the ask probability to hold. Category confidence is not a permission grant.

Inspect the supporting source ↗

When to choose it

Useful when an interface needs configurable model groups and explainable fallback reasons. Review the surrounding executor before treating the advisor as an authorization system.

How to inspect it yourself

Call the exported pure decision functions with a known category, unknown ID and below-threshold score using a local test harness; compare their reason fields without a network call.

Limits of this review

  • No server or paid model call was run here.
  • The reviewed response schema checks field types but should not be mistaken for a complete security audit.
Primary material used in this analysis