Update Your Live App From Claude Code

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

To update a live app from Claude Code, identify the service and revision already running, make one reviewed change and deploy it to that same service. Test the changed behavior at the existing public URL. You can keep working in the same conversation while the deployment record gives the next session a starting point.

An edit on your computer affects visitors after you publish the changed version. Ask Claude Code to distinguish the local files, the code pushed to the tracked branch and the application serving requests. That check prevents you from debugging a release that never included your change.

Read what is running

Ask Claude Code to read the live service before editing the project. Record its public URL, repository, tracked branch and running revision. Compare those facts with the local checkout. If they differ, establish which version you intend to change before the agent pushes code or creates another deployment for the same application.

The tracked-branch check compares local, remote and running commits. Keep the service identifier in the task too. A new name or a new conversation does not mean you need a second application; reuse the service that already owns the link your visitors have.

Review your change

Describe the behavior you want and ask Claude Code to show the proposed diff and validation. Keep the scope small enough to inspect: changing a headline, adding a form field or repairing one API call. Check whether the edit also changes stored records, configuration or external integrations before approving its deployment.

A schema change needs its own migration and recovery plan. Restoring an older application image does not undo database writes. The rollback guide explains that boundary. Test a form with disposable data; decide how to handle existing records before a release starts modifying them.

Check the version your visitors use

After deployment, ask Claude Code to confirm which revision is running and test the changed action at the public address. Open that address in a fresh browser session when checking frontend changes. If you still see the old behavior, compare the running revision and asset requests before asking the agent to rewrite the same feature.

Record the result next to the service or in the repository. The live-app operating card gives a longer record for releases that affect access or data. Include work you deferred so the next Claude Code session can continue without guessing what the last release proved.

An update task

Paste this task into the conversation where you want to make the change. Fill in the current URL and the desired behavior, then let the agent read the deployed state. The task works across deployment providers: it asks for the existing service, a reviewed diff and a public acceptance check rather than a new application for each edit.

Update the existing live app.
Current public URL:
Existing service identifier:
Change I want:
Action that must work afterward:

Read the running revision, repository and tracked branch first.
Compare them with this checkout and explain any mismatch.
Show the proposed diff, tests and configuration or data changes.
After approval, push and deploy to the existing service.
Confirm the running revision and test the action at the public URL.
Keep the existing address and data store.
Stop before deleting data, changing credentials or running a migration
that I have not reviewed. Report the result and any unfinished work.

FAQ

Can I continue in the same Claude Code conversation? Yes. With repository access and connected deployment tools, Claude Code can make and publish the next change from the conversation you are using. Read the live state again before each release; conversation history can describe an older version.

Do I need to deploy a new app for each change? Use the existing service for an update to the same application. A separate service or environment can help test a larger change, but create it as a deliberate choice with its own resource and data requirements.

How do updates work on aidrop.it? Ask Claude Code to inspect the existing Service on aidrop.it, push the reviewed change and build that Service. Check application.commit_sha in service_get to identify the running version. The public address stays with the Service; rebuilding the application does not recreate its managed database.