Review AI agent changes from your phone
The agent keeps working on your computer. You read the diff, answer the approvals that matter, try the running app and decide whether the change is done.
Reviewed against Lyre's public guides. Check current device support and plan limits before you rely on them.
The short answer
Yes, and the phone is often the better place to review. You are away from the editor, so you look at the result the way a user will: the diff, the running app and the reported checks. What you cannot do from a phone is assume that a completion message means the change is correct.
The review loop
This works with Claude Code, Codex and other providers Lyre can connect. The controls are the same; the provider owns its own approval prompts.
Restate the scope
Before reading code, write down what the task was supposed to change and what it was supposed to leave alone. A vague goal makes every diff look acceptable.Read the diff, not the summary
Open Changes and read the files. Check for unrelated edits, deleted behavior, new dependencies and anything that touches secrets or configuration. See reviewing changes.Answer approvals deliberately
A provider approval is for a specific command, file set or scope. Read it and answer only what you intend. Approval of one action does not authorize later actions.Run the app and repeat the original problem
Open the preview and do the thing that was broken. Check the narrow width, the long label, the empty state or the error path that motivated the task. A running process is not a working app. See open a preview.Confirm the checks actually ran
Read the commands and their output. If the agent says tests passed, find the result. If it could not verify something, keep that limit visible in your decision.Decide: accept, request a fix or stop
Accept only when the diff, the app and the checks agree. Otherwise send one specific correction. If the turn is going the wrong way, use Stop and inspect the state it left.
What to check before you accept
| Question | Where to look | Red flag |
|---|---|---|
| Is the change the size I asked for? | Changes | Unrelated files, formatting churn or a rewritten module for a one-line fix. |
| Does the original problem stay fixed? | Open app | Only the agent’s description changed; the screen still fails at the same width or step. |
| Are the checks real? | Conversation and terminal | No command output, a skipped suite, or a claim that something was verified without a result. |
| Did anything sensitive move? | Changes and settings | New environment files, keys, permissions or network calls that the task did not require. |
Keep unrelated work intact. If the workspace already has edits you did not make, read them before judging the agent's change. Do not discard someone else's draft to make a review easier.
What a phone review cannot prove
- A full test suite passed. You see what actually ran. If the relevant suite was skipped, the review is incomplete.
- Every device works. A preview proves the path you tried, on the client you used. Native store builds and other devices keep their own checks.
- The change is deployed. Preview, share and publish are separate workflows. A working preview is not a published release.
- Access is appropriate. App-only viewers see the app, not the agent or source. Granting one does not grant the other.
Review from a device the host owner has approved. Developer access is limited to approved projects; allowed commands still execute under the host account.
Share a running app with a reviewer through an App-only invitation when they only need to try it. That invitation covers one app and can be revoked. It does not expose conversations, files, terminals or desktop control.
When the review is interrupted
The host drops offline
- Reconnect after the computer is awake and online.
- Read the existing conversation before sending anything again; the previous turn may not have stopped.
The diff is confusing
- Ask the agent to explain the current diff and name the files it touched.
- Do not approve a change you cannot describe in one sentence.
The preview will not start
- Check the saved start command and terminal output on the host.
- Fix the actual failure instead of starting a second copy of the app.
You need to stop now
- Use Stop in the conversation, then check what state remains.
- Closing the pane is not a stop, and disconnecting the phone does not stop host work.
Phone review questions
Can I review code changes on a phone without a laptop?
Yes, for the diff, the conversation, approvals and the running app preview. The computer that owns the project still has to be awake, online and running Lyre.
Does opening the preview start the app on my computer?
The preview uses the project’s configured start command on the host. If no command is configured, set one on the host before relying on the preview.
Can a reviewer see my source if I share the app?
No. An App-only invitation grants the shared app only. Agent conversations, source files, terminals and desktop controls require a separate grant.
How do I remove review access afterwards?
The host owner revokes the device or invitation in Pair device, then confirms the client can no longer open the app or project. Uninstalling the client is not enough.
Sources for Lyre claims
- Public guide: files and changes
- Public guide: conversations and approvals
- Public guide: app previews
- Public guide: pairing and revocation
- Public guide: review and handoff
- Lyre documentation
Competitor descriptions link to each vendor's public documentation. This page is published by Lyre and is not a hands-on benchmark.