Chronological feed of everything captured from Cursor / Anysphere.
blog / CursorSH / May 21 / failed
blog / CursorSH / May 21 / failed
blog / CursorSH / May 21 / failed
blog / CursorSH / May 21 / failed
blog / CursorSH / May 21 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 8 / failed
tweet / @cursor_ai / May 3 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / May 1 / failed
tweet / @cursor_ai / Apr 28
GPT-5.5 is now accessible in Cursor and leads CursorBench with a 72.8% score. Cursor has partnered with OpenAI to provide this model at 50% discount until May 2. CursorBench serves as the evaluation benchmark for model performance in Cursor.
gpt-5.5cursor-aicursorbenchopenai-partnershipai-modelsmodel-benchmarking
“GPT-5.5 is available in Cursor”
tweet / @cursor_ai / Apr 28
GPT-5.5 is now accessible in Cursor and leads CursorBench with a 72.8% score. Cursor has partnered with OpenAI to provide the model at 50% discount until May 2. CursorBench serves as the evaluation benchmark for model performance in Cursor.
gpt-5.5cursor-aicursorbenchopenai-partnershipai-model-releasemodel-benchmark
“GPT-5.5 is available in Cursor”
tweet / @cursor_ai / Apr 28
Cursor 3.2 introduces /multitask for running async subagents to parallelize requests, bypassing queues by processing queued messages concurrently. Enhanced worktrees allow isolated background tasks across branches, with one-click integration to the local foreground. Multi-root workspaces support cross-repo changes in a single agent session, streamlining complex development workflows.
cursor-aimultitaskasync-subagentsworktreesmulti-root-workspacesai-coding-tools
“Cursor 3 interface supports /multitask command for async subagents to parallelize requests”
tweet / @cursor_ai / Apr 28
Cursor 3.2 adds /multitask in the new interface, enabling async subagents to parallelize requests instead of queuing them sequentially. Queued messages can be multitasked without waiting for prior runs. Enhanced worktrees allow isolated background tasks across branches, multi-root workspaces support cross-repo changes in a single agent session, and branches can be pulled into the local foreground with one click.
cursor-aimultitaskasync-subagentsworktreesmulti-root-workspacesai-coding-tools
“Cursor can run async subagents via /multitask to parallelize requests instead of queuing them”
tweet / @cursor_ai / Apr 28
Cursor 3.2 introduces multi-root workspaces, allowing a single agent session to target reusable workspaces composed of multiple folders for cross-repo changes. This builds on parallelization features like improved worktrees for isolated background tasks across branches and /multitask for async subagents. Users can download Cursor 3.2 to access these agents window enhancements.
cursor-aimulti-root-workspacesagent-sessionsworktreesmultitaskingai-coding-toolssoftware-updates
“Cursor supports multi-root workspaces for cross-repo changes”
tweet / @cursor_ai / Apr 28
Cursor 3.2 adds /multitask in the interface to run async subagents in parallel, bypassing queues for queued messages. Enhanced worktrees enable isolated background tasks across branches with one-click foreground integration. Multi-root workspaces support cross-repo agent sessions on combined folders.
cursor-aimultitaskasync-subagentsworktreesmulti-root-workspacesparallelizationai-coding-tools
“/multitask command enables async subagents to parallelize requests instead of queuing”
youtube / CursorSH / Apr 25 / failed
youtube / CursorSH / Apr 25 / failed
tweet / @cursor_ai / Apr 23 / failed
tweet / @cursor_ai / Apr 23 / failed
tweet / @cursor_ai / Apr 22 / failed
tweet / @cursor_ai / Apr 22 / failed
tweet / @cursor_ai / Apr 22 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
tweet / @cursor_ai / Apr 21 / failed
youtube / CursorSH / Apr 16 / failed
youtube / CursorSH / Apr 13
Developers are transitioning coding agents from brief 5-15 minute local runs to persistent cloud-based agents operating asynchronously for hours or days within VPCs, enabling completion of full bugs, features, or projects. This involves self-hosting private workers for extended autonomy. Executives, lacking direct experience, test AI tools on side projects and observe substantial productivity gains over traditional methods.
coding-agentsai-productivityagent-hostingcloud-agentsai-transformationexecutive-leadership
“Developers are moving coding agents from 5-15 minute tasks to hours or days-long executions completing entire bugs, features, or projects”
youtube / CursorSH / Apr 13
Cursor/Anysphere's AI coding agents are currently limited by running on only 68 15-minute intervals, creating a performance bottleneck with significant room for improvement. Coding advancements in 2025 serve as the bellwether for AI's evolution from query response to autonomous action-taking. This shift will soon extend to finance, recruiting, legal, sales, and other functions, transforming professional workflows.
cursor-aianysphereai-codingai-agent-actionsai-future-trendsproduct-evaluation
“Cursor/Anysphere runs their AI agents on only 68 intervals of 15 minutes each”