@onres2Cursor Projects: keeping two people and their AI agents on the same page
Cursor launched its Projects beta on September 10, and we jumped in this weekend at OnRes.
Jake, our technical lead, and I spent several hours setting up shared Projects for our development work.
We approach the work from different directions: I handle product direction and business requirements, while Jake handles technical implementation. The challenge is keeping both of us—and our AI conversations—working from the same decisions and project history.
Our setup brings together:
- Shared project context covering the purpose, decisions, current status and outstanding work.
- Linked Git repositories containing the code and supporting documentation.
- A coordinator conversation where we establish priorities and ask questions across the project.
- Separate conversations for specific development tasks.
The idea is for Jake to find the context and answers he needs while I’m unavailable, and for both of us to work on the same broader project without repeatedly rebuilding the background.
We’ve only just put this in place, so we’re still learning how well it works in practice. I’d be interested in how other small teams keep shared context current when several people are working with AI.
If anyone has insights, tips or suggestions to improve this setup, they’d be very welcome.
