Apps & Sync

Use the same knowledge where the work happens. MindWiki Cloud, the Mac app, the iPhone app, and authorized AI clients connect to your account's vault, so a captured idea can become a desktop document and an agent's saved result can become a page you read yourself.

Each surface serves a different moment. You do not need to copy a project into a separate knowledge base for every device or agent.

Choose the right surface

Open MindWiki Cloud or see Downloads for available app distribution. Controls differ between clients; the detailed editor documentation covers web and Mac rather than promising identical interfaces on every device.

Keep one account across surfaces

Sign into the same MindWiki account in each app. When authorizing another agent, choose your existing account so it joins the same vault instead of starting a separate collection.

Your capture email, pages, and agent connections belong to that account. Each agent has a separate grant that can be revoked individually. Your account sign-in access key is different from the OAuth credentials or API key used by an integration.

Continue work across devices

1. Capture a useful thought by email, on your phone, or through web Quick Capture.
2. Open the page on Mac and develop it into a brief.
3. Add source files, links, or properties where helpful.
4. Ask an authorized agent to read that brief and help with the next task.
5. Open its saved output on the web to review it.

The common object is the saved page. A change must save and sync before another surface can retrieve it. On the web, auto-save follows a pause in editing; the save command requests an immediate save.

Work with local files on Mac

The Mac app works with a local Markdown vault folder and synchronizes supported content with your cloud account. Follow the app's vault setup to choose the folder and connection.

Pages remain readable Markdown files with optional YAML metadata. Attachments live in _assets/ and are referenced by pages. You can inspect the local content, use supported export, and keep your own backup.

A local page and its cloud revision can differ while a device is offline or a transfer is pending. Check the sync state before assuming another app or agent can see your newest edit.

Understand saves, sync, and attachments

Saving records an edit on the current surface. Sync delivers changes between the local vault and cloud storage. Agent retrieval reads the cloud content available to its authorized connection.

Text and media do not necessarily finish transferring together. Larger files take longer, and a page reference may appear before the attachment is ready to open. Keep the referenced asset in place and allow its transfer to finish.

See Sync Model for technical behavior and Attachments & Files for authoring and preview support.

Handle overlapping edits deliberately

If two devices or agents edit a page from different starting revisions, inspect the current versions before choosing or merging changes. Agent page updates use revision checks to prevent stale writes silently replacing newer content.

For parallel agent tasks, separate output pages linked from one project hub are often easier to reconcile. See Conflicts when changes overlap and Shared Agent Memory for a repeatable handoff pattern.

If a page is missing elsewhere

• Confirm both surfaces use the same account.
• Check that the source edit saved.
• Check connectivity and sync status.
• Try the exact title or known path.
• Allow attachment transfers and indexing to complete.
• Inspect an agent's returned path rather than assuming a successful conversation saved a file.

Sync makes content available across your connected surfaces; it is not a separate historical backup. Use Export & Backup when you want an independent copy, and Devices for device management.

Next: Quick Start, Integrations, and Sync Model.