hermes - ✅(Solved) Fix Docs: broken anchor in Nix setup page (#container-aware-cli) [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#14595Fetched 2026-04-24 06:16:07
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
Participants
Timeline (top)
labeled ×3cross-referenced ×1renamed ×1

website/docs/getting-started/nix-setup.md contains a broken in-page anchor link:

  • Link target used in the troubleshooting table: #container-aware-cli
  • No matching heading anchor exists on the page

This causes Docusaurus to report a broken anchor during docs build.

Root Cause

In website/docs/getting-started/nix-setup.md:

  • The troubleshooting table links to [Container-aware CLI](#container-aware-cli)
  • The referenced section is currently an admonition title (:::info Container-aware CLI) rather than a markdown heading, so the expected slug anchor is not generated.

Fix Action

Fixed

PR fix notes

PR #14596: docs: fix broken nix-setup anchor for container-aware CLI

Description (problem / solution / changelog)

Summary

  • fix broken in-page anchor on website/docs/getting-started/nix-setup.md
  • add a real heading ### Container-aware CLI so the existing link target #container-aware-cli resolves
  • keep the existing :::info content unchanged

Why

The troubleshooting table links to [Container-aware CLI](#container-aware-cli), but the section previously used only an admonition title (:::info Container-aware CLI) which does not generate that heading anchor.

Validation

Built docs locally from website/:

  • npm ci
  • npm run build

Result:

  • broken anchor warning for /docs/getting-started/nix-setup#container-aware-cli is gone
  • unrelated existing warning remains in /docs/user-guide/docker (./api-server.md)

Closes #14595

Changed files

  • website/docs/getting-started/nix-setup.md (modified, +3/-1)

Code Example

[WARNING] Docusaurus found broken anchors!
- Broken anchor on source page path = /docs/getting-started/nix-setup:
   -> linking to #container-aware-cli (resolved as: /docs/getting-started/nix-setup#container-aware-cli)

---

### Container-aware CLI

:::info
...
:::
RAW_BUFFERClick to expand / collapse

Summary

website/docs/getting-started/nix-setup.md contains a broken in-page anchor link:

  • Link target used in the troubleshooting table: #container-aware-cli
  • No matching heading anchor exists on the page

This causes Docusaurus to report a broken anchor during docs build.

Reproduction

  1. Clone NousResearch/hermes-agent
  2. cd website
  3. npm ci
  4. npm run build

Actual behavior

Docusaurus emits:

[WARNING] Docusaurus found broken anchors!
- Broken anchor on source page path = /docs/getting-started/nix-setup:
   -> linking to #container-aware-cli (resolved as: /docs/getting-started/nix-setup#container-aware-cli)

Expected behavior

No broken anchor warnings for /docs/getting-started/nix-setup.

Root cause

In website/docs/getting-started/nix-setup.md:

  • The troubleshooting table links to [Container-aware CLI](#container-aware-cli)
  • The referenced section is currently an admonition title (:::info Container-aware CLI) rather than a markdown heading, so the expected slug anchor is not generated.

Suggested fix

Create an actual heading before the admonition, e.g.:

### Container-aware CLI

:::info
...
:::

This generates #container-aware-cli and resolves the warning.

Notes

I also saw a separate broken link warning in /docs/user-guide/docker (./api-server.md). Kept this issue scoped only to the Nix broken anchor.

extent analysis

TL;DR

Update the nix-setup.md file to use a markdown heading for the "Container-aware CLI" section to generate the correct anchor link.

Guidance

  • Verify that the issue is resolved by checking for the absence of the broken anchor warning after running npm run build.
  • Update the nix-setup.md file as suggested in the issue, by replacing the admonition title with a markdown heading, e.g., ### Container-aware CLI.
  • Ensure that the heading text matches the link target used in the troubleshooting table.
  • Review other pages, such as /docs/user-guide/docker, for similar issues with broken links.

Example

### Container-aware CLI

:::info
...
:::

Notes

This fix assumes that the issue is limited to the nix-setup.md page and that the suggested change resolves the broken anchor warning.

Recommendation

Apply the suggested workaround by updating the nix-setup.md file to use a markdown heading for the "Container-aware CLI" section, as this directly addresses the root cause of the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

No broken anchor warnings for /docs/getting-started/nix-setup.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING