Skip to content

[Triage] Open Issues Health & Prioritization Assessment Report #6035

Description

@sususu98

Overview

This tracking issue provides an automated triage and health assessment across all 65 open issues in router-for-me/CLIProxyAPI. The objective is to identify genuine protocol regressions, silent data-loss bugs, and credential/cooldown deadlocks that directly impact production reliability, distinguishing them from feature requests, configuration questions, and stale entries.

  • Audit Scope: 65 open issues
  • Evaluation Method: Full-context structured evaluation powered by TypeSafe Jev System One parallel decision pipeline + codebase architecture cross-check.
  • Summary of Tiers:
    • Tier 1 (Critical Real Bugs): 19 issues — Severe data loss, silent message drops, stream terminations, or credential cooldown storms. Recommended for priority fixes.
    • Tier 2 (Valid Defect / High-Value Parity): 17 issues — Real edge-case bugs, token parameter mismatches, cache degradation, or specific model fixes.
    • Tier 3 (Features & Enhancements): 22 issues — Protocol expansions, new provider integrations, configuration switches.
    • Tier 4 (Invalid / Stale / Rant): 7 issues — Complaints, empty links, or user config issues. Recommended for closure.

🚨 Tier 1: Critical Real Bugs (Recommended for Immediate Action)

1. Protocol Translation Silent Data Loss

These issues silently discard customer prompts, attachments, or stream frames, resulting in upstream 400s or downstream empty_stream with zero actionable diagnostics.


2. Cooldown, Rotation & Credential Penalty Loops

These issues cause healthy credentials or downstream traffic to be penalized or locked out unnecessarily.


3. Concurrency, Streaming & Transport Lifecycle


🛠 Tier 2: Valid Boundary Bugs & High-Value Improvements (17 issues)

Issue Title Summary
#5005 openai-compatibility provider forwards max_tokens unchanged to models that require max_completion_tokens O1/O3 and reasoning models reject max_tokens with HTTP 400. Proxy should automatically remap parameter.
#5067 Codex executor injects image_generation into muse-spark-1.2; HasSuffix does not match Hardcoded prefix/suffix checks fail to match specific model variants, leading to upstream rejection.
#5300 Codex: auto-derived prompt_cache_key defeats upstream prefix caching for batch workloads Synthetic cache key derivation causes cache hit rates to drop to 0.4%.
#4779 Codex WebSocket proxy cannot relay x-reasoning-included when upstream provides it Missing header relay in WebSocket handshake.
#5000 Sanitize Claude tool names and provide fallback input_schema for parameterless/custom tools Claude strictly validates tool names (regex regex ^[a-zA-Z0-9_-]{1,64}$); unescaped tool names cause 400s.
#5483 fix(translator): match Claude no-prefill model families by tokens Token-based heuristic needed for new Claude 3.7+ models.
#5546 fix(codex): map web search action.sources to Claude results Search sources citations dropped when translating between Codex and Claude.
#3361 Fix Claude Responses tool_search and namespace tool round-trip Round-trip schema serialization defect for nested tool calls.
#5874 Support credential-level or per-model disable-image-generation for codex-api-key Azure OpenAI rejects image_generation in payload; currently only a process-global toggle exists.
#5112 Codex Responses: strip unsupported top-level metadata Extra metadata fields rejected by upstream Codex endpoints.
#4893 feat(openai-compat): 3rd-party proxy HTTP 400 due to missing reasoning_content Certain third-party endpoints require reasoning_content even if empty on text-only assistant turns.
#5840 feat(translator): preserve multi-turn reasoning context for Gemini/Antigravity Multi-turn reasoning thought blocks lost during OpenAI endpoint translation.
#3662 Should Antigravity/Gemini tool schemas still flatten anyOf / oneOf? Upstream schema parser compatibility for polymorphic tool inputs.
#5839 devin: swe-2 rejects any tool declaration upstream while swe-1-7 accepts Tool schema normalization difference across Devin model iterations.
#5449 Tracking: Claude Code prompt-cache and Fable 5.1 fixes Collection of tracking PRs for Claude prompt caching.
#5783 feat(codex): guide recovery when automatic credential renewal becomes impossible Clearer diagnostic errors when OAuth refresh token is revoked.
#5190 feat(interactions): session fallback, tool-name collision, models endpoint Interactions API edge-case followups from PR #5022.

💡 Tier 3: Feature Requests & Enhancements (22 issues)

Notable Highlights:


🗑 Tier 4: Invalid, Stale, or Non-Actionable (7 issues — Recommend Closing)

The following issues do not contain reproducible technical bugs, lack necessary details, or are non-actionable complaints:

Issue Title Reason for Closure
#1564 能否再难用一点?! Non-actionable complaint / rant with no diagnostic data or reproduction.
#3251 就没人fork 下来,进行二次开发吗? Community discussion / question, not a software bug or feature request.
#3053 image Empty issue body with only an image reference; lacks description and context.
#2064 mac下正确的快速开始 User setup inquiry better suited for Discussions / Q&A.
#4694 配置的请求头无效!!! Incomplete report with no configuration snippet, headers, or error logs provided.
#6015 https://code.claude.com/docs/en/auto-mode-classifier-billing Raw documentation URL with no issue description or proposal.
#5329 相关包测试里有环境相关的测试 Local environment flakiness rather than a proxy runtime defect.

Generated by automated triage analysis on 2026-09-22.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions