Claude Code from anywhere. Your Mac stays the engine.

Where does the agent actually run?

Claude Code and the repository stay on your Mac. The glasses capture voice instructions and display the conversation. A cloud broker connects your paired devices to the relay running on the Mac.

In this setup the relay dials out to the broker, so you do not need to publish its local port. The glasses can be on another Wi-Fi network or a phone hotspot. A separate network is fine; no internet connection is not.

Do not confuse this with moving a development environment into Google Cloud. The cloud carries session traffic, but it does not keep Claude Code running after your Mac powers off. It also does not provide a backup of your repository.

Can you use Claude Code from your phone?

With the Rokid Claude phone companion, yes: pair your phone from the setup portal and open its browser-based client. You can send text or image context to the relay’s current session and follow its responses without using the glasses for that interaction.

This is not the Claude Code terminal running locally on a phone, nor is it a claim about every remote-access product. It is a connected client of the agent on your own Mac. The Mac must remain awake, online and authenticated; the phone needs internet access and a valid pairing credential.

Use the phone for precise text and attachments, the glasses for voice and brief progress checks, and the Mac for detailed code review. The phone companion guide explains the pairing steps and how to keep the context in the right session.

A checklist before you step away

1. Confirm the project: check the working directory and session you intend to use.
2. Set the boundary: give the agent a specific task, the files or area it should touch, and the verification you expect.
3. Check the host: the Mac should have power, network access and the relay running in its open Terminal.
4. Check the glasses: verify the connection and send a short instruction before leaving the desk.
5. Plan the review: decide which results you can read in the HUD and which require returning to a larger screen.

The supplied relay starter prevents idle sleep while it runs. Do not assume that closing a laptop lid, shutting down or losing power preserves the same behavior. Verify your Mac’s actual state rather than relying on the word “online” from an earlier check.

A practical use case: the test run and the coffee break

Imagine a checkout regression. At your desk, you select the project and ask the agent to investigate the failing test without changing unrelated code. You check the transcript, send the instruction, and take your coffee to a quiet terrace.

The Mac continues the work. You can glance at the progress when it is safe to do so, read the result, and ask for an explanation of the proposed fix. If the agent needs a screenshot or a precise error message, add it through the phone companion.

Then return to the Mac to inspect the diff and test output before merging. The benefit is a different way to spend the waiting period, not an exemption from engineering review. This is an example workflow, not a timed benchmark or a customer testimonial.

Stay reachable without watching every line

The glasses offer a small conversation surface, not a replacement monitor. Use it to check a task, clarify an instruction or respond to a completed session. You do not need to follow every tool event in real time to remain responsible for the outcome.

If you run several independent tasks, completion notifications can bring another session back to your attention. You can choose whether to go to it or stay with the current conversation. Read the parallel-session guide for queue behavior and file-isolation limits.

Choose surroundings where speaking is appropriate and looking at a display is safe. Do not use the HUD while driving or doing something that requires uninterrupted attention. Hands-free does not mean distraction-free.

What happens when the connection drops?

A dropped network connection does not necessarily stop a running task on the Mac. Restore connectivity and check the session state before sending the same instruction again. Otherwise, you may repeat work that already completed.

The relay stores session events and supports replay after a client reconnects. That is not a promise of uninterrupted service. If the Mac sleeps or the relay stops, the agent may be unavailable or a turn may be interrupted.

For a repeated disconnect, check the Mac, the relay and the glasses network separately. The troubleshooting guide follows that order.

What to keep in mind about data and access

Your repository and Claude credentials remain on the Mac, but session traffic passes through the cloud broker and is not end-to-end encrypted. Claude Code sends relevant context to its model provider according to your configuration. This is not an offline or zero-access service.

Keep relay commands and device-pairing codes private. Revoke paired devices you no longer control. Consider whether the task’s prompts, results and attachments contain confidential information before using the remote workflow.

For production changes, credentials, deployments or anything difficult to reverse, use an appropriate review process. Being able to speak an instruction from anywhere does not change the consequences of the tools it triggers.