Composer History, @Lint Errors, VS Code 1.93.1
read at source ↗ cursor.com
Composer History, @Lint Errors, VS Code 1.93.1
Source: Cursor Date: 2024-10-09 URL: https://cursor.com/changelog/0-42-x
Summary
Cursor 0.42.x restores Composer history (access and resubmit previous sessions after restart), restores @Lint Errors in Chat, and adds model search (cmd+option+/) for quick model switching across all input surfaces. VS Code 1.93.1 base, Python auto-import stability improvements, Composer restricted to context-aware file applications. Two CVEs patched (CVE-2024-43601, CVE-2024-48919).
Implications
Agent-IDE feature race. Composer history (persistent session access across restarts) is a precursor to the Memories system that ships later — Cursor is building session continuity incrementally. Model search with a single keyboard shortcut for switching across chat, Composer, and cmd-K makes model selection frictionless; this is UX infrastructure for the multi-model-per-task patterns that become explicit in 1.4.
Model integration cadence. The CVE patches (two in one release) signal Cursor is moving through security audits at scale — the VS Code base has known vulnerabilities and Cursor must track them. This is the operational overhead of forking VS Code and is a recurring cost that smaller VS Code extension approaches (GitHub Copilot, Windsurf’s early form) avoid.