CommandCodeAI / CommandCodeAI/command-code
Web dashboard: navigating to settings/billing (and other settings pages) triggers repeated downloads of .data files
@ObaidNadeem arbeitet bereits daran.
Seit 11.9.2026.
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 4k
- Forks
- 350
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
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.databilling.datausage.datastudio.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-Typeor an erroneous<a download>/router fetch in the dashboard app treating a JSON state response as a file.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.