CommandCodeAI / CommandCodeAI/command-code
Web dashboard: navigating to settings/billing (and other settings pages) triggers repeated downloads of .data files
@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.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.
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。