Skip to content
All Features

Your memory, anywhere.

Device Sync

Transfer your entire assistant state between machines with end-to-end encryption (AES-256-GCM + RSA-4096). The sync server stores only opaque encrypted blobs. It can never read your data. Selective component transfer lets you choose exactly what moves. The CLI works perfectly without sync; it's 100% optional.

See it in action

kognisant | sync

How it works

  1. 1

    Each device generates an RSA-4096 keypair on first link. The public key is stored server-side; the private key never leaves your device.

  2. 2

    On push: selected components are packed, a random AES-256 key is generated, the archive is encrypted, and the AES key is encrypted with the target device's public key.

  3. 3

    The server stores the opaque blob (it has no decryption key) and notifies the target device.

  4. 4

    On pull: the target device downloads the blob, decrypts the AES key with its private key, decrypts the archive, and unpacks into .kognisant_core.

Key capabilities

End-to-end encryption (AES-256-GCM + RSA-4096)
Server has zero knowledge of content
Selective component transfer (memory, skills, config, etc.)
Blobs auto-delete after 24h or on completion
SHA-256 checksum verification on download
CLI works 100% offline. Sync is optional

Use cases

  • Move your AI assistant from laptop to desktop
  • Set up a new machine with your existing context
  • Keep multiple development machines in sync
  • Backup your assistant state to the cloud (encrypted)

Commands

reference
kognisant sync login <token>

# Link device to your account

kognisant sync push

# Upload encrypted state to cloud

kognisant sync pull

# Download and decrypt from cloud

Ready to try Device Sync?