Add an errors screen that pulls admin ops error logs from sub2apicn and
the server4 fixed origin in parallel, refreshes every 60s while active,
and keeps the 0.2.3 key-usage panel and logs enhancements.
- accounts page gains a #keys DataTable below the accounts table showing
each API key's usage today: Key | Today | Tokens | Req, sorted by cost
- data comes from the Sub2API admin dashboard api-keys-trend (requests,
tokens, key names) plus api-keys-usage (today_actual_cost), derived
from the configured logs url and reusing the same admin API key
- key names use the same stable per-key colors as the logs page
- --once prints the same panel after the accounts snapshot; failures or
a missing token surface in the status line without touching accounts
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- logs columns are now Key | Account | Model | Effort | Type | Tokens |
Cost | First | Latency | Tok/s | Time
- First and Latency render in seconds (5.3s) instead of milliseconds
- Effort shows the request reasoning_effort (- when absent) and is
filterable; the detail line appends it to the model as model (effort)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- logs page adds First (first_token_ms) and Tok/s columns; Tok/s is
output_tokens / (latency - first_token) over the decode window
- detail line shows the same rate after first-token latency
- API key names render in a stable per-key color (crc32 over a 10-color
palette) so rows from the same key group visually; --once stays plain
- --once --logs prints the new first/tok-s columns
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
--once --logs now exits 2 with a clear pointer to SHUSUB2_LOGS_TOKEN /
~/.config/shusub2/logs-token instead of a raw HTTP 401 traceback; the TUI
logs page reuses the same hint.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- new logs page (press l / a to switch, or start with --logs) reading the
latest 100 requests from the Sub2API admin usage API on sub2apicn
- columns: Key, Account, Model, Type, Tokens, Cost, Latency, Time with a
per-row detail line (token buckets, actual cost, first-token latency)
- refreshes every 60s by default (--logs-refresh-seconds, --logs-limit)
- admin API key read from SHUSUB2_LOGS_TOKEN or ~/.config/shusub2/logs-token;
--save-config now persists logs-url/logs-token too
- --once --logs prints a one-shot logs snapshot
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
shujakuin