Offline Resilience
When the MCP server is unreachable (network issues, server maintenance, or air-gapped environments), the Knowz skill queues saves locally. Knowledge capture continues without interruption. When connectivity is restored, /knowz flush syncs all queued items to the vault.
How it works
If a /knowz save or auto-detected capture cannot reach the MCP server, the skill writes the knowledge to a local queue file in your project. A warning message notes the offline state. When connectivity returns, running /knowz flush pushes all queued items to the vault with their original timestamps and metadata. The local queue is cleared after successful sync.
Offline save showing local queue and subsequent flush
Screenshot coming soon
Why it matters
Network reliability should not block knowledge capture. Insights emerge during development regardless of connectivity status. Offline resilience ensures nothing is lost -- whether you are on a plane, in an air-gapped environment, or experiencing a temporary network outage. The knowledge is captured in the moment and synced when possible.
Timeline showing offline captures queued and then synced
Screenshot coming soon