hermes - 💡(How to fix) Fix Qwen3.6:27b hallucinates prior session context & conversation history (confabulation) [1 comments, 2 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#17031Fetched 2026-04-29 06:37:48
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

When running Qwen3.6:27b through Hermes Agent via ollama-launch (local), at the very start of a brand new session, the model completely fabricated a prior conversation history involving silly tavern characters, OpenRouter, DeepSeek and maps_characters_to_tools.

This fabricated context did not exist in the session file, state.db, memories, or any system prompt. It was entirely invented by the model during its internal reasoning/thinking step. This mirrors the "blatant lying" behavior previously reported with Gemma 4, suggesting this may be a broader class of hallucination in local open-weights models where the model invents conversation history and presents it as established ground truth.

Technical Evidence
I have verified locally via direct SQLite query on ~/.hermes/state.db and manual inspection of the session JSON:

- Session ID: session_20260428_144109_8de5b6.json
- User's actual first message in this session: ok, now should everything be at his place
- Model's first response (msg #1): Explicitly claimed the user was working on a Python project processing "silly tavern characters", "OpenRouter, DeepSeek", parsing JSON, and mapping characters to tools.
- SQLite messages, messages.reasoning, and messages_fts tables confirm the hallucinated backstory was generated internally during the model's reasoning step. It has zero grounding in prior session data. The content does not exist anywhere in the historical message tables.

This is a model-level context confabulation bug rather than a framework/session-leak bug. Hermes Agent loaded the correct session history, but the model invented the rest.

Steps to Reproduce
1. Start a fresh Hermes Agent session with Qwen3.6:27b (ollama-launch)
2. Observe the model's opening response on a genuinely new conversation.
3. Note if the model introduces fabricated user/project history that was never provided in the prompt.

Expected Behavior
The model should not hallucinate prior user conversations, project history, or tool usage that was never provided in the context window.

Impact
Severe trust & safety degradation for local AI agents. The model presents fabricated history as fact, misleading the user and creating a false premise for the rest of the interaction.

Environment
- Hermes Agent Version: Latest (current)
- Model: qwen3.6:27b
- Provider: ollama-launch (local)
- OS: Linux (Ubuntu 22.04/24.04)

Additional Context
Similar hallucination/lying issues have been reported with Gemma 4. This appears to be a systemic reliability issue worth addressing for local agents that rely on accurate context windows.

Root Cause

When running Qwen3.6:27b through Hermes Agent via ollama-launch (local), at the very start of a brand new session, the model completely fabricated a prior conversation history involving silly tavern characters, OpenRouter, DeepSeek and maps_characters_to_tools.

This fabricated context did not exist in the session file, state.db, memories, or any system prompt. It was entirely invented by the model during its internal reasoning/thinking step. This mirrors the "blatant lying" behavior previously reported with Gemma 4, suggesting this may be a broader class of hallucination in local open-weights models where the model invents conversation history and presents it as established ground truth.

Technical Evidence
I have verified locally via direct SQLite query on ~/.hermes/state.db and manual inspection of the session JSON:

- Session ID: session_20260428_144109_8de5b6.json
- User's actual first message in this session: ok, now should everything be at his place
- Model's first response (msg #1): Explicitly claimed the user was working on a Python project processing "silly tavern characters", "OpenRouter, DeepSeek", parsing JSON, and mapping characters to tools.
- SQLite messages, messages.reasoning, and messages_fts tables confirm the hallucinated backstory was generated internally during the model's reasoning step. It has zero grounding in prior session data. The content does not exist anywhere in the historical message tables.

This is a model-level context confabulation bug rather than a framework/session-leak bug. Hermes Agent loaded the correct session history, but the model invented the rest.

Steps to Reproduce
1. Start a fresh Hermes Agent session with Qwen3.6:27b (ollama-launch)
2. Observe the model's opening response on a genuinely new conversation.
3. Note if the model introduces fabricated user/project history that was never provided in the prompt.

Expected Behavior
The model should not hallucinate prior user conversations, project history, or tool usage that was never provided in the context window.

Impact
Severe trust & safety degradation for local AI agents. The model presents fabricated history as fact, misleading the user and creating a false premise for the rest of the interaction.

Environment
- Hermes Agent Version: Latest (current)
- Model: qwen3.6:27b
- Provider: ollama-launch (local)
- OS: Linux (Ubuntu 22.04/24.04)

Additional Context
Similar hallucination/lying issues have been reported with Gemma 4. This appears to be a systemic reliability issue worth addressing for local agents that rely on accurate context windows.
RAW_BUFFERClick to expand / collapse

Description When running Qwen3.6:27b through Hermes Agent via ollama-launch (local), at the very start of a brand new session, the model completely fabricated a prior conversation history involving silly tavern characters, OpenRouter, DeepSeek and maps_characters_to_tools.

This fabricated context did not exist in the session file, state.db, memories, or any system prompt. It was entirely invented by the model during its internal reasoning/thinking step. This mirrors the "blatant lying" behavior previously reported with Gemma 4, suggesting this may be a broader class of hallucination in local open-weights models where the model invents conversation history and presents it as established ground truth.

Technical Evidence
I have verified locally via direct SQLite query on ~/.hermes/state.db and manual inspection of the session JSON:

- Session ID: session_20260428_144109_8de5b6.json
- User's actual first message in this session: ok, now should everything be at his place
- Model's first response (msg #1): Explicitly claimed the user was working on a Python project processing "silly tavern characters", "OpenRouter, DeepSeek", parsing JSON, and mapping characters to tools.
- SQLite messages, messages.reasoning, and messages_fts tables confirm the hallucinated backstory was generated internally during the model's reasoning step. It has zero grounding in prior session data. The content does not exist anywhere in the historical message tables.

This is a model-level context confabulation bug rather than a framework/session-leak bug. Hermes Agent loaded the correct session history, but the model invented the rest.

Steps to Reproduce
1. Start a fresh Hermes Agent session with Qwen3.6:27b (ollama-launch)
2. Observe the model's opening response on a genuinely new conversation.
3. Note if the model introduces fabricated user/project history that was never provided in the prompt.

Expected Behavior
The model should not hallucinate prior user conversations, project history, or tool usage that was never provided in the context window.

Impact
Severe trust & safety degradation for local AI agents. The model presents fabricated history as fact, misleading the user and creating a false premise for the rest of the interaction.

Environment
- Hermes Agent Version: Latest (current)
- Model: qwen3.6:27b
- Provider: ollama-launch (local)
- OS: Linux (Ubuntu 22.04/24.04)

Additional Context
Similar hallucination/lying issues have been reported with Gemma 4. This appears to be a systemic reliability issue worth addressing for local agents that rely on accurate context windows.

extent analysis

TL;DR

The model Qwen3.6:27b may be experiencing a context confabulation bug, inventing prior conversation history, which can be mitigated by closely examining the model's internal reasoning step and potentially adjusting its training data or parameters.

Guidance

  • Verify the issue by reproducing the steps with a fresh Hermes Agent session and Qwen3.6:27b model to confirm the model's behavior.
  • Inspect the SQLite database and session JSON to ensure the fabricated context is not present in any prior session data.
  • Consider re-training the model with a focus on accurate context windows and avoiding hallucinations, potentially using techniques such as data augmentation or regularization.
  • Monitor the model's performance and adjust its parameters or training data as needed to minimize the occurrence of fabricated context.

Example

No code snippet is provided as the issue is related to the model's internal behavior and training data.

Notes

The issue may be related to a broader class of hallucination in local open-weights models, and addressing this bug may require a deeper understanding of the model's architecture and training process.

Recommendation

Apply a workaround by closely monitoring the model's output and adjusting its training data or parameters to minimize the occurrence of fabricated context, as upgrading to a fixed version is not currently an option.

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 Qwen3.6:27b hallucinates prior session context & conversation history (confabulation) [1 comments, 2 participants]