Repository navigation
literouter v0.3.1
v0.3.1 — Richer Request Activity
Highlights
- Request-level context: Every activity entry now records the ingress method and path, ingress and upstream protocols, client IP, User-Agent, and the exact request and response sizes.
- Usage and cost: Input tokens, output tokens, and the estimated cost are carried from the relay that actually answered into both the activity table and the detail view.
- Operational filters: The console can filter the stream by cache hits, failovers, or errors, with live totals for the visible requests, tokens, cost, and cache hits.
- Cache visibility: A local response-cache hit or miss is recorded on the request itself, so a fast answer no longer looks like an unexplained relay response.
- Routing clarity: The detail view keeps the logical model beside the renamed upstream model and names both sides' protocols, while preserving the existing timing, streaming, failover, and body-logging views.
Upgrade Notes
- The configuration schema is unchanged. Existing
config.jsonfiles continue to load without edits. - Existing persisted logs remain readable. Entries written before this release simply omit the new request-context fields, and the console renders them as unavailable rather than failing.
- The new fields describe only values the proxy already observed; no prompt, credential, or additional request content is logged.
Installation
Download the archive for Linux x86_64, macOS arm64, or Windows x86_64 from the GitHub Release, verify its .sha256 file, and run literouter serve. Linux users can also install the latest binary with:
curl -fsSL https://raw.githubusercontent.com/YangQi0408/literouter/main/scripts/install.sh | bashThen open http://127.0.0.1:8787/ui/ to use the built-in Web Console.