Cursor 1.5 vs oh-my-codex

“The primitive here is asynchronous agent execution decoupled from IDE focus — finally, you can kick off a refactor or test-writing task and context-switch without the whole thing dying. The DX bet is correct: the complexity is hidden in the runtime, not pushed onto the developer via config or orchestration boilerplate. The moment of truth is queuing a multi-file task, closing the tab, and coming back to a diff — and apparently it survives that test. Shared team rules is the feature that actually earns the enterprise tier: replacing the tribal knowledge of per-developer .cursorrules files with a versioned, shared config is the kind of mundane-but-real problem that unlocks actual team adoption. The autocomplete latency improvement is the only claim I'd want benchmarks on before citing it.”

“This is the right abstraction layer — repo-level AI hooks that work regardless of what editor you're in. The HUD is surprisingly polished for an indie project. I can see this becoming a standard part of the dotfiles setup for developers who work across multiple editors.”

“Background agent execution is the one feature that separates Cursor from GitHub Copilot in a meaningful, non-cosmetic way — Copilot hasn't shipped async task delegation at the IDE level, and that gap is real enough to matter today. The scenario where this breaks is multi-repo or monorepo tasks that cross service boundaries: background agents operating on partial context without a human in the loop will produce confident wrong diffs, and the memory panel won't save you there. What kills this in 12 months isn't a competitor — it's OpenAI or Anthropic shipping native IDE integrations with the same async primitive baked into their own tooling, collapsing the moat. But right now, the team rules feature alone justifies the Business tier for any eng team above 10 people, so this ships.”

“The hooks and agent teams concept is compelling but the execution feels early. Agent teams with no guardrails running on every commit is a recipe for noise and unintended changes. Until there's robust configuration for when NOT to fire agents, this needs careful testing before use on anything production-adjacent.”

“The buyer here is clear: VP Eng or CTO at a 20-200 person company, paid from the dev tooling budget, justified by reduced context-switching cost and standardized AI behavior across the team. Shared team rules is the expansion revenue mechanism — it's the feature that converts individual Pro subscribers into Business accounts, and that's a real land-and-expand wedge built into the product itself rather than bolted on by a sales team. The moat question is harder: Anysphere's defensibility depends on workflow lock-in through memory and rules accumulation, which gets stickier the longer a team uses it, but the underlying model access is still commoditized. The risk is that VS Code's own AI layer catches up fast enough that the switching cost never fully sets. For now, the unit economics on the Business tier are credible.”

“The thesis Cursor 1.5 is betting on: within two years, developers will manage fleets of concurrent async coding tasks rather than typing code themselves, and the IDE becomes a task dispatcher rather than a text editor. Background agent execution is the first real infrastructure bet on that trajectory — not a demo, an actual runtime change. The dependency that has to hold is that agents remain good enough to be trusted with multi-step tasks but not so good that the IDE layer becomes irrelevant entirely; Cursor is threading a specific needle in that window. The second-order effect nobody is talking about: shared team rules start to function as organizational AI policy, meaning the eng team — not IT, not legal — becomes the de facto owner of how AI behaves in the codebase. That's a power shift worth watching. Cursor is early on the async-agent trend line and building the right primitives for it.”

“The HUD pattern — a live display of autonomous agents working in your codebase — is a glimpse at how software development will feel in two years. When agents are good enough to be trusted, you'll want exactly this: a terminal showing what they're doing while you think about the next problem.”

“I'd use the hooks to auto-update documentation on every commit and have the HUD show me what changed in plain English. The editor-agnostic approach means it works the same whether I'm in Cursor, Zed, or vim — that flexibility matters a lot for creative workflows.”