A folder in Overwatch is not a bookmark. It is a workspace: its own sessions, its own directives, its own scrapbook notes, its own default model. Open it and everything about that project comes back with it.
Open the folder and the project's whole head comes with it.
“Global settings and tool auth tokens are siloed per device. Starting a session on a second device feels like starting from scratch.”
GitHub #52421 · Desktop ignores the CLI config. Also #56793. Claude Code stores memory and settings in a local ~/.claude that "doesn't sync across devices by design."
View the source ›
Built, and built the other way round. Overwatch settings hang off the folder, and the folder lives in the cloud. One source of truth, per project, on every device. The workaround people resort to today is a manual OneDrive symlink that needs admin PowerShell.
Add a folder and Overwatch treats it as a project: sessions grouped under it, file tools scoped to it, history kept with it.
Default model, intensity, directives and connectors are remembered per folder, so a marketing project and a codebase never share the wrong defaults.
Reopen a folder and its sessions come back in the order you left them, on any machine you sign in from.
A research folder can run a cheap fast model with a web-heavy directive set. A production repo can pin high intensity and a strict "never touch main" rule. Neither one leaks into the other, and you never re-set them by hand.
Set per folder. Synced to every device you sign in on.
Drag a folder onto the window, or open one from the sidebar. Overwatch reads it on your machine with real file tools, not an upload into a sandbox.
Open a folder or session, or drop one here