hermes - 💡(How to fix) Fix [Bug]: auxiliary title generation config is hardcoded to 30s and ignores config [1 pull requests]

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…

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

Code Example

Logs contain personal information (domains, usernames etc) so I won't share it. However nothing of importance is in these logs.

---
RAW_BUFFERClick to expand / collapse

Bug Description

Problem

What happened

After a session completes, I get the message ⚠ Auxiliary title generation failed: Request timed out.. After investigating this issue, I updated the config auxiliary.title_generation.timeout to something high like 1800, and still get this issue.

Why this happens

I run local LLMs and setting context to high on qwen3.6:27b uses almost double the VRAM that I have, so the model runs very slowly.

What I expected

For the config parameter to work.

Solution

I copied what I had here into the analysis part

Steps to Reproduce

  1. Use a very slow model (would have to be local)
  2. Chat with hermes about whatever
  3. Wait about 3 minutes
  4. ⚠ Auxiliary title generation failed: Request timed out.

Expected Behavior

The title_generation uses the auxiliary.title_generation.timeout config

Actual Behavior

The title_generation does not use the auxiliary.title_generation.timeout config

Affected Component

Configuration (config.yaml, .env, hermes setup)

Messaging Platform (if gateway-related)

No response

Debug Report

Logs contain personal information (domains, usernames etc) so I won't share it. However nothing of importance is in these logs.

Operating System

Alpine Linux

Python Version

3.13.5

Hermes Version

0.14.0 (2026.5.16)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

I have identified in the code where this disconnect from the config file happens. So I can later create a pull request to fix this. In agent/title_generator.py we can trace what happens, -> maybe_auto_title -> auto_title_session -> Once we get to generate_title, we can see that auto_title_session passes no timeout to generate_title, so it defaults to 30s.

Proposed Fix (optional)

The solution is to use the auxiliary.title_generation.timeout config. I haven't checked the rest of the codebase for how using the config is implemented but it should be a simple fix.

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Bug]: auxiliary title generation config is hardcoded to 30s and ignores config [1 pull requests]