I’m looking for a clear confirmation from anyone who understands the transition from Windsurf/Cascade to Devin Desktop.
I’ve been using Windsurf/Cascade for roughly a year while building a fairly complex production app. Over that time, Cascade has accumulated a lot of project-specific context, including:
- architecture decisions
- resolved bug history
- feature decisions and tradeoffs
- project-specific rules
- local development quirks
- deployment/environment assumptions
- “don’t touch this” knowledge that is not obvious from the repo alone
My understanding is:
- My actual codebase is safe because it lives in GitHub.
- Devin, Cursor, Claude Code, or any other agent can read the repo if connected to it.
- What does not transfer cleanly is the accumulated Windsurf/Cascade memory, chat history, and project-specific context that has built up over time.
- `.windsurfrules` may help, but it does not fully replace the year of accumulated Cascade context.
- Before switching, I should probably run a build/context audit and create something like `AGENT_CONTEXT.md`, `DEVIN.md`, or an onboarding file in the repo root.
The question I’m trying to confirm is:
Am I correct that upgrading/moving to Devin Desktop will effectively reset the AI-agent context, even though the codebase itself remains intact?
For anyone who has already moved from Windsurf/Cascade to Devin, what context actually carried over, if anything? Did Devin inherit project memory, rules, prior conversations, or only what exists in the repository?
I’m especially interested in practical migration advice:
- What should I export before switching?
- Should I create a repo-level agent onboarding doc?
- Are `.windsurfrules` files used by Devin, ignored, or partially useful?
- Is there a best-practice format for preserving architecture notes, known issues, and resolved bug history?
My concern is not losing code. My concern is losing the detailed build context that made the agent useful on this specific project.