Conversation
|
Understand this PR’s impact Explore downstream dependencies and potential security impact with Blast Radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe project catalog adds Jevonian, a TypeScript local OpenAI-compatible proxy, under the ChangesProject catalog
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Feature Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Landed on main as dde8d32 with you as the commit author, now live on https://awesomejev.com. Closing rather than merging because every PR appends to the same data file and they conflict with each other; landing directly keeps your authorship. Thanks! |
What this adds
How it uses Jev
Jevonian serves an OpenAI/Anthropic/Responses-compatible endpoint on
http://127.0.0.1:8787/v1. Forjevonian/auto, one Jev call answers both which candidate model and how deeply to think, chosen from a state snapshot built from the session (last user message, recent messages and tool results, consecutive error count, context headroom, quota health, candidate capabilities, and cache-switch penalties). Deterministic code narrows the candidate list first — wire protocol, context window, thinking-level floor, and spent quota windows are plain arithmetic, never model judgement.The four
typesafe,openrouter,vercel, andopencode-zenJev channels live insrc/brain.ts(https://api.typesafe.ai/v1/systemone,typesafe/jev-1.13).minConfidenceturns a low-confidence answer into a marked low-confidence turn in the ledger and response headers rather than a silently accepted route; secondary channels are only tried when the primary channel fails. Explicit routes (jevonian/plan,/execute,/utility,/chat) bypass Jev entirely, androuting.mode: "off"is pure pass-through.Why it is interesting
Two things other entries in this section do not cover:
The routing state and wire protocol for each Jev channel are documented in
docs/brain.md.Disclosure
I maintain Jevonian. v0, TypeScript, AGPL-3.0-only, published to npm as
jevonian. One project, one PR; this changes onlydata/projects.jsonand passesnpm run validate.siteis the npm package page rather than a homepage, since the product is the local server itself.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit