𝗜 𝘄𝗿𝗼𝘁𝗲 𝘁𝗵𝗲 𝘀𝗰𝗿𝗶𝗽𝘁 𝘁𝗵𝗮𝘁 𝘄𝗮𝘀 𝘀𝘂𝗽𝗽𝗼𝘀𝗲𝗱 𝘁𝗼 𝗽𝗿𝗲𝘃𝗲𝗻𝘁 𝘁𝗵𝗶𝘀. 𝗜𝘁 𝗱𝗲𝗹𝗲𝘁𝗲𝗱 𝟮𝟵 𝗿𝗲𝗮𝗹 𝗳𝗶𝗹𝗲𝘀 𝗮𝗻𝗱 𝗰𝗼𝘀𝘁 𝗺𝗲 𝘁𝗵𝗲 𝗿𝗲𝗽𝗼. The setup is the one most of us land on, because every step of it is sensible. Your Company Brain lives in Google Drive so it syncs everywhere. The desktop app makes it a normal folder. Your code ends up in there too, so the brain and the work sit together. Then you work from two machines and point AI agents at all of it. Every choice is fine. Together they put 𝗮 𝗱𝗮𝘁𝗮𝗯𝗮𝘀𝗲 𝗶𝗻𝘀𝗶𝗱𝗲 𝗮 𝗳𝗶𝗹𝗲 𝘀𝘆𝗻𝗰𝗲𝗿. Here is the collision. Your git folder is a database. Google Drive does not merge conflicts, it renames them, adding a " 2" or a " (1)". It does that everywhere, including inside the git folder. Git never puts a space in its own internal filenames, so the moment Drive renames one, git cannot read its own history. It never announces itself as a sync problem. It shows up as git having amnesia: "bad sha1 file", "badRefName", a missing object, or a push that just gets refused. Nothing hints that sync did it. 𝗡𝗼𝘄 𝘁𝗵𝗲 𝗽𝗮𝗿𝘁 𝘁𝗵𝗮𝘁 𝗰𝗼𝘀𝘁 𝗺𝗲 𝘁𝗵𝗲 𝗿𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆. The obvious fix is a script that deletes every odd-looking file inside the git folder. I wrote that script. I was proud of it. It ran on every single commit. What I did not know is that Drive sometimes renames the ORIGINAL rather than adding a copy beside it. So those "junk" files are sometimes your only copy of a real git object. My clever cleanup deleted 29 of them. The repo could no longer rebuild its own history. Re-clone. The work survived only because it had been pushed. 𝗧𝗵𝗲 𝗰𝗼𝗿𝗿𝗲𝗰𝘁 𝗿𝘂𝗹𝗲 𝗶𝘀 𝗼𝗻𝗲 𝗹𝗶𝗻𝗲, 𝗮𝗻𝗱 𝗶𝘁 𝗶𝘀 𝘁𝗵𝗲 𝗼𝗽𝗽𝗼𝘀𝗶𝘁𝗲 𝗼𝗳 𝘄𝗵𝗮𝘁 𝘂𝘀𝘂𝗮𝗹𝗹𝘆 𝗴𝗲𝘁𝘀 𝘄𝗿𝗶𝘁𝘁𝗲𝗻: • Suffixed file exists, original is MISSING, so 𝗿𝗲𝘀𝘁𝗼𝗿𝗲 𝗶𝘁. Drive renamed your original. • Suffixed file exists, original is there, so delete the duplicate. The original is fine. Nothing inside the git folder gets deleted unless a correctly named file survives next to it. And the habit that matters more than any script: 𝗧𝗵𝗲 𝗿𝗲𝗺𝗼𝘁𝗲 𝗶𝘀 𝘁𝗵𝗲 𝘀𝗼𝘂𝗿𝗰𝗲 𝗼𝗳 𝘁𝗿𝘂𝘁𝗵. 𝗧𝗵𝗲 𝘀𝘆𝗻𝗰𝗲𝗱 𝗳𝗼𝗹𝗱𝗲𝗿 𝗶𝘀 𝗮 𝗿𝗲𝗽𝗹𝗮𝗰𝗲𝗮𝗯𝗹𝗲 𝘃𝗶𝗲𝘄 𝗼𝗳 𝗶𝘁. 𝗡𝗼𝘁𝗵𝗶𝗻𝗴 𝗶𝗿𝗿𝗲𝗽𝗹𝗮𝗰𝗲𝗮𝗯𝗹𝗲 𝗲𝘃𝗲𝗿 𝗹𝗶𝘃𝗲𝘀 𝗼𝗻𝗹𝘆 𝗶𝗻 𝘁𝗵𝗮𝘁 𝗳𝗼𝗹𝗱𝗲𝗿.