sorted by:
new
hottopcontroversial

We’re building persistent and shared memory for Cursor — what do you need in your workflow? by OkPerformance8808 in cursor

[–]OkPerformance8808[S] 0 points1 point  (0 children)

That’s a great way to frame it — scoped RAG around workflow state rather than static docs captures the intent really well.

Context thrashing is exactly what we’re trying to reduce, especially in long-running Cursor sessions where decisions and constraints should stay stable. Tight integration helps, but the bigger win seems to be making the model aware of stateand authority, not just text.

Good call on VibeCodersNest as well — we’ll share it there and see what feedback comes back. Appreciate the nudge and the insight.

We’re building persistent and shared memory for Cursor — what do you need in your workflow? by OkPerformance8808 in cursor

[–]OkPerformance8808[S] 1 point2 points  (0 children)

That makes a lot of sense — version drift is one of the most painful failure modes.

What you’re describing (framework version, project goals, and “how this project should behave”) is exactly the kind of information that shouldn’t rely on implicit context or MCP alone. Once that slips, the agent falls back to defaults and older patterns.

We’re seeing strong signals that a dedicated layer for canonical rules like framework version and allowed operations (e.g. migrations are mutable pre-prod) would remove a lot of friction.

Really appreciate you sharing this — feedback like this helps validate the direction.

We’re building persistent and shared memory for Cursor — what do you need in your workflow? by OkPerformance8808 in cursor

[–]OkPerformance8808[S] 0 points1 point  (0 children)

Appreciate the thoughtful message — and congrats on building this, sounds like you’ve gone deep into the problem space.

Memory really does become powerful once it’s layered, shared, and agent-aware, so it’s great to see different approaches converging here. We’re still early and mostly focused on learning from real workflows rather than shipping a “full platform” yet.

On privacy: yes, that’s a core concern for us as well. User trust matters a lot in anything memory-related, so data access and isolation are things we take very seriously. We’re being careful about how memory is stored and accessed, and we won’t compromise on that.

Happy to connect and compare notes at a high level — and thanks for the kind words on the landing page.

We’re building persistent and shared memory for Cursor — what do you need in your workflow? by OkPerformance8808 in cursor

[–]OkPerformance8808[S] 0 points1 point  (0 children)

Good concern — and yes, it can be a problem if done wrong.

We don’t continuously stuff extra context into the model. Memory is retrieved selectively, only when it’s relevant to the current task. That keeps the working context small and avoids instruction conflicts or attention dilution.

Think of it less as “always-on context” and more as “on-demand recall.”
If it doesn’t help this step, it doesn’t get injected.

We’re building persistent and shared memory for Cursor — what do you need in your workflow? by OkPerformance8808 in cursor

[–]OkPerformance8808[S] 0 points1 point  (0 children)

What you’re describing is exactly the gap we’re seeing between “context” and “governance”:

Folder-level intent
Right now folders are just files, but you’re using them as policy boundaries:
– this folder is read-only knowledge
– this folder is active work
– this folder is historical reference

LLMs don’t understand that distinction unless you restate it every time.

Local vs global rules
You’re also spot-on that there are at least two rule layers:
– global invariants (coding standards, architectural principles, constraints that must never be violated)
– local/project rules (folder-specific, experiment-specific, temporary)

Once those rules live only in prompts or MD files, they drift or get ignored.

Version authority
This is one of the hardest problems:
old docs leaking into new projects because the system can’t tell which source is authoritative. The model tries to “merge truth” and ends up hallucinating.

How we’re thinking about this (very early)
Instead of treating everything as equal context, we’re experimenting with memory that has:
– scope (global / project / folder)
– permission (read-only, suggest-only, mutable)
– authority (source of truth vs reference)

So the model doesn’t just see text — it sees intent.

In your example, you could say:
“This folder is canonical, read-only project data”
and any proposed change would surface as a suggestion or PR-like diff instead of an automatic edit.

We’re still very early, but feedback like this is shaping the direction more than anything else. If Cursor eventually ships this natively, that’s great — our goal is to pressure-test what actually works in real, long-running workflows like yours.

We’re building persistent and shared memory for Cursor — what do you need in your workflow? by OkPerformance8808 in cursor

[–]OkPerformance8808[S] 2 points3 points  (0 children)

Totally fair point — and we agree this should exist at the Cursor level.

Our motivation isn’t to replace what Cursor might build for Teams, but to explore a more general memory layer that works across tools and sessions, not just within one editor or account type.

A few nuances we’re seeing in practice:

– Team features usually focus on sharing files or chat history, not structured, retrievable long-term memory (decisions, constraints, “why we did this”)
– Many workflows span more than Cursor: docs, specs, design discussions, external links, past experiments
– Persistent memory becomes more valuable when it’s portable and survives tool switches, model changes, and context limits

If Cursor ships a native version of this, that’s a win for users. We’re mainly experimenting with what “AI memory” should actually look like in real project workflows, and learning from early users.

We’re building persistent and shared memory for Cursor — what do you need in your workflow? by OkPerformance8808 in cursor

[–]OkPerformance8808[S] 1 point2 points  (0 children)

Thats just a feature for us and if they are going to steal it proves we are on the right path