https://chatgpt.com/s/t_6aa10616614c81919a7d6cceb2c2bf76
下面这版可以直接粘贴到 Comfy-Org/Comfy-Desktop → New issue → Bug Report。我把敏感信息留作可选项,也明确区分了“确认现象”和“尚未确认根因”。
建议标题:
[Bug]: Signing in to Comfy account hides existing local instance and shows "Instance 0" (Windows, Desktop 1.0.47)
App Version
- Comfy Desktop: 1.0.47
- OS: Windows 11
- Installation type: Local standalone ComfyUI installation managed by Comfy Desktop
- ComfyUI version:
v0.35.0+1
- Account state: Reproducible only when signed in to a Comfy account
Expected Behavior
After signing in to a Comfy account, the existing local ComfyUI installation should remain visible and selectable in the Comfy Desktop instance selector.
The existing local instance should not disappear from the Dashboard simply because the user signs in.
Expected:
Comfy Desktop
└── Comfy-daohegu
Actual Behavior
When I am not signed in, Comfy Desktop correctly shows my existing local instance:
Comfy-daohegu
GitHub latest · v0.35.0+1
After I sign in to my Comfy account, the main Dashboard changes to:
The existing local instance is no longer shown.
If I then sign out, the existing instance immediately reappears:
Comfy-daohegu
GitHub latest · v0.35.0+1
Therefore the local instance itself is still present and functional; the problem appears to be specifically related to the signed-in Dashboard / instance picker.
Steps to Reproduce
- Install/use Comfy Desktop 1.0.47 on Windows 11.
- Have an existing local standalone instance managed by Desktop.
- In this case, the existing instance is named
Comfy-daohegu.
- Start Comfy Desktop while signed out.
- Confirm that
Comfy-daohegu is visible in the instance selector.
- Sign in to a Comfy account.
- Return to the main Dashboard.
- The Dashboard now shows
Instance 0 and the existing local instance is no longer displayed.
- Select Add Existing Instance and point it to the existing installation directory.
- Desktop reports:
That directory is already used by "Comfy-daohegu".
- Sign out of the Comfy account.
- The
Comfy-daohegu instance immediately becomes visible again.
Reproduction result
This behavior is reproducible:
SIGNED OUT
↓
Comfy-daohegu visible ✅
↓
SIGN IN
↓
Instance 0 ❌
↓
SIGN OUT
↓
Comfy-daohegu visible again ✅
Diagnostics
The local instance registration is still present in:
%APPDATA%\Comfy Desktop\installations.json
The registered entry contains:
{
"id": "inst-1788440139228",
"name": "Comfy-daohegu",
"sourceId": "standalone",
"status": "installed",
"seen": false,
"installPath": "D:\\AI\\Comfy-Desktop\\ComfyUI-Installs\\Comfy-daohegu"
}
The installation directory exists:
D:\AI\Comfy-Desktop\ComfyUI-Installs\Comfy-daohegu
The ComfyUI directory contains the expected installation structure, including:
ComfyUI\
├── .git
├── .venv
├── custom_nodes
├── models
├── input
├── output
├── user
├── main.py
└── ...
The Desktop tracking marker is also present:
D:\AI\Comfy-Desktop\ComfyUI-Installs\Comfy-daohegu\.comfyui-desktop-2
Its contents are:
The installation metadata also contains 107 snapshots and a recent rollback record, indicating that Desktop still has substantial metadata for this installation.
installations.json was independently parsed with PowerShell ConvertFrom-Json and is valid JSON.
Relevant Log Output
After signing in, the Desktop log contains the following error:
[ERROR] Error occurred in handler for 'comfybuilder:listBuilds':
ComfyBuilderApiError: Forbidden: /v1/builds?limit=100:
The developer platform is in limited beta and your account is not enabled yet.
This results in HTTP 403.
However, I have not established that this 403 is the direct cause of the local-instance disappearance. The important reproducible symptom is that signing in causes the local instance to disappear from the Dashboard, while signing out immediately restores it.
The current app.log does not show an error mentioning Comfy-daohegu, installations.json, or a failed local-instance load during the signed-in state.
Additional Observation
Selecting Add Existing Instance does not solve the problem because Desktop already recognizes the directory as belonging to the existing installation:
That directory is already used by "Comfy-daohegu".
This suggests the local installation is still registered correctly, while the signed-in Dashboard / instance picker is failing to display the registered local installation.
Data Safety / Workaround
No local installation data was deleted or modified.
The following are intact:
- Existing ComfyUI installation
.venv
.git
custom_nodes
models
input / output
- Desktop tracking marker
installations.json
- Existing snapshots
Current workaround
Remain signed out of the Comfy account.
When signed out, the existing Comfy-daohegu instance is displayed and can be used normally.
Question
Could this be related to the signed-in Dashboard / instance picker state, account-specific filtering, or the new cloud/developer-platform UI?
The key distinction is:
The same local installation is visible immediately before sign-in and immediately after sign-out, but disappears only while signed in.
Please let me know if you need the full app.log, installations.json, browser/renderer console logs, or additional diagnostic information.
我建议你提交时再附两张图
第一张:未登录时显示 Comfy-daohegu 的主界面。
第二张:登录后显示 实例 0 的主界面。
这样官方开发者可以一眼看到 A/B 差异。
还有一个很重要的点:不要在 Issue 里公开你的真实 Comfy 账号邮箱。上面的报告没有放。
这个报告的结构也对应 Comfy Desktop 官方当前 Bug Report 模板要求的 App Version、Expected Behavior、Actual Behavior、Steps to Reproduce、Debug Logs 等字段。([GitHub]1) 目前 Comfy-Org/Comfy-Desktop 是官方 Desktop 仓库,GitHub 页面仍提供 Issues 入口。([GitHub]2)
[打开 Comfy Desktop GitHub Issues](https://github.com/Comfy-Org/Comfy-Desktop/issues?utm_source=chatgpt.com)
https://chatgpt.com/s/t_6aa10616614c81919a7d6cceb2c2bf76
下面这版可以直接粘贴到 Comfy-Org/Comfy-Desktop → New issue → Bug Report。我把敏感信息留作可选项,也明确区分了“确认现象”和“尚未确认根因”。
建议标题:
[Bug]: Signing in to Comfy account hides existing local instance and shows "Instance 0" (Windows, Desktop 1.0.47)App Version
v0.35.0+1Expected Behavior
After signing in to a Comfy account, the existing local ComfyUI installation should remain visible and selectable in the Comfy Desktop instance selector.
The existing local instance should not disappear from the Dashboard simply because the user signs in.
Expected:
Actual Behavior
When I am not signed in, Comfy Desktop correctly shows my existing local instance:
After I sign in to my Comfy account, the main Dashboard changes to:
The existing local instance is no longer shown.
If I then sign out, the existing instance immediately reappears:
Therefore the local instance itself is still present and functional; the problem appears to be specifically related to the signed-in Dashboard / instance picker.
Steps to Reproduce
Comfy-daohegu.Comfy-daoheguis visible in the instance selector.Instance 0and the existing local instance is no longer displayed.Comfy-daoheguinstance immediately becomes visible again.Reproduction result
This behavior is reproducible:
Diagnostics
The local instance registration is still present in:
The registered entry contains:
{ "id": "inst-1788440139228", "name": "Comfy-daohegu", "sourceId": "standalone", "status": "installed", "seen": false, "installPath": "D:\\AI\\Comfy-Desktop\\ComfyUI-Installs\\Comfy-daohegu" }The installation directory exists:
The ComfyUI directory contains the expected installation structure, including:
The Desktop tracking marker is also present:
Its contents are:
The installation metadata also contains 107 snapshots and a recent rollback record, indicating that Desktop still has substantial metadata for this installation.
installations.jsonwas independently parsed with PowerShellConvertFrom-Jsonand is valid JSON.Relevant Log Output
After signing in, the Desktop log contains the following error:
This results in HTTP 403.
However, I have not established that this 403 is the direct cause of the local-instance disappearance. The important reproducible symptom is that signing in causes the local instance to disappear from the Dashboard, while signing out immediately restores it.
The current
app.logdoes not show an error mentioningComfy-daohegu,installations.json, or a failed local-instance load during the signed-in state.Additional Observation
Selecting Add Existing Instance does not solve the problem because Desktop already recognizes the directory as belonging to the existing installation:
This suggests the local installation is still registered correctly, while the signed-in Dashboard / instance picker is failing to display the registered local installation.
Data Safety / Workaround
No local installation data was deleted or modified.
The following are intact:
.venv.gitcustom_nodesmodelsinput/outputinstallations.jsonCurrent workaround
Remain signed out of the Comfy account.
When signed out, the existing
Comfy-daoheguinstance is displayed and can be used normally.Question
Could this be related to the signed-in Dashboard / instance picker state, account-specific filtering, or the new cloud/developer-platform UI?
The key distinction is:
Please let me know if you need the full
app.log,installations.json, browser/renderer console logs, or additional diagnostic information.我建议你提交时再附两张图
第一张:未登录时显示
Comfy-daohegu的主界面。第二张:登录后显示
实例 0的主界面。这样官方开发者可以一眼看到 A/B 差异。
还有一个很重要的点:不要在 Issue 里公开你的真实 Comfy 账号邮箱。上面的报告没有放。
这个报告的结构也对应 Comfy Desktop 官方当前 Bug Report 模板要求的 App Version、Expected Behavior、Actual Behavior、Steps to Reproduce、Debug Logs 等字段。([GitHub]1) 目前
Comfy-Org/Comfy-Desktop是官方 Desktop 仓库,GitHub 页面仍提供 Issues 入口。([GitHub]2)[打开 Comfy Desktop GitHub Issues](https://github.com/Comfy-Org/Comfy-Desktop/issues?utm_source=chatgpt.com)