CommandCodeAI / CommandCodeAI/command-code

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

未關閉
#825 2 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@ObaidNadeem 已經在處理了。

開始於 2026年9月11日。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

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.

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。