CommandCodeAI / CommandCodeAI/command-code

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

Ouverte
#825 2 commentaires 0 réactions 1 personne assignée Voir sur GitHub

@ObaidNadeem y travaille déjà.

Depuis le 11/9/2026.

Langage dominant
Aucune donnée de langage
Étoiles
4k
Forks
350
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

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.

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.