Documentation
Your work stays yours.
Desktop keeps project history in a local database. The project file gives agents concise access to current work; Cloud sync is optional.
Local-first architecture
Mayvor is local-first project management for people building with coding agents. Desktop watches project files and reads local SQLite data; Cloud provides shared visibility when a project is linked and synchronization is enabled.
Three stores, three responsibilities
| Store | Responsibility |
|---|---|
Project board (.peacae/tasks.json) | Concise task context that an agent can read and update |
| Desktop SQLite database | Local task records, history, and the data used by Desktop views |
| Cloud database | Synchronized project records and team dashboards |
Agents follow the project's instructions and update the board. They do not call Cloud APIs or change Desktop-owned synchronization fields. See agent integration and the task data model.
Completed work and active context
Completing a task is a lifecycle update, not a request to delete its history. Set the appropriate timestamp under the project contract; do not delete database rows or erase earlier timestamps. Desktop retains local history separately from the compact project file.
The active file is intended to keep unfinished work manageable. An approximate 50-task capacity is described in the brand brief, but this Cloud repository does not contain the Desktop implementation that enforces it. It is not a verified limit here and is not a limit on total stored tasks. Follow the installed Desktop version and project contract for pruning behavior; do not manually remove completed tasks based on this guide.
Offline work and synchronization
Launch Desktop, then open your IDE in the watched repository. Local work can continue without a Cloud session. With a linked project and an authenticated session, Desktop handles synchronization; agents continue working with project files. See Desktop and Cloud and sync.
Backup and recovery
Synchronization mirrors data and should not be treated as an independently verified backup or point-in-time recovery system. This repository does not provide a Desktop database restore command. Preserve your local database using the supported procedures for your installed Desktop version. Avoid committing the live board or secrets; commit the agent instructions and project preferences as described in project setup.