-
Notifications
You must be signed in to change notification settings - Fork 4
FAQ
Yes. Cultiva is open source under GPL-3.0. No subscription, no cloud paywall.
No. Core use is fully offline with local IndexedDB storage.
Under Electron userData in your Windows profile (see Privacy and Security). Portable builds store data relative to the portable layout.
No telemetry in the default build. Network use is limited to optional features (plugin registry, weather API, Discord RPC, auto-update checks).
The habit becomes a Legacy tree — a permanent visual trophy in your garden.
Starting in 1.7, you get one missed day before a streak resets (configurable behavior — see release notes).
Yes — quantity habits let you log counts instead of simple done/not-done.
Common causes:
- Cultiva version below plugin's
minAppVersion(need 1.7.0+ for current registry) - No internet / GitHub blocked
- sha256 mismatch (registry out of date vs downloaded files)
- Sandbox timeout on slow
onEnable(e.g. blocking network before UI registers)
Check DevTools console: View → Toggle Developer Tools.
If you changed City in Settings but didn't pick from the plugin sheet, coordinates may still point to the default (Moscow). Use the Weather header chip → city search, or wait for the geocoding fix.
If Pomodoro is the only installed sheet plugin, shared sheet CSS may be missing. Install Weather or Time as a workaround, or wait for core sheet CSS injection.
The registry URL is configurable in plugin settings (advanced). Your registry must follow the cultiva-plugins format.
When a GitHub Release includes latest.yml, the packaged app checks for updates via electron-updater.
Yes — see Desktop Build. Requires Node 20+, npm ci, npm run build.
Open an issue on the main repo. Plugin-specific bugs can go to cultiva-plugins issues.
See Cultiva Plugins Guide and the cultiva-plugins README.