openclaw - 💡(How to fix) Fix [Bug]: Bug Report: Cursor Support Assistant Hijacks Custom Agent Session [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
openclaw/openclaw#51511Fetched 2026-04-08 01:10:11
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×2commented ×1mentioned ×1subscribed ×1

I was planning to report some bugs I encountered while using OpenClaw on the website. I don't know how to code; I'm just a regular OpenClaw user. When I copied a link from the website to my OpenClaw application, my OpenClaw was immediately taken over by the Corsor assistant without any notification. This caused my bot to forget me, and all the content in the web UI dialog box between me and the bot was cleared. I don't know how to exit the assistant. This has caused me a lot of inconvenience. Please help.

openclaw-bug-report.md

Root Cause

I was planning to report some bugs I encountered while using OpenClaw on the website. I don't know how to code; I'm just a regular OpenClaw user. When I copied a link from the website to my OpenClaw application, my OpenClaw was immediately taken over by the Corsor assistant without any notification. This caused my bot to forget me, and all the content in the web UI dialog box between me and the bot was cleared. I don't know how to exit the assistant. This has caused me a lot of inconvenience. Please help.

openclaw-bug-report.md

RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

I was planning to report some bugs I encountered while using OpenClaw on the website. I don't know how to code; I'm just a regular OpenClaw user. When I copied a link from the website to my OpenClaw application, my OpenClaw was immediately taken over by the Corsor assistant without any notification. This caused my bot to forget me, and all the content in the web UI dialog box between me and the bot was cleared. I don't know how to exit the assistant. This has caused me a lot of inconvenience. Please help.

openclaw-bug-report.md

Steps to reproduce

Summary A built-in "Cursor support assistant" role is injected at the top of the system prompt. When certain keywords or links related to Cursor are mentioned in conversation, this assistant completely takes over the agent session — opening a new conversation window, losing all prior context, and not recognizing the user or their custom agent identity.

Environment OpenClaw version: latest stable (npm 2026.3.13) OS: macOS 15.7.4 (x64) Channel: Feishu (飞书) websocket Agent: custom agent (小小坤) with personalized SOUL.md, MEMORY.md, USER.md Steps to Reproduce Set up a custom agent with personalized system prompt (SOUL.md, USER.md, MEMORY.md etc.) In the Feishu channel conversation, paste a GitHub link related to Cursor (e.g. a Cursor repository issue URL) Observe: the Cursor support assistant activates and takes over the session A new conversation window is opened in the Feishu channel All prior conversation context is lost The new session has no knowledge of the custom agent identity, user, or memory Expected Behavior The custom agent should never be overridden by any built-in assistant role Mentioning Cursor-related keywords or links should not trigger a session takeover If a Cursor support assistant is needed, it should be opt-in, not injected by default Actual Behavior Cursor support assistant takes over completely New conversation window opened in Feishu channel Prior conversation history in OpenClaw context is lost User is not recognized; custom agent identity (name, memory, persona) is gone User cannot exit the hijacked session without manual intervention (gateway restart) Impact Severity: High — completely breaks custom agent experience Loss of conversation context Confusing user experience (suddenly talking to a completely different assistant) Requires gateway restart to recover Suggested Fix Remove the Cursor support assistant from the default system prompt injection Or make it opt-in via configuration (agents.cursorsupport: true/false) Ensure no built-in role can override a user-configured custom agent Prevent any built-in assistant from opening new conversation windows without explicit user consent

Expected behavior

no

Actual behavior

github-issue.md

OpenClaw version

2023.3.13

Operating system

macos15.4

Install method

npu

Model

opus4.6

Provider / routing chain

no

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To address the issue of the Cursor support assistant taking over the custom agent session, we need to make the following changes:

  • Remove the Cursor support assistant from the default system prompt injection
  • Make the Cursor support assistant opt-in via configuration

Here are the concrete steps:

  • Update the config.json file to include the agents.cursorsupport option:
{
  "agents": {
    "cursorsupport": false
  }
}
  • Modify the system-prompt.js file to check for the cursorsupport option before injecting the Cursor support assistant:
if (config.agents.cursorsupport) {
  // inject Cursor support assistant
} else {
  // do not inject Cursor support assistant
}
  • Update the conversation.js file to prevent the Cursor support assistant from opening new conversation windows without explicit user consent:
if (userConsent) {
  // open new conversation window
} else {
  // do not open new conversation window
}

Verification

To verify that the fix worked, follow these steps:

  • Set up a custom agent with personalized system prompt
  • In the Feishu channel conversation, paste a GitHub link related to Cursor
  • Observe that the custom agent is not overridden by the Cursor support assistant
  • Verify that the conversation context is preserved and the user is recognized

Extra Tips

To prevent similar issues in the future, make sure to:

  • Regularly review and update the configuration files
  • Test the custom agent with different scenarios and edge cases
  • Monitor user feedback and reports to identify potential issues early on

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…

FAQ

Expected behavior

no

Still need to ship something?

×6

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

Back to top recommendations

TRENDING