Test from another screen
Understand pairing, remote access, and who can change your project.
On this page
The app runs on your computer
Your phone does not run the app. It connects to your computer, the host, to view and interact with the project. Keep the host powered, online and running Lyre.
- Lyre open on the computer that runs your project.
- A paired phone, tablet or second computer. Pair a device →
- Both devices on the same trusted network to start with.
-
Keep the host ready
Powered on, online, and Lyre open.
-
Pair the device
Approve the access you intend on the host. Pairing alone does not grant developer access. See Pair device.
-
Open the app there
Find the prepared app from Apps and try the flow you are testing.
Testing from outside your network needs a supported, configured remote connection. Local-network testing is verified separately from deployed off-network access. Never expose the desktop’s internal ports to the public internet as a shortcut.
the app opens on the second screen and responds there, and the computer is still awake and online.
What is free and what needs Pro
Free includes 30 minutes per account per UTC month shared across remote app previews and remote desktop on all devices. Sign in on the host to use the remote allowance. Local and LAN viewing have no time limit. Existing traffic limits still apply. Remote previews use your account's application relay allowance; hosted video fallback has a separate paid allowance.
| What you do | What it needs |
|---|---|
| Connect remotely, edit code, work with agents, start projects | Free. |
| App previews on your local network | Free. |
| Live app previews outside your local network | Included on Free within the application relay allowance. See plan limits. |
| AI provider usage | Charged by your provider, separately. |
you can say which of the four rows above covers what you are doing.
Choose access deliberately
An invitation is not permission to do everything. Each role grants a different set of actions.
| Role | What it means |
|---|---|
| Owner | Manages the computer, its pairings and access grants. |
| Developer | Can use the development actions granted for approved projects. |
| User: shared apps only | Can interact with the apps shared with them. That does not grant source, terminal or agent access. |
Use the access controls in your installed build. An invitation must not be treated as permission to do everything on the host.
Grant the smallest role that does the job. You can widen it later.
the device you are testing with has the narrowest role that still lets you do the test.
If the computer is offline
-
Check power and network
Is the host awake and connected?
-
Check Lyre
Is Lyre actually running?
-
Retry once it is reachable
Try the connection again after the host is back.
On devices offering Wake, use the host's configured wake permission and supported network setup, then retry the connection. Wake setup and offline recovery.
the device reaches the host and the app opens again.
Local does not mean every service is offline
Your project runs locally, but a cloud coding assistant, speech service or integration may receive the context you send to it. Check the provider and destination before sharing code, screenshots or recordings.
Read the privacy and connection model.
Decide where the data goes before you dictate it, screenshot it or send it to an agent, not afterwards.
you know which service receives what for this test.