熱門: 資料更新於2026年10月27日

軟體分類

網路軟體1,356
通訊社群321
影音軟體898
繪圖與影像539
辦公軟體1,124
開發工具3,134
AI工具529
安全與隱私385
系統工具3,114
遊戲523
教育與科學239
網路與IT284

hellogrok-cli 0.1.20下載

Console-only CLI of hellogrok, a local proxy that makes Grok Build custom model channels work with common API formats, native Web tools, isolated authentication, and automatic configuration recovery.

這是舊版本,目前最新版本為0.1.41。 hellogrok-cli 0.1.41 · 發行日期:

安裝檔 0.1.20

架構類型安裝範圍檔案大小下載SHA256
64位元 免安裝版 — — github.com VirusTotal
ARM64 免安裝版 — — github.com VirusTotal

下載連結與SHA256取自Windows套件管理員(winget)的社群資訊清單。執行前請先核對下載檔案的雜湊值。

更新紀錄

Added
- Per-channel absorb layer for transient upstream soft failures. While the upstream response headers have not been sent, retryable failures (busy/overloaded 503, 429, retryable 5xx, response-header timeouts) are retried inside the proxy with exponential backoff (2s–30s, honoring an upstream Retry-After up to 60s) for up to 90 seconds by default (absorb_retry_max_secs, absorb_retry_backoff_cap_secs). Grok Build's native 15-attempt retry budget stays untouched during the window; only when the window is exhausted does the failure pass through, still retryable. Transport errors are not absorbed so Grok Build's first-retry HTTP/1.1 client rebuild keeps working. UP absorb log lines record each wait.
- Synthesized 30-second Retry-After on retryable busy/overloaded 5xx passthroughs that carried none, pacing Grok Build's own retries. Upstream Retry-After headers are preserved.
- Opt-in dead-channel breaker (dead_channel_fail_fast, default off; dead_channel_fail_threshold, default 6). Only dial-level failures (connection refused, DNS, TLS handshake) count, because those can never succeed on retry; after the streak the proxy answers a non-retryable 503 proxy_circuit_open with X-Should-Retry: false, with one probe allowed after a 5-minute cooldown and any upstream response closing the breaker.
Changed
- The circuit breaker no longer fast-fails soft failures. Busy 503, 429, timeouts, transport resets, and error-body read failures pass through as retryable (or are absorbed first), so Grok Build keeps its complete native retry budget. X-Should-Retry: false is reserved for deterministic failures whose retries cannot succeed (authentication, permission, billing, quota, invalid request/model).

https://github.com/hellowind777/hellogrok/blob/HEAD/CHANGELOG.md#0120-2026-08-30

VPN與代理伺服器熱門排行

查看全部
  1. OpenVPNVPN與代理伺服器 · OpenVPN, Inc.
  2. nginxVPN與代理伺服器 · nginx
  3. Proton VPNVPN與代理伺服器 · Proton AG
  4. TailscaleVPN與代理伺服器 · Tailscale Inc.
  5. NetbirdVPN與代理伺服器 · NetBird GmbH
  6. v2rayNVPN與代理伺服器 · 2dust
  7. v2ray-coreVPN與代理伺服器 · v2fly
  8. Zed Attack ProxyVPN與代理伺服器 · ZAP
  9. WindscribeVPN與代理伺服器 · Windscribe Limited
  10. sing-boxVPN與代理伺服器 · SagerNet

hellowind777的其他軟體

查看全部
  • hellogrokVPN與代理伺服器 · hellowind777

標籤

分享