Sharing with Deep Links
CutReady supports deep links that let you share a workspace with anyone using a single URL. When a recipient clicks the link, CutReady opens the project automatically — or clones it if they don’t have it yet.
How It Works
Section titled “How It Works”Every CutReady workspace backed by a GitHub repository has a shareable URL:
https://cutready.io/gh/owner/repoFor example, if your workspace is at github.com/sethjuarez/mvp-summit-2026,
the share link is:
https://cutready.io/gh/sethjuarez/mvp-summit-2026When someone opens this link:
- CutReady is installed — the browser hands off to the app via the
cutready://protocol. CutReady checks if the workspace is already cloned and opens it, or prompts to clone it. - CutReady is not installed — the page shows a brief description and a download link pointing to the latest GitHub release.
Sharing a Workspace
Section titled “Sharing a Workspace”-
Push your workspace to GitHub (see Remote Sync).
-
Construct the link from your GitHub repository URL:
GitHub URL CutReady Link github.com/alice/my-democutready.io/gh/alice/my-demogithub.com/team/projectcutready.io/gh/team/project -
Send the link to your collaborator via chat, email, or paste it in a document.
Opening a Shared Link
Section titled “Opening a Shared Link”When you click a cutready.io/gh/... link:
-
Your browser redirects to the
cutready://protocol. -
CutReady activates and checks your recent projects for a matching repository.
-
Already cloned — the workspace opens immediately.
-
Not cloned — CutReady opens the Clone dialog pre-filled with the repository URL. Choose a folder, and it clones and opens automatically.
The cutready:// Protocol
Section titled “The cutready:// Protocol”CutReady registers a custom cutready:// URL protocol during installation.
The web redirect page at cutready.io translates the human-friendly URL into
this protocol:
cutready.io/gh/owner/repo → cutready://gh/owner/repoYou can also use the protocol URL directly if you prefer:
cutready://gh/sethjuarez/mvp-summit-2026Requirements
Section titled “Requirements”- Sender: Workspace must be pushed to a GitHub remote
- Recipient: CutReady installed + GitHub CLI authenticated (see Setup Guide)
- Repository access: The recipient needs read access to the GitHub repository (collaborator on private repos, or any user for public repos)
Troubleshooting
Section titled “Troubleshooting”Link opens the browser instead of CutReady
Section titled “Link opens the browser instead of CutReady”- Cause: The
cutready://protocol isn’t registered. This can happen if CutReady was installed via a portable build rather than the installer. - Fix: Reinstall CutReady using the
.msior.exeinstaller, which registers the protocol automatically.
Clone fails after clicking a link
Section titled “Clone fails after clicking a link”- Cause: GitHub CLI isn’t authenticated, or you don’t have access to the repository.
- Fix: Run
gh auth loginandgh auth setup-gitin a terminal, restart CutReady, and try the link again. See Setup Guide for full instructions.
”CutReady not installed” page appears but it is installed
Section titled “”CutReady not installed” page appears but it is installed”- Cause: The browser didn’t detect the protocol handler. Some browsers suppress protocol prompts after a user dismisses them once.
- Fix: Copy the
cutready://gh/owner/repoURL from the page and paste it directly into your browser’s address bar, or open CutReady manually and clone from the Home screen.