Give an AI agent access to a local app

Checked against the qURL™ CLI 3.4.1 source and documentation on October 8, 2026. Link and session behaviour is tested separately.

Content updated October 18, 2026. The verification date above records the original review; later behaviour checks are dated in the guide.

How do I let an AI agent share or use an app running on my machine?

Give your coding agent the qURL skill. It checks policy support, publishes privately, and gives you an address to send. Choose access rules and recipient emails for invitations. Recipients verify email in their own browser; never ask for their verification codes. If the deployment cannot support the policy, the app stays private. For another agent, ask for a one-time access link and open it with the qURL Go SDK.

What you need

• A coding agent that runs shell commands on the machine where the app runs (Claude Code, Codex, Cursor, and similar)
• An app running on this machine
• For an agent that opens a link in code: Go 1.26.6 or later
• No account or API key

Steps

1. Give the agent the qURL skill

   For Claude Code, save the skill to your personal skills folder. If Claude Code was already running and this created the folder, run /reload-skills. Other agents read the file from its URL; the prompt in the next step points them there.

   mkdir -p ~/.claude/skills/qurl && curl -fsSL https://layerv.ai/skills/qurl/SKILL.md -o ~/.claude/skills/qurl/SKILL.md

2. Ask it to share the app

   The agent finds the running app (or asks which one), installs the CLI if needed, publishes the app as a private resource, and gives you an address to send. 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. To let one person in at once, ask it for a one-time access link; that link is a secret.

   Read https://layerv.ai/skills/qurl/SKILL.md and use qURL to share the app I'm running locally.

3. For another agent, send it a link to open in code

   Ask your coding agent for a one-time access link, and send it to the other agent. An agent with a browser tool can open the link the way a person does. In code, open it with the qURL Go SDK (github.com/layervai/qurl-go/qurl). It needs no LayerV credentials, but opening uses the link’s one opening, so don’t open it first. The SDK connects over UDP port 443 by default. Fetching the link with curl returns the opener page, not your app.

   handle, err := qurl.EnterPortal(ctx, link)
   if err != nil { return err }
   req, err := http.NewRequestWithContext(ctx, http.MethodGet, handle.ResourceURL, nil)
   if err != nil { return err }
   if err := handle.AuthorizeContentRequest(req); err != nil { return err }
   resp, err := (&http.Client{CheckRedirect: handle.CheckContentRedirect}).Do(req)
   if err != nil { return err }
   defer resp.Body.Close()

What the recipient sees

A person opens the address in a browser and sees who published the app, marked Not verified. Today LayerV has verified only its own account, so every other publisher is shown as not verified. Recipients of a private invitation verify email in their own browser and save a passkey; their email verification code stays in that flow. For an existing legacy resource only, they ask for access and pass on a legacy code through a trusted channel. A person with a one-time link lands on your app directly. An agent that opens that link with the SDK gets your app’s URL and calls AuthorizeContentRequest on each request to it until the session ends, 1 hour by default. Either way, the session admits the network address the opener connects from.

Troubleshooting

Frequently Asked Questions