Claude Code remote access from your phone
Reach the Claude Code session that is already running on your computer. The phone sends requests and checks the result; the host keeps the project.
Reviewed against Lyre's public guides. Check current device support and plan limits before you rely on them.
The short answer
Yes, with one condition: the computer has to be reachable. Lyre pairs your phone or browser with a computer you control. Claude Code runs there, with that machine's project files, provider account and tool permissions. The phone is a client, not a second copy of the project.
What “remote access” means here
You are not opening an SSH session, publishing a development server or uploading a repository to a hosted IDE. You are connecting an authorized client to the Lyre host that already owns the workspace.
That design keeps drafts, files, running processes and provider credentials on the computer. It also means the phone cannot work around a host that is asleep, offline or no longer running Lyre.
Before you start:
- Lyre on the host. Check current downloads and device support before choosing a client.
- Claude Code connected on that computer. Confirm installation, sign-in and model readiness in Settings, AI & agents, Connections. See the coding-agent setup guide.
- A paired client. Follow the pairing guide. Pairing alone does not grant development access.
- Developer access to the approved project, or Owner access on your own device. App-only access permits one shared app, not the agent, source files or terminals.
- The host awake and online. Prepare the project start command if you want a live preview.
Costs are separate. Your Claude account, subscription and usage are billed by Anthropic, not included in Lyre. Off-network previews also use the host account's relay allowance; check current plan limits.
Connect and hand off the work
Open your saved connection
On the phone, connect to the computer that runs the project. For a first connection, pair it with the host owner and approve the intended project scope. Then confirm the computer name in Library before selecting the project.Choose Claude Code
Continue the existing Claude Code conversation for that project, or start a new one with Claude Code selected. Check the provider, account and available model before sending work.Ask before you edit
Start with a bounded question: what does the current code do, where is the relevant component, what check already exists. Read the answer before requesting a change.Request one change with a visible limit
Name the screen, the expected behavior and what must stay untouched. Ask for the smallest relevant existing check and for a report of what actually ran.Review the real result
Open Changes, read the diff, then open the app preview and repeat the failure you started with. A completion message is not proof; the diff and the running app are.
Example: fix a phone-sized tap target
This is a demonstration prompt for a sample restaurant site. Replace the button and screen with what you actually see in your project.
| Step | What to send |
|---|---|
| Inspect | Inspect the reservation page and explain why the Reserve button is hard to tap at a 390-pixel viewport. Do not edit files yet. Identify the relevant component and the smallest useful check. |
| Change | Make the Reserve button easier to tap at a 390-pixel viewport. Keep its text and reservation behavior. Limit edits to this issue, run the relevant existing checks, and report exactly what ran. |
One approval does not cover later actions. Commands execute under the host account. Read each provider approval for the command, file and scope requested, and answer only what you intend to allow. See the approval flow.
What a good check looks like
| Check | Where | What it proves |
|---|---|---|
| Diff scope | Changes | Only intended files changed and unrelated edits are intact. See reviewing changes. |
| Runtime behavior | Open app | The original failure is gone in the interactive preview, at the same width and flow. See open a preview. |
| Test output | Conversation and terminal | The named checks produced actual results. An agent summary alone is not a passing check. |
| Real network path | Mobile data | Off-network access reaches the same host, conversation and preview. See connection checks. |
When it does not work
- The computer is offline. Check power, sleep, network and whether Lyre is running, then reconnect. A phone cannot continue through an unreachable host.
- Claude Code refuses a request. Check installation, sign-in, account quota and model readiness on the host. Reconnecting the phone does not replenish provider usage.
- The preview fails or the phone disconnects. Inspect the saved start command and terminal output. After reconnecting, read the existing conversation before sending the task again.
- You need to stop. Use Stop in the conversation and inspect the resulting state. Closing the pane does not stop the agent or the app.
The host owner revokes the device grant in Pair device, then confirms the phone can no longer reopen the project. Uninstalling the phone client does not revoke access by itself.
App and agent have independent lifecycles: stopping a preview is not a request to stop the conversation, and disconnecting a phone does not stop work that is still running on the host.
Claude Code remote access questions
Do I need to install Claude Code again on the phone?
No. Claude Code runs on the host. The phone connects to that conversation and does not execute the agent locally.
Is the project uploaded to Lyre?
No. The project stays on the computer you paired. The phone receives the conversation, change views and, when configured, the app preview.
Can I use it over mobile data?
Off-network access uses Lyre’s relay path and the host account’s allowance. Test the real network path before relying on it, and check current plan limits.
What if someone else has the app link?
An App-only invitation is limited to the shared app and can be revoked. It does not grant the agent, source files, terminals or desktop control.
Sources for Lyre claims
- Public guide: use Claude Code from your phone
- Public guide: provider setup
- Public guide: files and changes
- Public guide: pairing and revocation
- Lyre documentation
Competitor descriptions link to each vendor's public documentation. This page is published by Lyre and is not a hands-on benchmark.