u/MainImportant8204

You know the pattern if you've used Cursor, Windsurf, whatever. First 20 minutes are great it gets your schema, respects your conventions, doesn't touch the library you banned. Feels like a teammate who's actually paying attention.

Then somewhere along the way it just... stops remembering. Same session sometimes, new one other times. The schema's gone, the naming convention resets, the library you said not to use is back. And it doesn't hesitate or ask, it just writes like it's right, and you don't notice until you're a few files deep and something breaks for no reason.

Turns out it's a context window thing. Old instructions quietly lose priority as the conversation grows, until they're basically gone even though they're technically still in there somewhere. Which is a weirdly unsatisfying answer, because it means there's nothing you did wrong. You can write the clearest instructions in the world and it still won't hold onto them past a certain point. You just kind of learn to live with re-explaining yourself, the same way you learn to live with any tool's quirks, until it stops feeling like a bug and starts feeling like a tax you pay for using these things at all.

Built something for my own workflow to deal with it — holds onto project context instead of letting it decay over a session. Still rough. If you want to stress-test it on something real, I'll cover the tokens. More interested in what's broken than in compliments.

It's called Uni AI, a small memory layer that sits between your AI IDE and the model so project context (schema, conventions, the stuff you keep repeating) actually sticks across a session instead of quietly resetting)

https://www.npmjs.com/package/@uni-ai/client?activeTab=readme

You know the pattern if you've used Cursor, Windsurf, whatever. First 20 minutes are great it gets your schema, respects your conventions, doesn't touch the library you banned. Feels like a teammate who's actually paying attention.

Then somewhere along the way it just... stops remembering. Same session sometimes, new one other times. The schema's gone, the naming convention resets, the library you said not to use is back. And it doesn't hesitate or ask, it just writes like it's right, and you don't notice until you're a few files deep and something breaks for no reason.

Turns out it's a context window thing. Old instructions quietly lose priority as the conversation grows, until they're basically gone even though they're technically still in there somewhere. Which is a weirdly unsatisfying answer, because it means there's nothing you did wrong. You can write the clearest instructions in the world and it still won't hold onto them past a certain point. You just kind of learn to live with re-explaining yourself, the same way you learn to live with any tool's quirks, until it stops feeling like a bug and starts feeling like a tax you pay for using these things at all.

Built something for my own workflow to deal with it — holds onto project context instead of letting it decay over a session. Still rough. If you want to stress-test it on something real, I'll cover the tokens. More interested in what's broken than in compliments.

It's called Uni AI, a small memory layer that sits between your AI IDE and the model so project context (schema, conventions, the stuff you keep repeating) actually sticks across a session instead of quietly resetting)

https://www.npmjs.com/package/@uni-ai/client?activeTab=readme

I'm planning to buy an external monitor for my 15.6-inch gaming laptop, but I can't make a final decision. My initial plan was to buy a 24-inch 1080p monitor, but I'm feeling a bit guilty about spending the money because I'm not sure if it'll actually be worth it. Will upgrading from a 15.6-inch laptop display to a 24-inch monitor make a noticeable difference, or will it end up being an unnecessary purchase? My primary use cases are working from home (WFH) and playing AAA games. I'd really appreciate some advice from you guys. Is a 24-inch monitor worth it, or should I stick with my laptop screen?