Synchronize vaults and handoffs across devices
The agent synchronizes notes and task handoffs between different devices and sessions, ensuring data consistency through git-backed vaults and automatic cleanup of stale handoffs.
How it works
The agent uses the ainote MCP server to manage vaults and handoffs. It can save handoffs for later retrieval using handoff_save, which stores data in a git-backed vault. It retrieves these handoffs using handoff_get. The agent also manages synchronization using sync_push and sync_pull to ensure data is consistent across devices. It should be aware that handoff_list and handoff_get are marked as destructive due to automatic 7-day purge of stale data, so it should use them carefully. The agent leverages the backend's conflict resolution capabilities during sync operations.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Save a handoff for project 'logi' with topic 'phase4' and content 'Meeting notes from 15:00'. Then, retrieve any existing handoffs for this project and sync the local vault to the remote git repository.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
vault_sync(action: push) 가 호출되면 백엔드가 conflict 를 감지·해결한다.ainote — Agent-native notes, tasks, memory & sync · ainote 개발자 문서