I’ve noticed that my Notebooks don’t get saved in the project git repo.
I’m also concerned that my chat history for the project on desktop will not be available to my laptop potentially causing issues.
At minimum I need the notebooks to be saved in the project git repo as I have all the specs in Notebooks. I have been considering just moving my notebooks to .md file and saving them in the src.
Hey, unfortunatly there is no good way to transfer composer and chat history across machines!
A good way around this, which also benefits in usual Composer usage, would be to make a file that contains are rough overview of your project, so that you can @ it when you start a new Composer, and also when you need to transfer to a new machine!
This seems like a no brainer easy win for a Cursor value proposition as nothing really does this, you can /resume in Claude Code which basically works in that realm.
Almost makes a case for Codespaces and using Co-Pilot because as long as the Codespaces is kept alive it keeps everything going…
So, odd though. Most devs probably tied to one machine, many aren’t.
Getting any of these environments to pick up context or the conversation is such an a*$ pain.
Yes, this is a major pain. I work on 4 different computers on the same remote-ssh SBC project. Work I did in a chat session on one computer needs to load context either from some rule that I decide to generate or by pasting an exported chat session. This is a pretty crappy situation. The SQL-lite database cannot be stored in my dropbox (which in any case only applies to 3 of the computers, not the SBC). Isn’t there some better solution? I end up replicating a lot of context!
I actually built a small extension that solves this exact problem — it syncs your AI chats between different Cursor workspaces and devices (using the built-in chat UI not exported into .md format).
It’s called Cursor Chat Transfer, and it works by securely storing your chat sessions so you can pick up where you left off, even on another computer.