Feature request for product/service
– Other –
Describe the request
I’d love to propose an idea that I think could become a natural extension of Cursor.
Today, Cursor is exceptional once an engineer starts coding. However, a lot of engineering work begins in meetings, where requirements, architecture, trade-offs, and task assignments are discussed.
Current meeting assistants stop at transcripts, summaries, and action items. What if Cursor went one step further and became an active engineering participant?
Proposal: Cursor AI Engineer
During engineering meetings (Zoom, Google Meet, Microsoft Teams, etc.), Cursor could:
- Join as a junior AI engineer.
- Understand the repository and project context.
- Raise clarifying questions only when highly confident that something is ambiguous or inconsistent.
- Suggest implementation approaches based on the existing codebase and architecture.
After the meeting, Cursor could:
- Convert discussions into implementation plans.
- Analyze the repository.
- Generate code.
- Create tests.
- Update documentation.
- Open a draft Pull Request.
For teams that prefer more control, it could generate a complete Cursor prompt instead of modifying the code automatically.
The AI would also maintain long-term memory across meetings, allowing it to remind the team about previous architectural decisions, unfinished migrations, or unresolved technical debt.
Instead of:
Meeting → Notes → Human starts coding
it becomes:
Meeting → AI participates → AI plans → AI implements → Draft PR
I believe this shifts Cursor from being an AI coding assistant to an AI engineering teammate.
I’d love to hear what the Cursor team and the community think. Would this fit Cursor’s long-term vision? What technical or UX challenges do you see?