github vava-nessa/free-coding-models v0.5.54

latest releases: v0.6.0, v0.5.99, v0.5.98...
3 months ago

Fixed

  • ๐Ÿ› ๏ธ patch-openclaw.js now respects real model metadata (#133) โ€” the script was destructuring only 3 of 5 fields from each nvidiaNim tuple ([modelId, label, tier, sweScore, ctx]), so it dropped the real ctx and fell back to a hardcoded contextWindow per tier (e.g. all S+ models got 128000, even DeepSeek V4 Flash which actually has 1M context). Now it parses the real ctx string ('200k' โ†’ 200000, '1M' โ†’ 1_000_000) and persists tier, sweScore, and a source field for traceability.

  • ๐Ÿงญ fcm_router now shows a real label in the TUI (#140) โ€” added a fcm_router entry to PROVIDER_METADATA so every UI surface (Setup wizard, Settings panel, tool launchers, TUI filters) resolves "Smart Router Daemon" instead of the raw key fcm_router (which users were reading as "Unknown"). The local getProviderLabel() in endpoint-installer.js was the only place that knew about fcm_router; it now falls through to PROVIDER_METADATA so all callers stay in sync.

Maintenance

  • ๐Ÿงน Closed 3 stale issues that were already fixed in older releases (verified by git log on the relevant code paths):
    • #116 โ€” Docker API 404s (fixed in v0.5.28, commit 2c07925)
    • #117 โ€” "pending" status confusing (fixed in v0.5.28, same commit)
    • #118 โ€” Probe loop silent stall (fixed in v0.5.36, commit f0dd3d8)
  • ๐Ÿงช +18 new unit tests for patch-openclaw.js parseCtx/defaultMaxTokens (11) and provider-metadata.js fcm_router lookup (7). All test runs go through pnpm test (no extra setup needed).

Pre-flight checks

  • 584/584 tests pass (pnpm test)
  • vite build succeeds (260 modules, ~283ms)
  • CLI loads cleanly (free-coding-models --help)

Don't miss a new free-coding-models release

NewReleases is sending notifications on new releases.