Local Link

Local Link enables users to open files and folders directly from Curiosity Workspaces to their local file system or network drives.

Prerequisites

  • Windows workstations for all users

  • Access to your Curiosity Workspace settings

  • Administrative privileges for initial setup and testing

  • Network file share access (if using network drives) for users

Architecture

Local Link creates a secure bridge between Curiosity Workspaces and local resources using:

  • Custom URI schemes: curiosity-open:// and curiosity-show://

  • RSA signature verification: Each link is cryptographically signed using SHA3-512 hashing

  • Workspace-specific certificates: Links only work with the matching workspace certificate

Deployment Steps

1

Download the Local Link Executable

  • Log into your Curiosity Workspace as an administrator

  • Navigate to Settings → Local Link Settings

  • Click on Curiosity LocalLink Release Page to download Curiosity-Link.exe https://github.com/curiosity-ai/curiosity-link/releases

  • Store the executable in a secure location accessible to your deployment system

2

Download the Workspace Certificate

  • In the same Local Link Settings page, click Download Certificate

  • This downloads your workspace-specific public key file (format: <workspace-name>.curiosity-link.public-key.pem)

  • Critical: The certificate must be in the same folder as the executable for proper operation

3

Prepare Deployment Package

Create a deployment folder containing:

deployment/
├── Curiosity-Link.exe
└── <workspace-name>.curiosity-link.public-key.pem

Both files must remain together in the same directory on each user's machine.

4

Choose Deployment Method

Select the appropriate method for your environment:

Option A: Group Policy Object (GPO)

  • Create a logon script that:

    • Copies both files to a standard location (e.g., C:\Program Files\CuriosityLink\)

    • Runs Curiosity-Link.exe register to register URI schemes

Example PowerShell logon script:

gpo-logon-script.ps1
$InstallPath = "C:\Program Files\CuriosityLink"
$SourcePath = "\\fileserver\share\CuriosityLink"

# Create directory if it doesn't exist
if (-not (Test-Path $InstallPath)) {
    New-Item -ItemType Directory -Path $InstallPath -Force
}

# Copy files
Copy-Item "$SourcePath\Curiosity-Link.exe" -Destination $InstallPath -Force
Copy-Item "$SourcePath\*.curiosity-link.public-key.pem" -Destination $InstallPath -Force

# Register URI schemes
Start-Process -FilePath "$InstallPath\Curiosity-Link.exe" -ArgumentList "register" -Wait -NoNewWindow

Option B: Software Deployment Tool

  • Use your existing software deployment solution (SCCM, Intune, etc.) to:

    1. Deploy both files to target machines

    2. Execute Curiosity-Link.exe register as a post-installation step

Option C: Manual Installation

  • For small deployments or testing:

    1. Distribute the deployment folder to users

    2. Instruct users to run Curiosity-Link.exe (without parameters)

    3. The application will register itself interactively

5

Verify Installation

  • Return to Local Link Settings in your Curiosity Workspace

  • Click Check now under "Test LocalLink"

  • Confirm the status shows as working correctly

Troubleshooting Verification:

  • Ensure Curiosity-Link.exe has been run at least once to register URI schemes

  • Verify the certificate file is in the same directory as the executable

  • Check that the certificate filename matches your workspace name

  • Confirm Windows hasn't blocked the executable

User Experience

Once deployed, users can:

  • Open files: Click Open with LocalLink in the workspace to open files in their default applications

  • Show in Explorer: Click Reveal with LocalLink workspace links to reveal files/folders in Windows File Explorer

  • Work with both local files (C:\...) and network paths (\\server\share\...)

All file operations are validated against the workspace certificate before execution.

Security Considerations

Best Practices

  • Restrict executable access: Store Curiosity-Link.exe in a protected directory (e.g., Program Files)

  • Protect the certificate: The .pem file is public but should be managed as part of your deployment

  • Test before deployment: Always validate the setup on test machines before organization-wide rollout

Support

Common Issues

Links don't open

Solution:

  • Run Curiosity-Link.exe register to register URI schemes

"Invalid signature" error

Solution:

  • Ensure certificate matches workspace and is in same folder as executable

Files open in wrong application

Solution:

  • Windows file associations control default apps; reconfigure via Windows settings

Network paths don't work

Solution:

  • Verify user has access permissions to the network share

Testing Individual Components

# Register URI schemes
Curiosity-Link.exe register

# Run interactive mode (will register if needed)
Curiosity-Link.exe

Quick Reference

Minimum deployment requirements:

  • Curiosity-Link.exe executable

  • Matching <workspace-name>.curiosity-link.public-key.pem certificate

  • Both files in the same directory

  • Run Curiosity-Link.exe register once per machine

Supported URI schemes:

  • curiosity-open:// — opens files

  • curiosity-show:// — reveals in Explorer

Security model:

  • RSA + SHA3-512 signature verification

  • Workspace-bound certificates

  • Zero-trust link validation

PreviousWorkspace IntegrationsNextAPI Integrations

Last updated