What the app never does

A short list of things Context Raven deliberately never does, so you know exactly where the edges are.

Network

• No network requests while you're signed out and none of your files are shared. The editor works fully offline.
• A remote image referenced by a URL is never loaded just by opening or viewing a note. It stays a chip showing the URL.

Your files

• Opening a file to read it never writes to it. The first keystroke you make is what unlocks saving, not opening the file.
• Nothing is permanently deleted from this app. Move to Trash always sends a file to the Trash, where the normal recovery applies.
• A path you've excluded for a folder is never read: not scanned, not watched, not searched.
• Renaming or moving a note never changes text you have not saved yet: the open note keeps it exactly as you typed it, and its links are reported instead of updated. See Rename, move and trash.
• Malformed YAML in the frontmatter block is never auto-corrected. It's written back exactly as you typed it.
• A missing file is never recreated automatically, and your unsaved edits for it are never discarded; both only happen if you choose to, from the recovery banner. See When a file goes missing.

Git and the cloud

• Context Raven never writes into your Git repository. Local file history reads your existing commits; it never creates one on your behalf.
• Share to cloud only pushes from your disk outward. Nothing is ever written back from the cloud workspace into a local file.

The one exception

Export is the one action that fetches something over the network on your behalf: clicking Download as PDF or Download as Word fetches any remote images the document references, with a 10-second timeout, so they can appear in the exported file. This only happens on that explicit click. See Export.