CommandCodeAI / CommandCodeAI/command-code

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

Open
#825 2 comments 0 reactions 1 assignee View on GitHub

@ObaidNadeem is already working on this.

Since Sep 11, 2026.

Dominant language
No language data
Stars
4k
Forks
350
PR merge metrics
No merged PRs in 30d

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.