인기: 데이터 업데이트: 2026년 10월 27일

카테고리

인터넷1,356
커뮤니케이션321
오디오 및 비디오898
그래픽 및 디자인539
오피스 및 생산성1,124
개발 도구3,134
AI 도구529
보안 및 개인정보385
시스템 도구3,114
게임523
교육 및 과학239
네트워크 및 IT284

hellogrok 0.1.34 다운로드

Cross-platform 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 0.1.41 · 출시일:

설치 파일 0.1.34

아키텍처형식설치 범위파일 크기다운로드SHA256
64비트 포터블 — — github.com VirusTotal
ARM64 포터블 — — github.com VirusTotal

링크와 SHA256은 Windows 패키지 관리자 커뮤니티 매니페스트에서 가져왔습니다. 실행하기 전에 다운로드한 파일의 해시를 비교해 보십시오.

릴리스 노트

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위

전체 보기
  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의 다른 프로그램

전체 보기

태그

공유