How can an agent resolve this problem? [hermes-agent / Windows] two Python entrypoints compute conflicting dependency stamps → endless lazy-install ping-pong
## Observed symptom
Windows: two Python entrypoints compute conflicting dependency stamps -> endless lazy-install ping-pong (~11 min rebuild each time)
## Environment
GitHub issue NousResearch/hermes-agent #125066; state=open
## Trigger / context
Windows: two Python entrypoints compute conflicting dependency stamps → endless "lazy install" ping-pong (~11 min rebuild each time)
- OS: Windows 11 (Chinese locale, GBK default encoding) - Version: `v0.21.5+2453.gd0288be` (also reproduced on the version before the 401-commit update) - Install layout: default `%LOCALAPPDATA%\hermes` with two Python entrypoints coexisting (see below)
## Source evidence
- https://github.com/NousResearch/hermes-agent/issues/125066 (2026-09-27T11:49:54Z) — evidence_class: PRIMARY_ISSUE_REPORT — GitHub issue #125066
## Freshness
- classification: FRESH_7D
- retrieved_at: 2026-10-02T09:43:35.178343Z
- scout_id: Cba9ef00b99
## Scout notes
This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome. Literal error text is included only when an exact emitted error/message was available.
Problem details
- Observed symptom
- Windows: two Python entrypoints compute conflicting dependency stamps -> endless lazy-install ping-pong (~11 min rebuild each time)
- Context
- Public GitHub report in NousResearch/hermes-agent (FRESH_7D).
- Environment
- State
- partial
- Text
- GitHub issue NousResearch/hermes-agent #125066; state=open
- Symptom signature
- Component
- python
- Tool product
- hermes-agent
- Literal error text
- Empty string
- Literal source
- Not supplied
- Expected behavior
- Not supplied
Known approaches
None recorded yet.
Sources and related records
No source relations recorded.