[Bug]: Error reported when created a new profile in desktop which also can't switch to the new profile

[AoJackie]

Bug Description

Steps to Reproduce

1. Start the hermes agent desktop
2. click the new profile button at bottom left
3. named the new profile, checked the clone from the default
4. click the button "Create Profile" at bottom right

Expected Behavior

1. there's no errors reported
2. the new profile can be switched with one button

Actual Behavior

1. the profile is actually created, but not worked

Affected Component

Other

Messaging Platform (if gateway-related)

No response

Debug Report

[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] 🔁 Transient APIConnectionError on alibaba — rebuilt client, waiting 6s before one last primary attempt.
[hermes] ⚠️  API call failed (attempt 1/3): APIConnectionError
[hermes]    🔌 Provider: alibaba  Model: glm-5
[hermes]    🌐 Endpoint: https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions
[hermes]    📝 Error: Connection error.
[hermes]    ⏱️  Elapsed: 0.57s  Context: 2 msgs, ~3,862 tokens
[hermes] ⏳ Retrying in 2.9s (attempt 1/3)...
[hermes] ⚠️  API call failed (attempt 2/3): APIConnectionError
[hermes]    🔌 Provider: alibaba  Model: glm-5
[hermes]    🌐 Endpoint: https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions
[hermes]    📝 Error: Connection error.
[hermes]    ⏱️  Elapsed: 3.82s  Context: 2 msgs, ~3,862 tokens
[hermes] ⏳ Retrying in 5.2s (attempt 2/3)...
[hermes] ⚠️  API call failed (attempt 3/3): APIConnectionError
[hermes]    🔌 Provider: alibaba  Model: glm-5
[hermes]    🌐 Endpoint: https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions
[hermes]    📝 Error: Connection error.
[hermes]    ⏱️  Elapsed: 9.34s  Context: 2 msgs, ~3,862 tokens
[hermes] ⚠️  API call failed (attempt 1/3): APIConnectionError
[hermes]    🔌 Provider: alibaba  Model: glm-5
[hermes]    🌐 Endpoint: https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions
[hermes]    📝 Error: Connection error.
[hermes]    ⏱️  Elapsed: 15.47s  Context: 2 msgs, ~3,862 tokens
[hermes] ⏳ Retrying in 2.3s (attempt 1/3)...
[hermes] ⚠️  API call failed (attempt 2/3): APIConnectionError
[hermes]    🔌 Provider: alibaba  Model: glm-5
[hermes]    🌐 Endpoint: https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions
[hermes]    📝 Error: Connection error.
[hermes]    ⏱️  Elapsed: 18.01s  Context: 2 msgs, ~3,862 tokens
[hermes] ⏳ Retrying in 5.3s (attempt 2/3)...
[hermes] ⚠️  API call failed (attempt 3/3): APIConnectionError
[hermes]    🔌 Provider: alibaba  Model: glm-5
[hermes]    🌐 Endpoint: https://dashscope.aliyuncs.com/compatible-mode/v1/chat/completions
[hermes]    📝 Error: Connection error.
[hermes]    ⏱️  Elapsed: 23.66s  Context: 2 msgs, ~3,862 tokens
[hermes] ❌ API failed after 3 retries — Connection error.
[hermes] 💀 Final error: Connection error.
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] ⚠️  API call failed (attempt 1/3): NotFoundError [HTTP 404]
[hermes]    🔌 Provider: nvidia  Model: deepseek-ai/deepseek-v3.2
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 404: 404 page not found
[hermes]    📋 Details: 404 page not found
[hermes]    ⏱️  Elapsed: 0.99s  Context: 10 msgs, ~4,116 tokens
[hermes] ⏳ Retrying in 2.5s (attempt 1/3)...
[hermes] ⚠️  API call failed (attempt 2/3): NotFoundError [HTTP 404]
[hermes]    🔌 Provider: nvidia  Model: deepseek-ai/deepseek-v3.2
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 404: 404 page not found
[hermes]    📋 Details: 404 page not found
[hermes]    ⏱️  Elapsed: 3.90s  Context: 10 msgs, ~4,116 tokens
[hermes] ⏳ Retrying in 5.2s (attempt 2/3)...
[hermes] ⚠️  API call failed (attempt 3/3): NotFoundError [HTTP 404]
[hermes]    🔌 Provider: nvidia  Model: deepseek-ai/deepseek-v3.2
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 404: 404 page not found
[hermes]    📋 Details: 404 page not found
[hermes]    ⏱️  Elapsed: 9.74s  Context: 10 msgs, ~4,116 tokens
[hermes] ❌ API failed after 3 retries — HTTP 404: 404 page not found
[hermes] 💀 Final error: HTTP 404: 404 page not found
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] ⚠️  API call failed (attempt 1/3): APIStatusError [HTTP 410]
[hermes]    🔌 Provider: nvidia  Model: z-ai/glm5
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 410: Error code: 410 - {'type': 'about:blank', 'title': 'Gone', 'status': 410, 'detail': "The model 'z-ai/glm5' has reached its end of life on 2026-05-18T00:00:00Z and is no longer available."}
[hermes]    📋 Details: {'type': 'about:blank', 'title': 'Gone', 'status': 410, 'detail': "The model 'z-ai/glm5' has reached its end of life on 2026-05-18T00:00:00Z and is no longer available."}
[hermes]    ⏱️  Elapsed: 0.76s  Context: 10 msgs, ~4,100 tokens
[hermes] ❌ Non-retryable error (HTTP 410): HTTP 410: Error code: 410 - {'type': 'about:blank', 'title': 'Gone', 'status': 410, 'detail': "The model 'z-ai/glm5' has reached its end of life on 2026-05-18T00:00:00Z and is no longer available."}
[hermes] ❌ Non-retryable client error (HTTP 410). Aborting.
[hermes]    🔌 Provider: nvidia  Model: z-ai/glm5
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    💡 This type of error won't be fixed by retrying.
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [updates] restart: Handing off to the Hermes updater…
[hermes] Hermes backend exited (SIGTERM)
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [updates] venv shim still locked after 15s; proceeding anyway (force)
[hermes] [updates] launched updater: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-setup.exe --update --branch main; exiting desktop to release venv shim
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [updates] restart: Handing off to the Hermes updater…
[hermes] [updates] venv shim unlocked; safe to proceed
[hermes] [updates] launched updater: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-setup.exe --update --branch main; exiting desktop to release venv shim
[hermes] Hermes backend exited (SIGTERM)
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes backend exited (SIGTERM)
[hermes] [boot] Hermes backend exited before it became ready (SIGTERM).
[hermes] [boot] Desktop boot failed: Hermes backend exited before it became ready (SIGTERM). Log: C:\Users\CNJASUN12\AppData\Local\hermes\logs\desktop.log
[hermes] [hermes] [boot] Resolving Hermes runtime
[hermes] [hermes] [boot] Hermes runtime is ready
[hermes] [hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [hermes] [boot] Waiting for Hermes backend to become ready
[hermes] [hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [hermes] [updates] restart: Handing off to the Hermes updater…
[hermes] [hermes] [updates] venv shim unlocked; safe to proceed
[hermes] [hermes] [updates] launched updater: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-setup.exe --update --branch main; exiting desktop to release venv shim
[hermes] [hermes] Hermes backend exited (SIGTERM)
[hermes] [hermes] [boot] Resolving Hermes backend
[hermes] [hermes] [boot] Finding an open local port
[hermes] [hermes] [boot] Resolving Hermes runtime
[hermes] [hermes] [boot] Hermes runtime is ready
[hermes] [hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [hermes] [boot] Waiting for Hermes backend to become ready
[hermes] [hermes] Hermes backend exited (SIGTERM)
[hermes] [hermes] [boot] Hermes backend exited before it became ready (SIGTERM).
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [file] openPath failed: Failed to open path; revealing in folder instead
[hermes] [file] openPath failed: Failed to open path; revealing in folder instead
[hermes] Hermes backend exited (1)
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] ⚠️  API call failed (attempt 1/3): BadRequestError [HTTP 400]
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    📋 Details: {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    ⏱️  Elapsed: 0.58s  Context: 30 msgs, ~37,192 tokens
[hermes] ❌ Non-retryable error (HTTP 400): HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes] ❌ Non-retryable client error (HTTP 400). Aborting.
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    💡 This type of error won't be fixed by retrying.
[hermes] ⚠️  API call failed (attempt 1/3): BadRequestError [HTTP 400]
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    📋 Details: {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    ⏱️  Elapsed: 0.41s  Context: 30 msgs, ~37,199 tokens
[hermes] ❌ Non-retryable error (HTTP 400): HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes] ❌ Non-retryable client error (HTTP 400). Aborting.
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    💡 This type of error won't be fixed by retrying.
[hermes] ⚠️  API call failed (attempt 1/3): BadRequestError [HTTP 400]
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    📋 Details: {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    ⏱️  Elapsed: 0.35s  Context: 30 msgs, ~37,205 tokens
[hermes] ❌ Non-retryable error (HTTP 400): HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes] ❌ Non-retryable client error (HTTP 400). Aborting.
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    💡 This type of error won't be fixed by retrying.
[hermes] ⚠️  API call failed (attempt 1/3): BadRequestError [HTTP 400]
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    📋 Details: {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    ⏱️  Elapsed: 0.30s  Context: 2 msgs, ~3,831 tokens
[hermes] ❌ Non-retryable error (HTTP 400): HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes] ❌ Non-retryable client error (HTTP 400). Aborting.
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    💡 This type of error won't be fixed by retrying.
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] ⚠️  API call failed (attempt 1/3): BadRequestError [HTTP 400]
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    📋 Details: {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    ⏱️  Elapsed: 0.86s  Context: 30 msgs, ~37,189 tokens
[hermes] ❌ Non-retryable error (HTTP 400): HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes] ❌ Non-retryable client error (HTTP 400). Aborting.
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    💡 This type of error won't be fixed by retrying.
[hermes] ⚠️  API call failed (attempt 1/3): BadRequestError [HTTP 400]
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    📝 Error: HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    📋 Details: {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes]    ⏱️  Elapsed: 0.39s  Context: 30 msgs, ~37,195 tokens
[hermes] ❌ Non-retryable error (HTTP 400): HTTP 400: Error code: 400 - {'status': 400, 'title': 'Bad Request', 'detail': "Function id 'f32596d4-0577-4a17-baf2-034515d1e457': DEGRADED function cannot be invoked"}
[hermes] ❌ Non-retryable client error (HTTP 400). Aborting.
[hermes]    🔌 Provider: nvidia  Model: qwen/qwen3.5-397b-a17b
[hermes]    🌐 Endpoint: https://integrate.api.nvidia.com/v1
[hermes]    💡 This type of error won't be fixed by retrying.
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup
[hermes] [boot] Resolving Hermes backend
[hermes] [boot] Finding an open local port
[hermes] [boot] Resolving Hermes runtime
[hermes] [boot] Hermes runtime is ready
[hermes] [boot] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] Starting Hermes backend via Hermes at C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent (venv: C:\Users\CNJASUN12\AppData\Local\hermes\hermes-agent\venv)
[hermes] [boot] Waiting for Hermes backend to become ready
[hermes] Hermes Web UI → http://127.0.0.1:9120
[hermes] [boot] Hermes backend is ready. Finalizing desktop startup

Operating System

Windows 11 Enterprise

Python Version

No response

Hermes Version

Hermes Agent v0.16.0 (2026.6.5) · upstream 7df3aa3

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR

[clrblind]

same

[regyang2583]

@AoJackie

Environment

OS: Windows 11(10.0.22631.6199)
Hermes Agent: v0.16.0 (2026.6.5) · upstream 484f484
Project: G:\hermes_data\hermes-agent
Python: 3.11.15
Desktop shortcut target: G:\hermes_data\scripts\launch_hermes.bat
Profile: zizi (located at G:\hermes_data\profiles\zizi)
Steps to Reproduce

Launch Hermes Desktop via desktop shortcut (launch_hermes.bat).
Log in / open the profile switcher in Desktop.
Switch to profile zizi.
Desktop shows: 設定載入失敗 / Hermes backend for profile "zizi" exited before it became ready (0).
Actual Behavior

Desktop fails to attach to the zizi backend and shows the error popup above.
The gateway process is actually alive (Scheduled Task Hermes_Gateway_zizi running), but Desktop sends an UNKNOWN planned gateway stop signal that terminates it immediately after startup.
Discord bot works fine with the same profile, confirming the gateway itself can function — only the Desktop UI cannot attach.
Key Log Evidence

程式碼
2026-06-12 04:13:56,323 INFO gateway.run: Received UNKNOWN as a planned gateway stop — exiting cleanly
2026-06-12 04:13:56,333 WARNING gateway.run: Shutdown context: signal=UNKNOWN under_systemd=no parent_pid=29144 parent_name=? loadavg_1m=? parent_cmdline='(unknown)'

[hermes] [boot] Hermes backend exited before it became ready (0).
Additional Context

The launch_hermes.bat starts gateway with hermes gateway run --replace without --profile zizi, so the Desktop (which targets profile zizi) and the background gateway may run under different profile contexts.
After the latest Desktop update, hermes doctor reported Config version outdated (v28 → v29) for the profile; hermes doctor --fix did not auto-migrate it, and manual bump to v29 did not resolve the issue.
Model misconfiguration was also observed: deepseek-ai/deepseek-v3.2 under NVIDIA NIM endpoint returns HTTP 404, and Nous Portal token was expired (HTTP 401). The model has since been corrected to nvidia/minimax-m2.7, but the Desktop bootstrap failure persists independently of model errors.
Related Issues

#43240 — exited before it became ready (SIGTERM) when creating/switching profiles
#37869 — Desktop shows remote connection failure while logs say backend is ready

[teknium1]

Thanks for the report and the follow-up environment evidence. This automated hermes-sweeper review found that the named-profile Desktop boot loop is fixed on current main.

• b1fe2107d6e02207c8d7c315e4b51d50620ecb98 fixes Desktop-managed named-profile backends being rerouted to the machine dashboard and exiting before readiness.
• Current hermes_cli/main.py:12021-12027 preserves per-profile Desktop backends when HERMES_DESKTOP=1.
• tests/hermes_cli/test_dashboard_unified_launch.py:124-145 covers the regression explicitly.
• Current Desktop creation flow refreshes then selects the new profile (apps/desktop/src/app/chat/sidebar/profile-switcher.tsx:308-315), while apps/desktop/src/store/profile.ts:301-314 opens its profile-scoped gateway backend.

The fix is contained in release tag v2026.6.19.