ONE MEMORY ACROSS YOUR AIs
Pick up the topic.
MiM finds the history.
Current guidelines come first. Previous chats provide evidence. Only you approve changes.
Set up MiM with a passkey
Click Create my passkey below. In the browser prompt choose this Windows device (Windows Hello), then use your usual Windows PIN or fingerprint. MiM never sees it.
Replace a lost passkey
Use your saved recovery password and one offline recovery code. A successful replacement revokes all old passkeys, AI connections, sessions and unused approvals. It does not recover backup-decryption keys.
Initialize your original canonical guidelines
This one-time setup loads only the unchanged rule files pinned by your deployment manifest. Compare the displayed manifest and per-file hashes against your independently retained original reference; do not trust the page alone. It does not promote chat archives or approve the pending OLD rule. Once initialized, later rule changes require your normal fold workflow.
YOUR PRIVATE MEMORY
Welcome back.
Use email and password
Activate once here. After that, sign in from any browser with your email and the recovery password you chose when setting up MiM. No phone scan is needed. Your email is a sign-in name; it is not Google sign-in.
Personal setup steps
- Enroll your passkey and save recovery codes privately.
- Open the local MiM companion using Start-MiM-Companion.cmd.
- Select approved source folders or export files; inspect coverage and preview.
- Set two public backup recipients; keep private identities separately.
- Create separate collector tokens and finite C/E plans below; enable automatic upload only when ready.
- Restore a synthetic backup, then connect and test one AI at a time.
Downloads, missing sources, retries and media gaps remain visible. Connecting an AI does not grant access to its other web chats.
Talk normally with a connected AI. Its MiM instructions tell it to look up relevant history automatically. The connection test must verify that the AI actually does this.
What is protected
Original backups are encrypted on your computer. Searchable copies require a separate approval. Their search index is readable by this host; these copies are not end-to-end encrypted. Your backup keys stay off this server.
Changes still require the ordered checklist, a current Kimi result, your current-chat “fold”, and your confirmation of the exact change here.
Your history
Connect your AIs
MCP address:
Use OAuth where your AI supports it. Otherwise, create a separate token for that app and put it in the Authorization: Bearer header. Never put a token in a URL.
Backups & uploads
The local companion prepares two separate packages. Review the selected content locally, then select its prepared transport folder here. The folder is read only when you approve and upload.
Advanced: approve a companion upload ticket
Ongoing backup plan
Use the local companion to choose sources and obtain its scope fingerprint. This is finite permission for collection only. It cannot approve memory changes or disclose content to Kimi or the relay.
Transfers
Erasing revokes access and cleans the active database and package files. Older snapshots and hosting backups may retain data. A busy cleanup is reported for retry.
Encrypted original backups
Searchable copies and held private batches
A held batch is stored on this host but cannot be searched by AI clients until you review and release its exact digest. Erasing the last searchable copy suppresses that conversation from future indexing. Suppression does not erase separately retained C originals or all host snapshots.
Your approval is required
Only you approve changes. MiM asks you to confirm your password or optional passkey when fresh verification is needed.
Configure the Kimi reviewer
Use a current key from your Moonshot account and its exact model ID. Do not use a key previously exposed in a chat. Saving does not send a request; reviews use api.moonshot.ai after exact disclosure approval.
Data disclosure approvals
Read the exact data before allowing it to go to Kimi. The same restriction applies to relay posts and historical-content derivatives.
Completed Kimi reviews
Pending folds
Current canonical guidelines
Imported from your existing vault. History cannot change these. Rule or permission changes require connected AIs to boot again; ordinary memory folds do not.
Portable topic file for another AI
For an app without a compatible connector, download your guidelines plus bounded permitted topic context. It includes your private rules, profile and attachment metadata, not encrypted originals or authorization. You choose where to share it.