Cursor 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.
2 comments
This is a very real problem, and honestly one that very few people are addressing yet. To me it's really a "source of truth" problem, and a strategic one. In a time when everything is this fast, automated and agentic, the hard part isn't just having a source of truth, it's having a real-time one that people and agents can both rely on.
Wishing you both the best with the setup.
Very humbly, here's how I've come to see it: the only thing that stays truly meaningful now is the goal, the purpose behind the work.Actions change constantly, but goals hold, so I believe work should be expressed through goals rather than actions.
The units we divide and conquer with shouldn't be tasks, but goals and sub-goals or lets say goals in a child/parent tree order.
It may not directly address what you're facing, but I wanted to share it in case it opens a window or sparks an idea.
Thanks, Furkan. Keeping the goal clear while the work evolves makes sense. Appreciate you sharing your perspective.