KeepGlide

Guide

Connect your Cloud Provider

With sync, your Markdown notes and PDFs live in your Cloud Provider account and in a folder on this computer, kept in step. When two versions collide, both are kept.

Local mode needs no account at all. If you only want your files on this computer, choose Local folder only and you can skip the rest of this page.

The five steps in 16 seconds. Simplified drawings, not screen recordings.

Choose a mode

Each computer picks its own mode in Settings > This machine and the vault, so one computer can sync while another stays local.

Everything in the cloud

Notes and PDFs live in your Cloud Provider account. KeepGlide reads and writes them there and keeps only a read cache on this computer. This mode needs the Cloud Provider connection.

Sync to a local folder

Files live in a folder on this computer and in your Cloud Provider account, and changes are carried between them. Changes made without a connection wait on this computer and are sent when the connection returns.

Local folder only

Files stay on this computer. No account, no network and no Cloud Provider setup.

The first-run setup offers the same three choices under the names Local folder only, Cloud Provider and Local folder and Cloud Provider.

Before you start

KeepGlide runs on your computer and has no server of its own. Your notes talk only to your own Cloud Provider account, so KeepGlide asks you to create your own connection once, in the Cloud Provider developer console.

Create a Desktop app client there and download its JSON file. Console names and positions can change; look for these labels.

  1. Create a project, for example named KeepGlide, and make sure it is the selected project.
  2. Enable the file API for that project with Enable. This turns the API on; it does not by itself allow access to your files.
  3. Configure the consent screen: an app name, a support email, and the External audience for a personal account.
  4. Under Data Access, add the Cloud Provider file permission that KeepGlide requests, and save. KeepGlide does not request mail access.
  5. For continuous personal use, select Publish app and confirm In production. See Troubleshooting for why.
  6. Under Clients, select Create client, choose Desktop app, and download the JSON file when it is created. Keep it private. Web application clients are rejected.

Connect in five steps

The illustrations show the Settings version. The first-run setup asks the same questions with its own buttons.

  1. Import client JSON

    In the Cloud Provider section of Settings, select Import client JSON and choose the Desktop app file you downloaded. In the first-run setup the button is Import JSON. Importing does not connect your account yet.

    Simplified drawing, not a screenshot.

  2. Connect Cloud Provider

    Select Connect Cloud Provider. Sign-in opens in your default browser, and KeepGlide waits here: Finish the authorization in the browser and come back to this window.

    If you see a warning, check your own project's name and permissions before you continue.

    Simplified drawing, not a screenshot.

  3. Allow access in the browser

    Choose the account whose Cloud Provider files hold your vault. If the browser shows that the app hasn't been verified, continue only when the project is the one you created; publishing your own project does not remove this warning.

    Review the Cloud Provider access permission and allow it. The browser then returns to KeepGlide.

    Simplified drawing, not a screenshot.

  4. Test connection

    Back in KeepGlide, select Test connection. When it passes you see Connection tested. Cloud Provider is ready.

    If the permission was not granted, KeepGlide says so and offers Reconnect and allow Cloud Provider.

    Simplified drawing, not a screenshot.

  5. Choose the folder on Cloud Provider

    Select Choose folder on Cloud Provider and pick the vault folder in the picker. In the first-run setup this button stays unavailable until the test passes.

    Simplified drawing, not a screenshot.

What KeepGlide can access

KeepGlide asks only for Cloud Provider file access. It never asks for your email. Your Cloud Provider password never goes to KeepGlide: you sign in on the Cloud Provider page itself.

Full access (default)

KeepGlide can see all of your Cloud Provider files, so the folder picker can list the folders you already have.

Restricted access (optional)

KeepGlide sees only the files it creates or opens. The trade-off: the folder picker stops listing folders the app has not touched. Changing the access level in Settings asks you to allow access again.

The saved authorization stays on this computer. Disconnecting removes it.

Working offline

How KeepGlide behaves without a connection depends on the mode you chose.

Everything in the cloud

Reads and writes go straight to Cloud Provider, so this mode needs the connection. This computer keeps a read cache, and PDF edits you have not uploaded wait in a pending cache until the upload is confirmed.

Sync to a local folder

Works offline. Changes wait in a queue on this computer and are sent when the connection returns.

Local folder only

Needs no network, because no account is involved.

Disconnect

In the Cloud Provider section of Settings, select Disconnect. KeepGlide asks you to confirm: Remove this app's access to Cloud Provider on this machine? When it is done, it shows Disconnected.

Disconnecting removes the saved authorization on this machine only. Your files in Cloud Provider are not deleted. To revoke KeepGlide's access everywhere, use the permissions page of your Cloud Provider account.

Simplified drawing, not a screenshot.

Troubleshooting

The connection stops working after 7 days

Accounts in the Testing publishing state get tokens that expire after seven days. For continuous personal use, publish your app in the developer console (Publish app, then In production), then select Reconnect and allow Cloud Provider to get a new authorization. Publishing avoids the Testing expiry, but it does not guarantee permanent tokens, and it does not verify the app, so the warning can still appear.

KeepGlide says the permission was not granted

Returning to KeepGlide without the Cloud Provider access permission leaves the connection incomplete. Select Reconnect and allow Cloud Provider, allow the permission in the browser, and then run Test connection again.

KeepGlide rejects my client file

KeepGlide accepts only Desktop app clients; a Web application client is rejected. Create a client of type Desktop app in the developer console, download its JSON when it is created, and import that file. If the downloaded file has no secret, create a new Desktop app client and download that one.

Test connection fails

Check that the file API is enabled in the project that owns your client, and that this computer is online. Then run Test connection again.