# "i see the issue" from the ai

**URL:** <https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060>\
**Category:** Feedback\
**Created:** [January 4, 2025, 7:51am UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060 "2025-01-04T07:51:26Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![john-savepoint](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/john-savepoint/32/15998_2.png) [@john-savepoint](https://forum.cursor.com/u/john-savepoint)\
**Post date:** [January 4, 2025, 7:51am UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/1 "2025-01-04T07:51:26Z")

</div>

No you don’t Cursor AI. I am so sick of seeing this “I see the issue” when it is not addressing it at all.

I think the biggest issue is the context especially in composer. In composer there is no codebase button, but composer really should be having full context all the time, and there should be a toggle in the less use case of needing limited context.

Chat is where I think limited context is more appropriate

---

<div class="post-metadata">

**Author:** ![jake](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jake/32/20459_2.png) [@jake](https://forum.cursor.com/u/jake)\
**Post date:** [January 6, 2025, 2:25am UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/2 "2025-01-06T02:25:57Z")

</div>

Choosing the right context is a hard problem to solve. I’m certain the Cursor team are working on this. But until then, if you’re aware of what files are pertinent, especially after a long chat/composer session, I find it’s useful to start a new chat/composer and directly @ those files.

This can cut out a huge amount of noise from longer chat sessions, and often results in the LLM _actually_ being able to identify the issue.

---

<div class="post-metadata">

**Author:** ![john-savepoint](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/john-savepoint/32/15998_2.png) [@john-savepoint](https://forum.cursor.com/u/john-savepoint)\
**Post date:** [January 6, 2025, 1:37pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/3 "2025-01-06T13:37:55Z")

</div>

Yes I do currently employ these tactics that you have recommended. And they are good enough work arounds for the problem but that’s what they are work arounds.  
I love Cursor don’t get me wrong but it’s got a while to go yet with the application let alone the supporting LLMs.

---

<div class="post-metadata">

**Author:** ![RenjiYuusei](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/renjiyuusei/32/22500_2.png) [@RenjiYuusei](https://forum.cursor.com/u/RenjiYuusei)\
**Post date:** [January 6, 2025, 1:42pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/4 "2025-01-06T13:42:24Z")

</div>

> [@john-savepoint](#):
>
> In composer there is no codebase button

Which mode are you using? Normal mode has @codebase Agents mode doesn’t have @codebase

---

<div class="post-metadata">

**Author:** ![jake](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jake/32/20459_2.png) [@jake](https://forum.cursor.com/u/jake)\
**Post date:** [January 6, 2025, 1:57pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/5 "2025-01-06T13:57:58Z")

</div>

It’s a new product in a rapidly developing space. They’re shipping fast and listening to user feedback. Give them time ~:)

---

<div class="post-metadata">

**Author:** ![john-savepoint](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/john-savepoint/32/15998_2.png) [@john-savepoint](https://forum.cursor.com/u/john-savepoint)\
**Post date:** [January 6, 2025, 3:27pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/6 "2025-01-06T15:27:16Z")

</div>

Ah, Im using agent all the time which is why? But sometimes it feels like it is lacking context. It greps stuff but not all the time. Thank you.

---

<div class="post-metadata">

**Author:** ![john-savepoint](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/john-savepoint/32/15998_2.png) [@john-savepoint](https://forum.cursor.com/u/john-savepoint)\
**Post date:** [January 6, 2025, 3:28pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/7 "2025-01-06T15:28:15Z")

</div>

Totally understand. Im not throwing them under the bus, very happy, and the updates do come regularly.

---

<div class="post-metadata">

**Author:** ![RenjiYuusei](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/renjiyuusei/32/22500_2.png) [@RenjiYuusei](https://forum.cursor.com/u/RenjiYuusei)\
**Post date:** [January 6, 2025, 3:35pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/8 "2025-01-06T15:35:16Z")

</div>

You have to give it enough context.

---

<div class="post-metadata">

**Author:** ![SoMaCoSF](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/somacosf/32/14963_2.png) [@SoMaCoSF](https://forum.cursor.com/u/SoMaCoSF)\
**Post date:** [January 6, 2025, 3:41pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/9 "2025-01-06T15:41:48Z")

</div>

I find I regularly forget that I have an @[file] in my agentic chat window… is this forcing the agetn to constantly think that they attached @ link is still relevant, even if I have changed my context of thought?

What would be nifty, is a little “context bucket”(s)

Like TAGs for context – like…

For example - what if we had a _context versioning_ system - whereby within the scope of a project we have an OSI of contexts::

login  
user  
db  
front\_end  
back\_end  
etc…

as parts of the system/stack – and when we call a stack context ‘&back\_end’ → sets auto-\_context\_focus on all the components and files associated with '&back\_end’s context…

Then when we document the system we can tell the bot "give me a detailed .rmd for &back\_end and how &user flows through backend (showing how say a users requests to make a post traces through the system to populate a DB entry and displaey to & front\_end…

(thinking out my e\_dibles here… so humor me.

I am thinking about holographic symbols for context/even code functions as a ‘QR\_Code’ for context/persona/archetype/perspective

 ![](https://us1.discourse-cdn.com/cursor1/original/3X/1/b/1b2d3c9821ba506beb899e9d31272ab27fa2c287.png)  
Based on the idea of Postres Watermakring for sync rep - as applied to the idea of vector context windows and agentic behavior:

(came from this read:

> **[Using watermarks to coordinate change data capture in Postgres](https://blog.sequinstream.com/using-watermarks-to-coordinate-change-data-capture-in-postgres/)**
>
> In change data capture, consistency is paramount. A single missing or duplicate message can cascade into time-consuming bugs and erode trust in your entire system. The moment you find a record missing in the destination, you have to wonder: is this...

* * *

```auto
class ContextualWatermark:
    def __init__ (self):
        self.vector_space = VectorSpace(dimensions=512) # Embedding space
        self.context_buffer = []
        self.watermarks = []
        
    def create_watermark(self, context_state):
        """Creates a quantum-inspired watermark for current context"""
        # Embed current context into vector space
        context_vector = self.vector_space.embed(context_state)
        
        # Create interference pattern with previous contexts
        interference = self.compute_interference(context_vector)
        
        # Generate holographic watermark
        watermark = {
            'vector': context_vector,
            'interference': interference,
            'timestamp': time.time(),
            'context_hash': self.hash_context(context_state)
        }
        
        self.watermarks.append(watermark)
        return watermark
    
    def compute_interference(self, vector):
        """Computes quantum-like interference with existing contexts"""
        interference = np.zeros_like(vector)
        for past_mark in self.watermarks[-5:]: # Consider recent history
            # Complex-valued interference pattern
            interference += self.quantum_interference(vector, past_mark['vector'])
        return interference
    
    def retrieve_context(self, query_vector, depth=3):
        """Retrieves relevant past context using holographic principles"""
        # Project query into vector space
        query_embedding = self.vector_space.embed(query_vector)
        
        # Find resonating watermarks
        resonances = []
        for mark in self.watermarks:
            # Compute resonance using quantum similarity
            resonance = self.compute_resonance(query_embedding, mark)
            resonances.append((resonance, mark))
            
        # Sort by resonance strength and return top matches
        relevant_marks = sorted(resonances, key=lambda x: x[0], reverse=True)[:depth]
        return self.reconstruct_context(relevant_marks)
    
    def compress_history(self):
        """Compresses history while preserving retrievability"""
        # Group similar contexts using quantum clustering
        clusters = self.quantum_cluster(self.watermarks)
        
        # Create superposition states for each cluster
        compressed = []
        for cluster in clusters:
            superposition = self.create_superposition(cluster)
            compressed.append(superposition)
            
        # Update watermarks with compressed version
        self.watermarks = compressed
        return compressed

class VectorSpace:
    def __init__ (self, dimensions):
        self.dimensions = dimensions
        self.basis_vectors = self.initialize_basis()
    
    def embed(self, data):
        """Embeds data into vector space using quantum-inspired encoding"""
        # Implementation would use advanced embedding techniques
        pass
    
    def initialize_basis(self):
        """Creates basis vectors for the semantic space"""
        # Implementation would define the vector space structure
        pass

```

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [January 7, 2025, 5:27pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/10 "2025-01-07T17:27:15Z")

</div>

The agent mode of AI does sometimes need prompting to look at the folder structure.

This is especially the case in big projects or big conversations where the AI may assume it has all the context it needs from the previous conversation, so it doesn’t want to use a tool call to look up the project structure again or look inside any files that it feels it already knows about.

As others have said, we are working hard on this as context is the key for really good responses from even small models. But it’s a tough one to perfect right now.

As time goes on I’m sure this will get better. But the suggestions above are the best workarounds for now!

---

<div class="post-metadata">

**Author:** ![john-savepoint](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/john-savepoint/32/15998_2.png) [@john-savepoint](https://forum.cursor.com/u/john-savepoint)\
**Post date:** [January 8, 2025, 3:50am UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/12 "2025-01-08T03:50:58Z")

</div>

Continuing the discussion from [I see the issue 🤬](https://forum.cursor.com/t/i-see-the-issue/39060/11):

I dont know how hard it is to implement but possibly an “acquired context” button you can press that shows you all of the files, folders, snippets, docs etc that you have provided for context and a weighting it has in the upcoming prompt.

eg. you press “acquired context”  
it shows:  
file3.md | uploaded 1 prompt ago | 0.95 weight  
file1.js | uploaded 2 prompts ago | 0.75 weight  
file2.pdf | uploaded 10 prompts ago | 0.1 weight

This way we can see everything that we have provided it and what it is still taking into consideration and if we need to provide the context files again To essentially wake it up and use the most recent text or at least minimise the amount of hallucination.

It seems like the cursor indexing does a similar thing when you provide full codebase context.

I might not understand LLM but this is how it feels in use, If you provide a contextual file it seems to become less and less accurate or used over proceeding prompts.

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [January 8, 2025, 7:39pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/13 "2025-01-08T19:39:24Z")

</div>

It’s unfortunately not quite that simple about how the context works behind the scenes, as it changes between every prompt you ask. But I agree that more visibility is not a bad thing here!

---

<div class="post-metadata">

**Author:** ![Signal](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/signal/32/18633_2.png) [@Signal](https://forum.cursor.com/u/Signal)\
**Post date:** [January 10, 2025, 2:22pm UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/14 "2025-01-10T14:22:19Z")

</div>

I made a similar complaint a while ago but I was advised to write “better prompts” even though I knew the issue is way deeper than that. Sometimes you give explicit instructions for it to follow but still won’t adhere. When you ask it why, it says “I’m sorry I should’ve followed…” Cursor is simply not good enough for complex projects yet and I appreciate the fact that the developers are working towards making it better.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 18, 2026, 10:24am UTC](https://forum.cursor.com/t/i-see-the-issue-from-the-ai/39060/15 "2026-06-18T10:24:04Z")

</div>


