Where Does Devin Keep Sessions and Repos?
Where Devin keeps repos, sessions and IDE state, and why most history lives in the cloud.
Last updated
Devin is a cloud agent from Cognition. Repos, sessions, playbooks and billed minutes live in your Devin account and linked git hosts. The local machine holds editor extensions, auth tokens and checkout caches.
That split surprises people who hunt AppData for transcripts. The durable copy sits behind login on the web. Local paths below cover extension state and cloned repos. Treat them as disposable next to pushed branches.
Where Devin stores this, by platform
%APPDATA%\Code\User\globalStorage\cognition.devin
Extension storage and login tokens live here. Session transcripts render in the web app, not in these folders. Push branches to keep agent edits.
~/Library/Application Support/Code/User/globalStorage/cognition.devin
Same extension storage layout as Windows. Repo checkouts sit wherever you cloned. The account dashboard is the archive of record.
~/.config/Code/User/globalStorage/cognition.devin
Exact extension folder name may vary by fork (Cursor, Windsurf, VS Code). Check the extensions panel when the path misses. Cloud sessions stay reachable regardless.
Frequently asked questions
How do I keep Devin session history?
Use the Devin web app session history and your git remote. Local folders hold cache only. Pushing branches preserves work that the dashboard may prune.
How do I move Devin work to another machine?
Connect the same GitHub account and repo in the new IDE. Sessions attach to repos and accounts, not machines. Sign in before assuming work vanished.
Notice an outdated path? Let us know.