Get a Public URL for Your Claude Code App

From the team behind aidrop.it — one workspace to build, host, and keep changing your code.

To give the app you built with Claude Code a public URL, deploy its production version to a remote service, then test that address from another device. Keep the project you already have. Ask Claude Code to inspect how it builds, prepare the deployment and verify the page or action you want to share.

A link such as http://localhost:3000 points to the computer opening it. Your friend will reach their own machine, not yours. The localhost specification reserves that name for the local device. A deployed app runs elsewhere and remains available when you close your laptop.

Choose the runtime

Ask Claude Code whether your project produces static files or needs a server. A landing page with HTML, styles and browser JavaScript can use static delivery. Login, saved records or a private API may require a backend and a data store. Match the deployment to the code you have before choosing a plan.

For a Vite project, build the production files and deploy the output. Vite documents preview as a local check, not a production server. For an application server, record its start command, listening port and required configuration. The first-deploy brief helps collect those facts.

Keep Claude Code in the deployment loop

Connect your deployment provider to Claude Code using its supported integration, then ask the agent to show the plan before it acts. Give it the existing project, the code revision to publish and one action that must work online. Approve the changes needed to run that version, including any new paid resources.

Claude Code supports remote tools through MCP. With the appropriate tools and repository access, the agent can push your code, request a build and check its result. The Claude Code deployment guide explains that workflow. Your Claude Code subscription and the deployment provider's plan are separate.

Test your public link

Open the HTTPS address on a phone or another computer and exercise the action you named. Check images, navigation and API requests as well as the first page. A homepage that loads while its form calls localhost still depends on your laptop. Fix that dependency before sending the link to someone else.

Decide which pages a visitor may access without signing in. Use the live-app access check before sharing account screens or real records. A hard-to-guess address gives you a convenient link; protect restricted pages with application authentication and authorization.

A publishing task

Copy this task into the conversation where your project lives. Replace the blanks with your own action and audience. The task works with a deployment provider that your agent can access; it asks the agent to report missing requirements before proceeding and to test the address after deployment rather than treating a completed build as enough.

Put this existing project online.
The visitor must be able to:
The intended audience is:

Inspect the code and identify static output or the server process.
Check the production build, start command, port and required value names.
Find browser requests that still depend on localhost.
Show the deployment plan and any cost or data changes for approval.
Use the approved provider and publish the chosen code revision.
Test the public HTTPS address and the visitor action above.
Report the URL, running revision and test result.
Do not include secret values in the report.

FAQ

Do visitors need Claude Code to open my app? No. Visitors open the deployed website in their browser. They need an application account only if your app requires one; they do not need the coding tool that helped you create it.

Can I share the app without buying a domain? Yes. Many providers supply a public address for the first deployment. You can test that address before adding a domain you own. Check the provider's plan requirements before adding a custom hostname.

Can I get the public URL through aidrop.it? Connect aidrop.it to Claude Code, bring your existing project and approve its deployment. The agent pushes the code and checks the build through MCP. A successful deployment gives the app a public HTTPS address; your project still has to fit the runtime and plan limits.