fix(usage): a CLIProxy hub saved as its management.html panel URL shows accounts again#25579

Approvability

Verdict: Would Approve

Macroscope's review found this PR approvable — This is a localized fix to normalize CLIProxy panel URLs while preserving existing path prefixes, with regression coverage added for the intended management.html case. A separate medium-severity edge-case finding remains about filenames containing management.html, but it does not alter this change’s small bug-fix classification.

Needs human approval because:

• 1 blocking correctness issue found at or above your repo's Minimum Blocking Severity

^{Adjust the Minimum Blocking Severity for this repo — including turning it Off — in Settings. You can add or adjust custom eligibility rules. Learn more.}

Review in Change Stack →

No actionable comments were generated in the recent review.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

External image Recent review info

External image Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: 7c22e24
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: 678fe06f-29de-4a88-872c-db88bc39b7a0

External image Commits

Reviewing files that changed from the base of the PR and between 9f73d4ef97f75747c23efdcbd4deb89d9808f132 and df62f6d680f973049dcf9313036f21d24708b228.

External image Files selected for processing: 1

• apps/server/src/usage/cliproxyApi.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 4 remain after this review.

merged current github/main into the existing contributor branch without rebasing. resolved the URL-helper conflict by retaining main's hub.url rename and this PR's parsed-pathname normalization. the diff remains two files, 32 additions and 7 deletions.

verification at df62f6d680f973049dcf9313036f21d24708b228:

• all 29 reported checks pass, with no pending or failing checks. github reports MERGEABLE; both review threads are resolved.
• blacksmith: all 26 focused CLIProxy tests pass. vp run check:changed FETCH_HEAD passes format, lint, knip, graphql, three affected package typechecks, and 27 tests across two files. the worker fetched current main to establish the comparison base.
• two independent read-only reviewers approved this head with no blocker or should-fix findings.
• no UI changes or new tests. existing evidence below is from the prior takeover, not rerun in this pass. live authenticated account restoration, desktop/mobile, and remote/tunnel behavior remain unverified.

before, main with the same saved hub url and fixture data:

after, this head with the same saved hub url and fixture data:

Verified in a real dev environment

partial verification at 9f73d4ef97f75747c23efdcbd4deb89d9808f132, with no source changes.

• installed and ran github/main (36aea583bb) in a separate worktree, stopped it, then installed and ran this exact fork head. used playwright from the repo with /usr/bin/google-chrome against the actual dev web client and server. no mocks, fixtures, replay provider, or seeded data.
• added the real local CLIProxy service through settings → providers → add hub, using its /management.html url. usage → limits reports http 404 on main. the identical url and key reach management authentication on this head and report http 401. this proves the routing correction, but does not prove account restoration.
• created a project for the real /home/user/t3code git repo through the app. selected codex gpt-6.1-sol, sent a prompt, then sent a follow-up in the same thread. both completed through the real local proxy. the recording shows the follow-up response and limits view.
• canceled hub removal and confirmed it remained configured; confirmed removal and checked that it disappeared from both settings and limits.
• blacksmith: vp i && vp test run apps/server/src/usage/cliproxyApi.test.ts passed all 23 existing tests. these cover prefixes, trailing slashes, uppercase panel names, queries/fragments, and near-match filenames. the pr's existing 24 ci checks are successful.

before, main with the saved panel url:

after, the same saved panel url and key reach authentication:

read-only dev database transcript after the app turns:

Not verified

restored pooled accounts and their session/weekly limits remain unverified. this vm supplies a codex API key, but the real hub rejects it as an invalid management key. later refreshes returned http 403, so i stopped unauthorized probes. the recording includes that later response. a valid hub management key is required to complete the successful account-list/quota path; no fixture was substituted.

the local codex quota probe separately returns JSON-RPC -32600 on both main and this head. real agent turns work, but this does not prove the local quota probe works. native desktop, ios/android, remote/tunnel connections, and a successful authenticated prefixed hub were not exercised. an 8-second vm overload toast appears in the recording; neither provider turn stalled.

this is evidence of corrected routing and working neighboring flows, not a full end-to-end verification of the requested account restoration. no commit or push was needed.