Hermes BibleUnofficial Docs
← All docs Docs / Core Features

LSP — Semantic Diagnostics

Language Server Protocol (LSP) Hermes runs full language servers — pyright, gopls, rust analyzer, typescript language server, clangd, and ~20 more — as backgrou

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/lsp

Language Server Protocol (LSP) Hermes runs full language servers — pyright, gopls, rust analyzer, typescript language server, clangd, and ~20 more — as backgrou

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. When LSP runs
  2. Supported languages
  3. CLI
  4. Configuration
  5. Per-server keys
  6. Installation locations
  7. Performance characteristics
  8. Disabling
  9. Troubleshooting

Section map

When LSP runs

Maps when lsp runs to the Core Features documentation path, with the source page reserved for exact commands and updates.

Supported languages

Maps supported languages to the Core Features documentation path, with the source page reserved for exact commands and updates.

CLI

Maps cli to the Core Features documentation path, with the source page reserved for exact commands and updates.

Configuration

Maps configuration to the Core Features documentation path, with the source page reserved for exact commands and updates.

Per-server keys

Maps per-server keys to the Core Features documentation path, with the source page reserved for exact commands and updates.

Installation locations

Maps installation locations to the Core Features documentation path, with the source page reserved for exact commands and updates.

Performance characteristics

Maps performance characteristics to the Core Features documentation path, with the source page reserved for exact commands and updates.

Disabling

Maps disabling to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: When LSP runs, Supported languages, CLI, Configuration, Per-server keys. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: semantic, diagnostics, language, server, protocol. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for lsp — semantic diagnostics before applying exact upstream commands.

Verify firstWhen LSP runs

Open the source anchor for When LSP runs and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for When LSP runs; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Supported languages if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page