Claude Code on a phone: keep the session and project identifiable

Connect to the session you mean to control

The 28 February 2026 video introduces Claude Code Remote Control from a phone. The demonstration connects through a QR code at 0:24, then sends commands at 1:16. Start with a known session and project so the phone interaction has a clear destination; reaching a chat is different from confirming that it controls the work you intended.

1. Follow the QR-code connection shown in the recording without substituting an undocumented terminal command.
2. Identify the active project and current task on the connected session before sending new instructions.
3. Begin with a small question about the session’s state and compare the response with the work visible on the computer.

Review plans and changes in the live session

At 1:52 Luke uses remote control inside a live session. The description says you can send commands, approve plans and manage coding sessions away from the computer. Those actions have different consequences: a status question asks for information, while approval can allow a project change. Read the proposed action before choosing the next step.

1. State the intended change precisely and keep it tied to the current project rather than an ambiguous “continue”.
2. Inspect the complete plan and any relevant files or scope before approving it from the phone.
3. Check the resulting report and, when back at the computer, inspect the actual files or application behaviour affected by the change.

Keep cloud sessions separate from remote control

The bonus at 5:02 covers cloud-based Claude Code sessions started from claude.ai without a terminal. A newly created cloud session and a remotely controlled existing session are different routes. The description does not establish that they share the same local files, permissions or running processes automatically.

1. Decide whether you need to continue existing local work or start a separate cloud task before choosing the route.
2. For a new session, identify its actual project inputs and expected deliverable rather than assuming it inherited the computer’s context.
3. Keep completed work and remaining checks recorded so switching devices does not turn an unfinished attempt into an assumed result.

The takeaway

Remote access is useful when the target session and its actions remain clear; connectivity alone does not verify the project outcome.