Building ApogeeWatcher.com, a comprehensive performance monitoring platform designed for agencies, developers, and businesses that take their website seriously.
Cursor v2 is solid — the agent loop improvements really closed the gap. Where Claude Code pulls ahead for me is the terminal-native workflow and CLAUDE.md project memory that persists across sessions.
Building ApogeeWatcher.com, a comprehensive performance monitoring platform designed for agencies, developers, and businesses that take their website seriously.
Cursor can have project memory files as well. We keep a separate "wiki" repository with plans and decision-making logs. Plus, Cursor can search past discussions and adjust the behaviour accordingly, even if something was not noted down in a wiki file.
The wiki repo approach is smart — separating plans and decision logs from code keeps context clean. Cursor searching past discussions is essentially doing what CLAUDE.md files do for Claude Code but with implicit indexing instead of explicit structure. The trade-off is discoverability: explicit memory files are predictable but require maintenance, while searchable history is zero-effort but can surface irrelevant context. Both are valid depending on how structured your team workflow is.
The wiki repository pattern is smart. Having plans and decision logs separate from code means the model gets architectural context without parsing through implementation details. That past discussion search is something Claude Code handles differently through CLAUDE.md files and project memory but the goal is the same: persistent context that survives sessions.
Cursor Composer v2 is genuinely solid — the gap between tools is shrinking fast. The model routing idea still applies though; even Cursor lets you pick models per task, which is where the real cost savings hide.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Still on Cursor/Composer and happy with it. v2 is Opus-level.
Cursor v2 is solid — the agent loop improvements really closed the gap. Where Claude Code pulls ahead for me is the terminal-native workflow and CLAUDE.md project memory that persists across sessions.
Cursor can have project memory files as well. We keep a separate "wiki" repository with plans and decision-making logs. Plus, Cursor can search past discussions and adjust the behaviour accordingly, even if something was not noted down in a wiki file.
The wiki repo approach is smart — separating plans and decision logs from code keeps context clean. Cursor searching past discussions is essentially doing what CLAUDE.md files do for Claude Code but with implicit indexing instead of explicit structure. The trade-off is discoverability: explicit memory files are predictable but require maintenance, while searchable history is zero-effort but can surface irrelevant context. Both are valid depending on how structured your team workflow is.
The wiki repository pattern is smart. Having plans and decision logs separate from code means the model gets architectural context without parsing through implementation details. That past discussion search is something Claude Code handles differently through CLAUDE.md files and project memory but the goal is the same: persistent context that survives sessions.
Cursor Composer v2 is genuinely solid — the gap between tools is shrinking fast. The model routing idea still applies though; even Cursor lets you pick models per task, which is where the real cost savings hide.