Repository navigation
🐞 Files save but end up empty #2175
Description
Description
Hey, I ran into a pretty frustrating issue where saving files seems to work… but the contents just don’t actually get written.
To Reproduce
- Open CodeEdit
- Create or open a file
- Type anything into it
- Save using Cmd + S (or the save option in the menu)
- Check the file afterward (in Finder or by reopening it)
Expected Behavior
The file should save normally with whatever content I added.
Version Information
macOS version: 26.4
CodeEdit version: v0.3.6
Additional Context
This happened consistently every time I tried saving.
I didn’t check whether CodeEdit had Full Disk Access in macOS Privacy settings before uninstalling, so I’m not sure if that could be related.
If it is a permissions issue, maybe the app could warn about it or document it more clearly.
Screenshots
No response
Activity
zenxdv commentedon Apr 10, 2026
Quick update: I tried reproducing this after a fresh macOS reinstall, and the issue still happens consistently.
So it doesn’t seem to be caused by leftover configs or a broken local setup. I still didn’t explicitly verify Full Disk Access permissions, but this was on a clean system.
zenxdv commentedon Apr 17, 2026
New update: I just looked through the GitHub commit comments, and found out that sidebar files are just "Scratch Pads" for pasting content but don't actually save, instead I just create a new file from the menu bar after I decided to redownload CodeEdit, apologies for not reading thoroughly.