Steps
Save the qURL skill to ~/.agents/skills/qurl/SKILL.md, then ask Cascade to share the app, or type @qurl to call the skill directly. Cascade installs the qurl CLI if needed, publishes the app as a private resource, and gives you an address to send; it applies the private access rules you choose.
Install the skill
Devin Desktop discovers skills in ~/.agents/skills, as well as its own ~/.codeium/windsurf/skills. For one project only, save it to .devin/skills/qurl/SKILL.md (or the older .windsurf/skills) in the repo.
mkdir -p ~/.agents/skills/qurl && curl -fsSL https://layerv.ai/skills/qurl/SKILL.md -o ~/.agents/skills/qurl/SKILL.mdNo skill installed? Paste the prompt
Cascade reads pages from URLs pasted into your message, so the one-line prompt works without installing anything.
Read this skill and use qURL to share local apps and files moving forward. https://layerv.ai/skills/qurl/SKILL.mdChoose who can open the app
The agent applies the private access rules you choose. For named recipients, give it their email addresses so it can send invitations. Recipients verify their email in the browser and save a passkey; they never send you their email verification code. The agent checks policy support before sharing and keeps the app private if the deployment cannot support it. For existing legacy resources only, pass on a six-digit access code when it came from the person you mean to let in, over a channel where you know it is them. Ask for a one-time link when that meets your needs; the link is a secret.
What the recipient sees
A person opens the emailed invitation or the address in a browser and sees who published the app and whether LayerV has verified that publisher.
More
The private policy controls access. Named recipients verify their email there and save a passkey; their email verification code stays in that flow. A person with a one-time link lands on your app directly. A one-time browser session stays with the browser that opened the link; a script or agent without a browser is admitted by its network address instead.
Troubleshooting
| If you see | Do this |
|---|---|
| @qurl isn’t offered | Check the file is at ~/.agents/skills/qurl/SKILL.md and reopen the project. Skills can also be created from the Cascade UI. |
| The private-policy commands are unavailable or consumer access is disabled | Ask the agent to follow the access-policy support check in the qURL skill. It updates an older CLI when needed. If the deployment cannot support the requested policy, stop sharing and keep the app private; do not fall back to legacy access requests. |
Show 7 more fixes
| If you see | Do this |
|---|---|
| For an existing legacy resource, the agent cannot turn on access requests, or publishes with no Access: line in the output | The CLI is older than 3.4.1. Ask the agent to update it; the skill’s install step always installs the latest release. qurl --version should then print 3.4.1 or later. |
| qurl publish says the local app is not accepting TCP connections | Start the app first and check that curl works on the same address. qurl publish connects to localhost as 127.0.0.1, so if your app listens only on IPv6 (on macOS or Linux, lsof -iTCP -sTCP:LISTEN -nP shows [::1]), publish 'http://[::1]:PORT' instead, or start the dev server with --host 127.0.0.1 and publish that address. Neither requires listening on your LAN. Keep the quotes: zsh treats the brackets as a pattern. |
| The recipient sees “Access link invalid” | The link was already used or has expired. Run qurl share again and send the new link. |
| The recipient sees “Resource not found” | The resource was deleted after the link was made. Publish the app again, then run qurl share and send the new link. |
| publish rejects http://127.0.0.1 with “only HTTPS URLs are allowed”, asks you to log in, or prints no Access: line | Your qURL CLI is out of date. On macOS run brew update, then brew upgrade qurl; elsewhere install the latest release. After updating, qurl --version prints 3.4.1 or later, and every publish is private by default. |
| publish says this Linux session “can’t reach a systemd user manager” | You are in a container or sandbox without a user service manager. Run qurl publish with --foreground; sharing lasts as long as that process runs. Container and CI setup → |
| publish says “Quota Exceeded” with “protected resource limit reached”, or “Your qURL account has reached a plan limit” | You can see this without an account: a device with no account can keep up to 3 active resources, with links that last up to 24 hours. Run qurl list --status active, then qurl delete <CRID> for any you no longer need (it asks you to confirm; --yes skips that). qurl stop keeps the resource, so it does not free a slot. |
Frequently Asked Questions
Is Windsurf the same as Devin Desktop?
Windsurf’s documentation now lives under Devin Desktop, and the agent is still called Cascade. The older .windsurf folders still work; .devin is the preferred name.
Will the agent send the address or a link to other people?
It gives the address or link to you, and you decide who receives it. It sends invitation emails only to recipients you authorize. For legacy resources, it approves only a code you pass on, never the name on a request.
Do I need a LayerV account or API key?
No. Publishing from the CLI needs no account; the first publish creates an identity for this computer. Recipients verify their email and save a passkey in their browser when the private policy requires it. Without an account you can keep up to 3 active resources, with links that last up to 24 hours.
Who else can reach my app while the link is open?
Opening the link starts a session for that browser, which lasts 1 hour by default. After a browser opens it, another browser on the same public IP cannot use its access. A script or agent that opens the link without a browser is admitted by its network address instead, which other devices on that public IP share until the session ends. A link admits whoever opens it: the API’s IP and country rules do not apply to the signed links qurl share issues. Keep your app’s own sign-in for anything sensitive.
Share it from Windsurf
Paste this prompt into Windsurf in the project whose app is running. It reads the qURL skill, publishes the app privately, and you choose who can open it.