Skip to content

Latest commit

 

History

History
49 lines (28 loc) · 3.05 KB

USER-GUIDE.md

File metadata and controls

49 lines (28 loc) · 3.05 KB

Taskly user guide

English · 简体中文

A local task manager for lists, quick capture and scheduled reminders.

Availability

Development preview; no paid checkout is open. A future official desktop purchase will be announced with its delivered terms.

Platforms and installation

Desktop previews for macOS, Windows and Linux. Select the OS and CPU shown on the release asset; mobile and watch applications are not delivered products.

Use official Releases, select an explicitly listed OS/architecture asset, read its release notes and check supplied checksums. An absent asset/platform is not a delivery promise. Preview builds may lack publisher signing or notarization; do not disable system-wide security protections to install them.

Your first successful session

  1. Create a list and add one non-sensitive task. Check the parsed date before saving.
  2. Complete the task, reopen the application and confirm the saved state.
  3. For reminders, allow OS notifications and test one while the app is running. Do not assume delivery while it is closed or the computer sleeps.

Data, backup and recovery

Tasks use SQLite, normally ~/.taskly/tasks.db, with configuration in ~/.taskly/config.ini. Quit every Taskly process, then back up the directory, including any WAL/SHM files. Restore into a separate copy first. A cloud-synced live database is not a supported concurrent-editing mechanism.

Network, keys and privacy

Core task use is local. Update checks/downloads and links you open contact external services. Sharing a database or diagnostics can disclose task titles and notes.

Known limits

Reminders are evaluated consistently by the shared core on all three desktop hosts, but Taskly must be running and the OS must allow notification delivery. The standalone packaged CLI is not yet part of desktop releases; source CLI instructions remain in the README.

Updates and removal

Back up data and read the destination release notes first. An in-app update check does not necessarily install an update for your channel; follow the manual for portable, installer and source paths. Never bypass a failed signature check or replace the program with an untrusted artifact. On failure, preserve data and the error, then recover with a trusted release. Removing the program does not necessarily erase its separate data directory; verify your backup before deleting personal data.

Get help

Report problems in GitHub Issues, in English or Chinese. Include the version, OS/architecture, installation channel, steps, expected result and actual result. Reproduce with synthetic input first; do not attach keys, credentials, databases, private source documents or complete logs. Public support has no guaranteed response time.

Further reading