Sessions
Transcript
/v1/messages
Anthropic-compatible. Point any SDK at …, key = control token. agent = host runs the CC loop (host tools/files, real usage). raw = credential-borrowing passthrough — the client builds the full request, host only swaps creds (needs the sdk_client surgery).
Response
awaiting request…
Egress 出口自检
登录前先确认:本容器出网真的走了你配的 best-vn.{acct} 代理(VN 出口),没漏成直连。打 ip-api.com,经代理 / 强制直连各一路,比对出口 IP。
Login
全程走 CC 自己的 OAuthService + installOAuthTokens(它的 axios/TLS/头),token 落 ~/.claude/.credentials.json。① 起登录 → ② 复制 URL 在指纹浏览器登录 → ③ 粘回「授权码#state」→ ④ complete。
Status
idle — 点 start login 开始
MCP hot-plug
add/reconnect/toggle need a real TUI (register closure). connect is a headless dry-run. attach wires tools into the selected session only.
—
Interception gateway
Rewrites every z_8(callModel) request in place (semantic MITM); CCH recomputes natively.
—
Request observer
ccasapi lifecycle
Every request through the cc-send path (CC's SDK client / YF) — invisible to Observe, which taps sp/z_8/T0f one layer above. Each capture: inbound identity + official? verdict (hover the badge for the evidence), the request as received, what 补CC包 injected/rewrote (original→fixed diff), and the return / error. Cold-start 400s and rate-limits are flagged.
/v1/messages — each capture flares in newest-first, expandable into RX · FIX · TX channels.Capabilities
| surgery | state | fn | exposes | meaning |
|---|
Raw
—
Official limits
CC 自带 fetchUtilization → GET /api/oauth/usage(发的就是 CC 那个请求)。订阅限额,百分比 + 重置时间。
Local usage
本机经 /v1/messages 网关捕获的真实 token 累计,按 model 分组(不含其它设备/claude.ai)。