Continue the same work across devices
Move from your desk to your phone and another paired computer while the original host keeps your project and conversation running.
On this page
Can I continue the same project from another device?
Yes. Connect each device to the same Lyre host and open the same project, workspace and conversation. You can start at your desk, follow the task on your phone and review it from another paired computer. The original host keeps the project files, agent and app processes; it must stay awake, online and running Lyre.
Prepare the host and each client
- A project and working agent on the original host. Check provider setup there before moving away from the desk.
- Compatible clients on the phone and second computer. Check downloads and device support; use Lyre on the other computer, the browser client, or a supplied compatible phone build as appropriate.
- Each client has its own authorized connection to the original host. Follow pairing for a new device, preferably on the same trusted network first.
- Developer access to the approved project, or Owner access on a device you trust with host administration. Pairing or signing into an account alone does not grant Developer access. Review roles and grants.
- A tested start command on the host if you want an interactive app preview. Save the startup configuration.
Local project work and local-network connections do not require a Lyre cloud account. Account-backed remote services have their own sign-in and allowance requirements. Provider subscriptions and AI usage costs are separate from Lyre; changing the screen you use does not change the selected provider's terms. See current plan limits.
Keep the host and client roles clear
| Part | Where it belongs |
|---|---|
| Project files and tools | The original host holds the working directory and runs project commands. A connected laptop can act as a client without moving those files onto it. |
| Conversation and running work | Open the existing host-run conversation on each authorized client. Read its latest messages and task state before sending another request. |
| Drafts and views | Unsent drafts and pane state belong to their client. Do not assume they appear on another device. Save file edits successfully and send or deliberately keep a message draft before moving. |
A second computer can be a host for its own projects and a client for this one. Check the selected computer each time: opening a local copy there creates a different work context. This workflow does not copy a repository, migrate a running process or merge separate conversations.
If you want files and tools on a laptop while a stronger computer supplies inference, follow use desktop models on a laptop. That model-lending workflow has separate execution and model-source computers; see the model connection owner.
Move from desk to phone to another computer
-
At the desk, identify the work you will continue
In Library, open the project and its existing workspace or worktree. Note the host, workspace and conversation names. Review current progress and save any file edits. Keep the host awake with Lyre open.
-
On the phone, open the original host connection
Use the saved connection; an unconnected client offers Connect from Library. Select that host's project, the same workspace or worktree, and the existing conversation. Read the latest reply or pending approval before sending a follow-up. Open app opens its prepared preview for touch testing.
For provider-specific steps, use Claude Code from your phone or Codex from your phone.
-
On the second computer, connect back to that host
Open its saved connection or pair this computer through the existing connection flow. In Library, select the original host and the same project, workspace and conversation. Review Changes or try the app there. You do not need to add a local clone to continue this host-run task.
Example: review a task away from your desk
Suppose you started a small website change on your desktop and want to check it from your phone. After opening the same conversation, use this example request if the task state needs explaining:
Summarize the latest change in this workspace and the checks already run.
Tell me whether you are waiting for input and what I should try in the app.
Do not edit files or start another copy of the app.Try the reported behavior in the phone preview. If you need to send an image, use the supported preview screenshot controls and review the attachment before Send. A screenshot is context for the chosen provider; it does not grant access to another device, project or whole desktop.
On the second computer, inspect the actual diff and check output before asking for another change. These are example steps to run, not a record of a completed customer task.
Leave a screen without stopping the work
Closing a conversation pane or disconnecting a client does not stop the host-run agent. Use the conversation's Stop control when you intend to stop its turn, then inspect the resulting state. The app and agent have independent lifecycles: stopping one does not establish that the other has stopped.
A disconnected terminal can still have a running process on the host. Reconnect and inspect it before starting another copy. Closing a preview viewer and stopping the app process are separate actions. See terminal and script controls and app lifecycle controls.
The existing host conversation carries its recorded messages and task state. An unsent draft or unsaved editor change on one client is not proof of a host save or a draft on the next device.
Check continuity on each screen
-
Check identity and recent history
On the phone and second computer, confirm the original host, project, workspace and conversation. Read a recent host-recorded message and compare the task state. A similar project name alone does not identify the same work.
-
Check an actual result
Inspect a saved change or use the preview to reproduce the behavior you are testing. Read the actual check output; a connected indicator, agent completion message or running process does not prove the app works.
-
Check the return and remote route
Disconnect one client, reconnect and reopen the same conversation. Confirm that it can show fresh host state before sending another request. If you need off-network access, repeat on mobile data or an outside network using remote connection checks; same-network success is a separate result.
All three screens reach the same host-run work, recorded messages and saved changes are available with the right grants, and reconnecting lets you continue without creating a replacement task.
Recover the affected connection
- The original computer is offline
- Check power, sleep, network and whether Lyre is running on that host. Use offline recovery, then reconnect. Opening another computer does not resume a process on the unreachable host.
- A phone returned from the background with stale progress
- Check the named computer and connection status. Let reconnection settle or use the available retry/Connections action. Read fresh conversation state before resending a request; the prior task may still be running. Queued requests have their own conversation owner.
- The project or conversation is missing or denied
- Confirm the selected host and workspace. Ask the host owner to check that this device has the intended project grant. App-only access cannot open agents or source; reconnecting does not widen it. Use the existing access controls.
- The app or provider fails while the host is reachable
- Inspect the actual preview error and script output, or the provider account readiness and quota. Use preview recovery or provider recovery. A working connection does not repair an app or replenish model usage.