Skip to content

[Bug]: Hermes Studio auto-update misses pip dependencies in embedded Python runtime (2nd occurrence) #64079

Description

@zhengzhangerp-oss

Summary

Hermes Studio auto-updates leave the new embedded Python runtime missing pip dependencies, causing silent failures. This is the second occurrence of the same class of bug (v9: missing .py source file, v10: missing pip package).

Environment

Item Value
OS Windows 10 Pro
Hermes Studio 0.6.29
Embedded runtime 0.18.2 (auto-upgraded from 0.17.0)
hermes-agent CLI 0.18.0
Affected provider minimax-cn (transport: anthropic_messages)
Unaffected provider deepseek (transport: openai_chat)

Root Cause

Hermes Studio's desktop runtime (~/.hermes-web-ui/desktop-runtime/hermes/{version}/win-x64/python/) is an independent Python environment, completely isolated from the CLI venv. When Studio performs a major version upgrade, the new runtime directory is created but pip dependencies are NOT synced.

This is the second occurrence (v9: missing source file, v10: missing pip package). Both share the same root cause.

Proposed Fix

  1. Short-term: Add a dependency integrity check on Studio startup, auto-triggering pip install when packages are missing
  2. Long-term: Add a pip sync step to the Studio version upgrade process

Workaround

$RT = "$env:USERPROFILE\.hermes-web-ui\desktop-runtime\hermes\{version}\win-x64\python\python.exe"
& $RT -m pip install anthropic==0.87.0
Remove-Item -Recurse -Force "$env:USERPROFILE\.hermes-web-ui\desktop-runtime\hermes\{version}\win-x64\python\Lib\site-packages\anthropic\__pycache__"
# Restart Hermes Studio

CVE note: pyproject.toml and lazy_deps.py pin anthropic==0.87.0 due to CVE-2026-34450 and CVE-2026-34452.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Medium — degraded but workaround existsarea/configConfig system, migrations, profilescomp/desktopElectron desktop app (apps/desktop/*)platform/windowsNative Windows-specific behavior or breakagesweeper:implemented-on-mainSweeper: behavior already present on current mainsweeper:risk-compatibilitySweeper risk: may break existing users, config, migrations, defaults, or upgradessweeper:risk-platform-windowsSweeper risk: may break or behave differently on native Windowstype/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions