CommandCodeAI / CommandCodeAI/command-code

Web dashboard: navigating to settings/billing (and other settings pages) triggers repeated downloads of .data files

Aperta
#825 2 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@ObaidNadeem ci sta già lavorando.

Dal 11/9/2026.

Lingua principale
Nessun dato sulla lingua
Stelle
4k
Fork
350
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Summary

When navigating the Command Code web dashboard (commandcode.ai), certain pages cause the browser to repeatedly download .data files into the download folder. Seen on /settings/billing and other settings/studio routes.

Downloaded files (re-created on every visit/navigation):

  • lzt02276551.data (named after the logged-in username)
  • keys.data
  • billing.data
  • usage.data
  • studio.data
  • plus numbered duplicates (keys(1).data, lzt02276551(2).data, …) because it re-downloads on each navigation.
What the files contain

Each file is a serialized snapshot of the dashboard SPA's current route + page data + user object — a reference-style JSON array, e.g.:

[{"_1": 2}, "routes/login/settings/billing", {"_3": 4}, "data", { ... }, "user", { ... }, "login", "<username>", "isCurrentUser", true]

Other files show "routes/studio-entity", "routes/login/settings/api-keys", "routes/login/settings/usage" etc. So it looks like the app's router/serializer state is being emitted as a downloadable attachment instead of being consumed in-page.

Expected behavior

Navigating billing/settings pages should render normally in the SPA and not trigger any file downloads.

Actual behavior

Every visit to the page downloads the matching .data file(s) into the browser download directory (downloaded repeatedly across page loads — hence the (1), (2) suffixes).

Environment
  • Web dashboard at https://commandcode.ai (Chrome/Edge, Windows)
  • Not related to the CLI / Provider API — this is the hosted web UI
Notes
  • No credentials/API keys appear in the files (checked), but it still dumps route/user state to disk on every navigation, which is unexpected and undesirable.
  • Likely a missing/incorrect Content-Type or an erroneous <a download>/router fetch in the dashboard app treating a JSON state response as a file.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.