Merge pull request #167 from Jr-kenny/pr/docs-codefences

fix(docs): add missing code block language specifiers
This commit is contained in:
Teknium 2026-02-27 23:16:27 -08:00 committed by GitHub
commit 337cd574c8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
6 changed files with 13 additions and 13 deletions

View file

@ -29,7 +29,7 @@ python cli.py --gateway # Runs in foreground, useful for debugging
## Architecture Overview
```
```text
┌─────────────────────────────────────────────────────────────────┐
│ Hermes Gateway │
├─────────────────────────────────────────────────────────────────┤
@ -303,7 +303,7 @@ The gateway keeps the "typing..." indicator active throughout processing, refres
When `HERMES_TOOL_PROGRESS=true`, the bot sends status messages as it works:
```
```text
💻 `ls -la`...
🔍 web_search...
📄 web_extract...
@ -345,7 +345,7 @@ The `text_to_speech` tool generates audio that the gateway delivers as native vo
Voice and provider are configured by the user in `~/.hermes/config.yaml` under the `tts:` key. The model only sends text; it does not choose the voice.
The tool returns a `MEDIA:<path>` tag that the gateway send pipeline intercepts and delivers as a native audio message. If `[[audio_as_voice]]` is present (Opus format available), Telegram sends it as a voice bubble instead of an audio file.
The tool returns a `MEDIA:<path>` tag that the gateway sending pipeline intercepts and delivers as a native audio message. If `[[audio_as_voice]]` is present (Opus format available), Telegram sends it as a voice bubble instead of an audio file.
**Telegram voice bubbles & ffmpeg:**
@ -365,7 +365,7 @@ Cron jobs are executed automatically by the gateway daemon. When the gateway is
When scheduling cron jobs, you can specify where the output should be delivered:
```
```text
User: "Remind me to check the server in 30 minutes"
Agent uses: schedule_cronjob(
@ -389,7 +389,7 @@ Agent uses: schedule_cronjob(
The agent knows where it is via injected context:
```
```text
## Current Session Context
**Source:** Telegram (group: Dev Team, ID: -1001234567890)