Cursor lands in Microsoft Teams

This turns Teams from a discussion layer into an agent dispatch layer, which is the right direction for enterprise AI workflows.

• –The full-thread context pass is the key detail here; it reduces the usual “missing context” failure mode in chat-driven automation
• –Auto-selecting repo and model from prompt plus recent agent activity suggests Cursor is optimizing for low-friction handoff, not manual setup
• –PR generation makes the output reviewable by default, which matters more in Teams than a raw chat response
• –The move broadens Cursor beyond the IDE into the collaboration surface where a lot of work actually gets assigned
• –This is most compelling for organizations already standardized on Microsoft 365 and looking to route internal requests into coding agents