Composer 1.5 gathering someone else's context of not related project/repository

Support Bug Reports
,
1

Describe the Bug

Preconditions:

  • Unity Game Project
  • Composer 1.5 model
  • Model context: 74% used, only Unity-related, project-specific requests/prompts

Problem:

  • For some reason model started to gather context of another project/repository not related to our organization. In model’s “Thoughts” I can see that model thinks about “how to add the 4k and full HD resolution support to the project”. Subsequent prompts doesn’t fix the issue, “reapply” of the prompt too.

Result:

  • prompt is not executed, or executed incorrectly with garbage from another project/repo context
  • if prompt is reapplied model continues to work on the not related context, from someone else’s project which is not related to our project/organization at all

Example:

Prompt: Add loading token to the coordination service as a field.
Model’s Thoughts:
"I’m saving the aspect ratio setting to the cloud storage. I’m updating the aspect ratio settings in the project configuration. I’m setting the project aspect ratio to 16:9. I’m reviewing the project settings options to identify where to set the aspect ratio. I’m examining the project settings options to locate where to set the aspect ratio. I’m reviewing the project settings structure to find the correct location for aspect ratio configuration.

I’m identifying the correct project settings category and option for aspect ratio configuration. I’m searching for the correct project settings option related to aspect ratio configuration.

I’m examining the project structure to locate the aspect ratio settings option in App.tsx."

Result:
“33: 2: ILoadingContext 33: “projectSettingsOption_aspectRatio_720p”, 35: projectSettingsOption_aspectRatio_720p”, 36: projectSettingsOption_aspectRatio_36: projectSettingsOption_aspectRatio_720p", 37: projectSettingsOption_aspectRatio_720p", 36: projectSettingsOption_aspectRatio_720p", 37: projectSettingsOption_aspectRatio_720p", 39: projectSettingsOption_aspectRatio_25", 40: projectSettingsOption_aspectRatio_36: projectSettingsOption_aspectRatio_36: projectSettingsOption_aspectRatio_60", 42: projectSettingsOption_aspectRatio_720p", 36: projectSettingsOption_aspectRatio_36: projectSettingsOption_aspectRatio_720p", 37: search for settingsOption_aspectRatio_720p", 36: projectSettingsOption_aspectRatio_36: projectSettingsOption_aspectRatio_720p", 37: projectSettingsOption_aspectRatio_720p", 36: projectSettingsOption_aspectRatio", 48: projectSettingsOption_aspectRatio_720p", 48: projectSettingsOption_aspectRatio_ProjectSettingsOption_aspectRatio", 48: projectSettingsOption_aspectRatio_720p", 49: projectSettingsOption_aspectRatio_36", 51: projectSettingsOption_aspectRatio_720p", 51: projectSettingsOption_aspectRatio_720p", 51: projectSettingsOption_ascriptSettings", 52: projectSettingsOption", 52: projectSettingsTitle", 51: projectSettingsOption_aspectRatio", 86: projectSettingsOption_aspectRatio", 86: projectSettingsOption_aspectRatio", 86: pr"

Steps to Reproduce

There is no concrete steps to reproduce

Expected Behavior

Model gathers project context and executing prompt

Operating System

MacOS

Version Information

Version: 2.6.13 (Universal)
VSCode Version: 1.105.1
Commit: 60faf7b51077ed1df1db718157bbfed740d2e160
Date: 2026-03-06T06:17:49.499Z (1 wk ago)
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.3.0

For AI issues: which model did you use?

Composer 1.5

Does this stop you from using Cursor

No - Cursor works, but with this issue

4

Hey, thanks for the report.

This is a known issue. We’ve had a few similar reports where the agent picks up unrelated project context. Here are a couple related threads for reference:

A server-side fix has already been deployed for the main known cause. Two things to try:

  1. Make sure you’re on the latest Cursor version. Go to Cursor > Check for Updates. Your build (Mar 6) is from before some of the related fixes.
  2. Start a new chat when you hit this. The contaminated context can carry over within the same conversation.

If the issue still happens after updating, can you share a Request ID from one of the affected chats? Go to the top right of the chat panel, then click Copy Request ID. That’ll let us trace what happened server-side.

Let me know how it goes.

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.