Hey, that’s a familiar pain point, it comes up pretty regularly. There’s a fresh thread exactly about this where users share approaches, take a look: How are people handling context across different AI coding tools?
If we’re talking about Cursor specifically, part of your list who you are, response style, what you hate, project goals can be moved out of your head into:
- User Rules: personal preferences that apply to all projects. This is where things like no fluff, no over explaining basics, and your style live.
- AGENTS.md / Project Rules in
.cursor/rules: project specific context like architecture, agreed decisions, what you’ve already tried and rejected. You can keep it right in the repo so it’s versioned and doesn’t get lost between sessions. Docs: Rules | Cursor Docs
Since the rules live in files inside the project, it’s easy to reuse them outside Cursor too, it’s your data and not tied to any one provider.
For more “live” memory across sessions, the community often hooks up MCP servers for persistent memory. See examples in these threads: Recall — open MCP memory pattern that survives across Cursor sessions and Persistent memory for Cursor that survives every session — .brain/ folder approach. The approaches vary, you can borrow ideas for your case.
So no, you’re not the only one with this pain. If you decide to build an open source project, share it, users here like discussing that.