Full mode : issues with usage section

[w0l4i]

hi there

in full mode client pc windows and android ver 1.6.3 has issues to show usage today (estimated) section
NON OF THE NUMBER CHANGES ALL ARE AT 0 BUT IN OTHER MODES THEY WILL CHANGE AND SHOW CORRECT DATA USAGE ,
also the reset time of google app script daily limit is based on PST time not utc !

[w0l4i]

[w0l4i]

@claude @therealaleph

[therealaleph]

@w0l4i thanks — both are real, separate bugs:

1. "Usage today (estimated)" stuck at 0 in Full mode. Confirmed. The counter increments on each apps_script mode relay call — in Full mode the muxer takes a different path (src/tunnel_client.rs batch path), and it's not wired into the same counter. So in Full mode the displayed "today" is always zero. Need to instrument the batch fire path with the same counter increment. Tracking as a follow-up — not in v1.6.4 (which only contains the batching fix from #231) but will land in the next release.

2. PST vs UTC reset time. Also confirmed. Apps Script's daily quota resets at midnight Pacific Time (PST/PDT, depending on DST), not UTC. We display the reset countdown as if it were UTC midnight, which is off by 7-8 hours. The fix is to compute the next midnight in America/Los_Angeles instead of UTC. Also tracking for next release.

If you want to take a stab at either as a PR, both are small and isolated:

• (1) is a counter wiring in src/tunnel_client.rs::fire_batch — increment per-op or per-batch, your choice (per-op is more accurate to what Apps Script counts).
• (2) is in whichever module renders the reset countdown — needs a small dependency on chrono-tz or hand-rolling the PT offset (PT = UTC-8 standard / UTC-7 DST). Daylight saving boundary is the tricky bit.

Otherwise I'll bundle these into v1.6.5 alongside whatever else accumulates this week.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}