Hi @hmijail,
I am posting a copy of my reply here. I hope @WhiteNoise will agree to let this information to stay on this thread.
The feature request has been open since 2021, and the underlying need still seems valid: some users want Obsidian to provide a built-in way to disable autosave, delay autosave, or configure save frequency. In my view, that is still the best long-term solution. Save behavior is core application behavior, and it would be safer and cleaner if Obsidian handled it natively.
The plugin I made, Autosave Control, is not meant to replace this feature request. It is a community workaround because the feature has not been implemented in Obsidian itself.
There has also been discussion here about whether solving this through a plugin is safe. I think that concern is fair.
No plugin can honestly guarantee that data loss is impossible. In this case especially, the plugin interacts with save behavior, so it necessarily carries more inherent risk than a purely visual or cosmetic plugin. That is exactly why I still think this belongs in Obsidian core in the long run.
Obsidian itself can implement this with better knowledge of its internal save pipeline, editor state, metadata handling, sync assumptions, and workspace behavior than a community plugin can. Also, because Obsidian itself is closed-source, plugin authors necessarily work from the public API and observable behavior rather than full knowledge of the internal implementation.
The plugin is open source, so anyone can inspect what it does and how it does it. Users should still understand the tradeoff before using it: if autosave is delayed or disabled, unsaved changes can remain in memory until written to disk, and a crash before saving can lose them. That is the tradeoff of this kind of workflow.
Also, because the plugin wraps around core Obsidian functions, it could introduce bugs in other parts of Obsidian that rely on those functions. I am doing my best to fix bugs as they are found, but the risk is still there.
All that being said, the plugin is now available in the official Community Plugins directory:
I would kindly invite everyone to keep plugin-specific support, bug reports, release notes, implementation details, and implementation-specific risk discussion in [this thread], so this feature-request thread can remain focused on the native Obsidian feature request.
But I do want to be clear: I still think this should be handled by Obsidian itself. The plugin exists because the native option does not.