How can we access the dashboard via network?

[bbfans]

I want to view the dashboard in home network local ip. how can to do it ? can we expose it as a web service?

[mm7894215]

Hey @bbfans — good ask, and the more interesting answer turns out to be: the right path for what you want probably isn’t exposing the local dashboard at all, it’s cloud aggregation (sign in once, see your usage across every device at www.tokentracker.cc). I do have a branch for that — more on it at the bottom.

Today, three workarounds that work right now

1. SSH tunnel — cleanest, zero code change:

   ssh -L 7680:127.0.0.1:7680 <user>@<host-running-tracker>
   # then open http://localhost:7680 on the other device
   

2. Tiny LAN forwarder on the host, if SSH is overkill:

   socat TCP-LISTEN:7681,fork,bind=0.0.0.0 TCP:127.0.0.1:7680
   

   Then http://<host-lan-ip>:7681 reaches the dashboard from any LAN device. Heads-up: anything on your LAN can now read your token stats.
3. Tailscale / Cloudflared / ZeroTier — same idea, but auth + encryption built in. My pick if you want it to also work off-LAN.

Why tracker serve is bound to 127.0.0.1 in the first place

Not an oversight — it was tightened on purpose in #19 (bab2fa7b). That PR also added an ephemeral same-origin localAuthToken on mutating endpoints. Whatever shape a future --host flag takes, it has to keep that: mutating routes stay localhost-only, the LAN-reachable surface stays read-only, and the flag has to be loud (e.g. --host 0.0.0.0 --i-understand-this-exposes-my-tokens).

The path I actually recommend: cloud aggregation

There is a WIP branch — wip/cloud-aggregation (f90cab43) — that adds:

• 6 cloud edge functions (tokentracker-account-{summary, daily, hourly, monthly, heatmap, model-breakdown}) that aggregate by user_id across every signed-in device
• An AccountViewContext in the dashboard that flips fetchers between local and cloud (same UI, different data source)
• Device-token fallback so each device authenticates without manual key juggling

The story: sign in once on each machine, and www.tokentracker.cc shows your usage from all of them, anywhere, on any device, no LAN exposure required. It briefly landed on main (commits 022cdc85 / b53d18b8) and I reverted it within ~90 minutes the same day to rethink the account-view UX (auto-enabling public profile on first sign-in was too aggressive, and cross-device dedup needed more thought). The branch has been sitting at one commit since 2026-04-15.

If folks following this discussion 👍 it, that’s a useful signal to bump the rebase + ship work up the queue. If anyone wants to help validate the cross-device dedup logic against real data, that’s the riskiest part — happy to coordinate.

For your immediate need: SSH tunnel today, cloud-aggregation when it lands.