Issue Description
While working in an existing Agent conversation, Qoder suddenly displays the following warning:
“This conversation contains sensitive content. Try switching models or start a new session.”
Once this happens, the conversation effectively stops working. The Agent no longer continues the task reliably, and attempting to continue the same conversation does not resolve the issue.
This is particularly disruptive during long-running development sessions because the conversation contains important context about code changes, testing, deployment, previous findings, and outstanding work.
There is also no indication of what content was considered sensitive, which message caused the restriction, or whether the issue is related to the user’s input, Qoder-generated output, terminal output, source code, logs, or something else.
In my case, the conversation was related to normal software development work involving production/staging verification, PWA/login issues, JavaScript files, browser testing, and deployment checks. I was not intentionally discussing or providing sensitive content.
Starting a new session means losing significant working context and creates unnecessary rework. Even with the new session the same damn messages come up after a few minutes.
Steps to Reproduce
-
Open an existing Qoder Agent conversation with a reasonably long development history.
-
Continue working normally on a software development task.
-
Allow Qoder to inspect files, execute terminal commands, review staging/production behavior, and make code changes.
-
Continue the conversation after Qoder performs multiple tool calls and code changes.
-
At some point, Qoder displays:
“This conversation contains sensitive content. Try switching models or start a new session.”
-
Attempt to continue by sending another message.
-
The conversation either stops responding properly or continues to display the sensitive-content warning.
-
Switching within the same conversation does not provide a clear recovery path, leaving the user effectively forced to start a new session.
Expected Behavior
If Qoder detects potentially sensitive content:
- The conversation should not become permanently unusable.
- Qoder should clearly identify, at least at a high level, what triggered the restriction.
- Normal source code, terminal output, server diagnostics, URLs, staging results, logs, or deployment information should not incorrectly trigger a sensitive-content block.
- If a specific message or tool output is problematic, Qoder should isolate or redact only that content rather than blocking the entire conversation.
- The user should be able to continue the existing development session after removing or skipping the problematic content.
- If switching models is required, Qoder should allow the conversation context to continue without forcing the user to recreate the entire development history.
- There should be a clear recovery option such as “Continue without this message”, “Redact sensitive content”, or “Resume with another model.”
Actual Behavior
The conversation becomes effectively blocked.
Qoder displays:
“This conversation contains sensitive content. Try switching models or start a new session.”
There is no explanation of what triggered the warning.
Continuing the conversation does not resolve the issue, and the Agent may stop responding or fail to complete the task.
The only practical option appears to be starting a new conversation, which causes loss of the active working context and forces the user to explain the project state, previous work, outstanding bugs, testing results, and deployment status again.
This is especially problematic during long Agent sessions involving many code changes.
Screenshots / Screen Recordings
Attached screenshots show:
-
The conversation working normally before the issue.
-
Qoder performing production/staging verification and code-related tasks.
-
A tool/action failure occurring during the session.
-
The message:
“This conversation contains sensitive content. Try switching models or start a new session.”
-
Attempts to continue the existing conversation after the warning.
-
The same warning continuing to appear with no obvious recovery mechanism.
Operating System
Windows 11 x64
OS Version: 10.0.26200
Current Qoder Version (Menu → About Qoder → Copy)
Qoder IDE Version: 1.27.1
VSCode Version: 1.106.3 (user setup)
Commit: fbee3cda2cb9ace9bbff189fb28a92b6f53db69
Date: 2026-08-29T10:02:31.262Z
Electron: 42.2.0
Chromium: 148.0.7778.97
Node.js: 24.15.0
V8: 14.8.178.14-electron.0
OS: Windows_NT x64 10.0.26200
Priority:
High — Blocking issue. This can make a long-running Agent development conversation unusable without warning and forces the user to recreate project context in a new session.
