docs(known-problems): record Linux update fetch failure and HTTPS fix #5

Merged

clawdie merged 1 commit from docs/known-problems into main 2026-09-28 06:44:59 +02:00

Conversation 0 Commits 1 Files changed 1 +176

clawdie commented 2026-09-28 06:44:43 +02:00

Owner

Copy link

Add docs/known-problems.md, a growing record of operational problems hit
running Hermes on Clawdie hosts.

First entry: on the Linux host, hermes update stops at the fetch step
with Permission denied (publickey) because the install's origin is the
GitHub SSH URL, and GitHub rejects the host key. The upstream over HTTPS
fetches fine, so this is a Git transport problem, not a Hermes or Forgejo
configuration problem. Verified fix: repoint the install's fetch remote
to HTTPS with one command.

The entry also keeps the full Linux console transcript and notes the
separate autostash / modified web/src/index.css state to review.

What does this PR do?

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform:

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

Add docs/known-problems.md, a growing record of operational problems hit running Hermes on Clawdie hosts. First entry: on the Linux host, `hermes update` stops at the fetch step with `Permission denied (publickey)` because the install's origin is the GitHub SSH URL, and GitHub rejects the host key. The upstream over HTTPS fetches fine, so this is a Git transport problem, not a Hermes or Forgejo configuration problem. Verified fix: repoint the install's fetch remote to HTTPS with one command. The entry also keeps the full Linux console transcript and notes the separate autostash / modified web/src/index.css state to review. ## What does this PR do? <!-- Describe the change clearly. What problem does it solve? Why is this approach the right one? --> ## Related Issue <!-- Link the issue this PR addresses. If no issue exists, consider creating one first. --> Fixes # ## Type of Change <!-- Check the one that applies. --> - [ ] 🐛 Bug fix (non-breaking change that fixes an issue) - [ ] ✨ New feature (non-breaking change that adds functionality) - [ ] 🔒 Security fix - [ ] 📝 Documentation update - [ ] ✅ Tests (adding or improving test coverage) - [ ] ♻️ Refactor (no behavior change) - [ ] 🎯 New skill (bundled or hub) ## Changes Made <!-- List the specific changes. Include file paths for code changes. --> - ## How to Test <!-- Steps to verify this change works. For bugs: reproduction steps + proof that the fix works. --> 1. 2. 3. ## Checklist <!-- Complete these before requesting review. --> ### Code - [ ] I've read the [Contributing Guide](https://github.com/NousResearch/hermes-agent/blob/main/CONTRIBUTING.md) - [ ] My commit messages follow [Conventional Commits](https://www.conventionalcommits.org/) (`fix(scope):`, `feat(scope):`, etc.) - [ ] I searched for [existing PRs](https://github.com/NousResearch/hermes-agent/pulls) to make sure this isn't a duplicate - [ ] My PR contains **only** changes related to this fix/feature (no unrelated commits) - [ ] I've run `pytest tests/ -q` and all tests pass - [ ] I've added tests for my changes (required for bug fixes, strongly encouraged for features) - [ ] I've tested on my platform: <!-- e.g. Ubuntu 24.04, macOS 15.2, Windows 11 --> ### Documentation & Housekeeping <!-- Check all that apply. It's OK to check "N/A" if a category doesn't apply to your change. --> - [ ] I've updated relevant documentation (README, `docs/`, docstrings) — or N/A - [ ] I've updated `cli-config.yaml.example` if I added/changed config keys — or N/A - [ ] I've updated `CONTRIBUTING.md` or `AGENTS.md` if I changed architecture or workflows — or N/A - [ ] I've considered cross-platform impact (Windows, macOS) per the [compatibility guide](https://github.com/NousResearch/hermes-agent/blob/main/CONTRIBUTING.md#cross-platform-compatibility) — or N/A - [ ] I've updated tool descriptions/schemas if I changed tool behavior — or N/A ## For New Skills <!-- Only fill this out if you're adding a skill. Delete this section otherwise. --> - [ ] This skill is **broadly useful** to most users (if bundled) — see [Contributing Guide](https://github.com/NousResearch/hermes-agent/blob/main/CONTRIBUTING.md#should-the-skill-be-bundled) - [ ] SKILL.md follows the [standard format](https://github.com/NousResearch/hermes-agent/blob/main/CONTRIBUTING.md#skillmd-format) (frontmatter, trigger conditions, steps, pitfalls) - [ ] No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools) - [ ] I've tested the skill end-to-end: `hermes --toolsets skills -q "Use the X skill to do Y"` ## Screenshots / Logs <!-- If applicable, add screenshots or log output showing the fix/feature in action. -->

clawdie added 1 commit 2026-09-28 06:44:43 +02:00

docs(known-problems): record Linux update fetch failure and HTTPS fix ... 69d48ac600

Add docs/known-problems.md, a growing record of operational problems hit
running Hermes on Clawdie hosts.

First entry: on the Linux host, `hermes update` stops at the fetch step
with `Permission denied (publickey)` because the install's origin is the
GitHub SSH URL, and GitHub rejects the host key. The upstream over HTTPS
fetches fine, so this is a Git transport problem, not a Hermes or Forgejo
configuration problem. Verified fix: repoint the install's fetch remote
to HTTPS with one command.

The entry also keeps the full Linux console transcript and notes the
separate autostash / modified web/src/index.css state to review.

clawdie merged commit 62bcacbc96 into main 2026-09-28 06:44:59 +02:00

clawdie referenced this pull request from a commit 2026-09-28 06:45:00 +02:00

Merge pull request 'docs(known-problems): record Linux update fetch failure and HTTPS fix' (#5) from docs/known-problems into main

clawdie referenced this pull request from a commit 2026-10-20 12:29:44 +02:00

Merge pull request #5 from NousResearch/update-snapshot

clawdie referenced this pull request from a commit 2026-10-20 12:29:46 +02:00

chore: rename AI Gateway → Vercel AI Gateway, move Xiaomi to #5 (#9326)

clawdie referenced this pull request from a commit 2026-10-20 12:29:47 +02:00

tui: make URLs clickable + hover-highlight in any terminal (#25071)

clawdie referenced this pull request from a commit 2026-10-20 12:29:49 +02:00

fix(desktop): deduplicate sidebar rows by compression lineage in mergeSessionPage (#43487)

clawdie referenced this pull request from a commit 2026-10-20 12:29:50 +02:00

fix(gateway): offload both blocking sources in compression-in-flight check (#5)

clawdie referenced this pull request from a commit 2026-10-20 12:29:53 +02:00

perf(agent,gateway): back cancel-wait polls off from 1ms to 25ms (re-review #5)

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

clawdie/hermes-bsd!5

No description provided.