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

軟體分類

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

hellogrok-cli 0.1.34下載

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.34

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

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

更新紀錄

Added
- Responses absorb window for retryable response.failed SSE terminals. While nothing has been written to the client, a Responses stream whose only terminal is a retryable failure (rate limit, concurrency, overload) is withheld — response headers and early frames stay buffered up to 32 frames — and replayed inside the absorb window with the same backoff and Retry-After handling as HTTP soft failures. Grok Build keeps its full retry budget; an exhausted window passes the failure through retryable. absorb_retry_max_secs = 0 streams the failed event immediately; deterministic response.failed events pass through without retry.
- Structured upstream error summaries for HTTP errors and Responses response.failed/error events (type, code, message), with bearer tokens, key assignments, and sk- values redacted and long messages truncated. An official Grok catalog name (for example grok-4.6) observed on a non-xAI custom channel is logged with body size, tool count, and session presence to aid /resume diagnosis; first-party api.x.ai routes and custom IDs without the grok- prefix are excluded.
- Explicit non-retryable 502 responses for stream-shape mismatches: an SSE body answered to a non-streaming request, or a streaming body answered to Grok Build's fixed non-streaming WebSearchClient request.
Fixed
- Concurrency-limit rejections (concurrency, concurrency limit, and the corresponding Chinese phrases) classify as transient, and error envelopes nested under response.error are recognized the same as top-level error objects.
- Client disconnects no longer surface as upstream stream failures. Messages, Chat Completions, native, and Responses streams log a client abort and emit no proxy_stream_error when the client write fails or the request context is canceled; truly truncated upstream streams still emit the error.
- Benign upstream-model mismatches log once per channel/protocol/configured/upstream pair (bounded to 256 keys); conflicting and invalid declarations always log. Responses SSE headers are sent only after the hold decision, so an absorbed retry never emits partial headers.

https://github.com/hellowind777/hellogrok/blob/HEAD/CHANGELOG.md#0134-2026-09-14

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

標籤

分享