Connecting a repository asynchronously

Sometimes you can’t finish connecting a repository in one sitting. Installing the Paradime Deploy Key on your Git provider often needs someone with admin access, and in some organizations that can take up to a day. Instead of blocking your setup until the key is in place, Paradime lets you save the repository now and verify the connection later. This guide walks through the asynchronous (deferred) connection flow: the scenario it solves, how to save a pending connection, and how to validate it once the Deploy Key has been installed.

​

When to use this

Use the asynchronous flow when:

• You don’t have permission to add Deploy Keys to the repository and need to hand the key to a colleague or platform team.
• Your Git provider is managed by another team and key installation takes time.
• You want to record the repository connection now and complete verification during a maintenance window.

If you already have admin access and can install the Deploy Key immediately, use Test & Save instead and connect in a single step. See Importing a repository.

​

How it works

The connection moves through two states:

​

Step 1: Save a pending connection

1. In Paradime, go to Settings → Workspace.
2. In the Git Connections section, click Edit Repository.
3. Paste your repository’s SSH URL into the Repository SSH URL field.
   You must use the git@... or ssh:... version of your Git URL, not the https://... version. Paradime clones over SSH and cannot use HTTP URLs.
4. Copy the Deploy Key that Paradime generates.
   The Deploy Key is stable. It stays the same when you refresh or reopen the page, so you can save now and hand the key to your Git admin without it changing.
   Two controls sit next to the Deploy Key, which matter for the async flow because the key often changes hands before it’s installed:
   • Refetch copies the same Deploy Key again without changing it. Use it to grab the key a second time, for example to re-send it to your Git admin. Anything already installed keeps working.
   • Regenerate creates a new Deploy Key and replaces the old one. Paradime asks you to confirm first.
   Regenerating invalidates the previously generated Deploy Key. If you regenerate after sharing the key, any copy your Git admin already installed stops working, and you’ll need to send and install the new key before verification can succeed.
5. Click Save without testing.

Paradime saves the repository and shows a Pending verification state (an amber badge and banner) in the Git Connections section.

​

Step 2: Install the Deploy Key

Send the Deploy Key to whoever manages your Git provider and have them add it to the repository with read and write access. Each provider has its own steps:

​

Step 3: Verify the connection

Once the Deploy Key is installed:

1. Go to Settings → Workspace.
2. In the Git Connections section, find the pending connection and click Verify connection.
3. Paradime checks access to the repository. On success, it clones the repository and promotes the connection to Verified. The Code IDE, Bolt, and DinoAI activate.

​

Troubleshooting

If Verify connection fails, the connection stays pending and Paradime shows an error. Common causes:

• Deploy Key not installed yet. Confirm your Git admin has added the current key to the correct repository. If the key was regenerated after you shared it, install the newest one.
• Missing write access. The Deploy Key must be granted read and write access, not read-only.
• Wrong URL format. Confirm the SSH URL starts with git@... or ssh:..., not https://....

Fix the issue and click Verify connection again. For persistent errors, see Git and repository errors or contact support.