THE SHORT ANSWER
Separate Claude Code sessions can run in parallel through the relay. A single session accepts one running turn at a time. Switching the session you view does not cancel the work elsewhere, but it does not create a separate working copy of the repository.
Project, session and turn: three different things
A project is the working directory where the agent operates. A session is a conversation with its own Claude context. A turn is one instruction and the agent work that follows it.
These distinctions explain the concurrency rules. Two sessions may each have a turn running. A second turn cannot run at the same time inside the same session because the two processes would compete over the same conversation history.
The glasses show your selected conversation. They are not a wall of simultaneously scrolling terminals. Switching the view changes what you interact with, not whether another session is allowed to finish.
Start a task, then change your focus
- Choose the intended project and session. Check the visible project name before sending an instruction.
- Give that session a scoped task and confirm the transcript.
- While it runs, tap to open the running-task menu and choose Switch session or Switch project.
- Select another existing conversation, or start a new one in the intended project.
- Give the second session its own instruction. The first session can continue independently.
Switching projects selects another working directory and starts a fresh session. Resuming an existing session is a separate action. If you expect to continue a specific thread, select that thread rather than treating every new project selection as a resume.
Queue a follow-up or interrupt the current turn?
Use Queue an instruction when the next request belongs after the current turn. For example, let the implementation finish, then ask for a concise summary of its changes and test results.
A queued instruction is tied to the session context in which it was added. If you switch sessions, that queued instruction is dropped rather than being sent to a different conversation. Do not queue a task and assume it will follow you through subsequent session switches.
Use Interrupt now when you need to stop the current direction. Interruption is not an undo operation: file changes or commands already completed may still have effects. Inspect the repository before asking the agent to continue or reverse a change.
A result can come back to your attention
When another session finishes, the app can show a completion notification and wake the display. Choose Go to it to inspect that conversation, or Stay here to keep your current focus.
Notifications reduce the need to open every session repeatedly. They are not a guarantee that every outcome is correct or that an offline device will alert immediately. Check the session result and any reported errors, especially after a network interruption.
When returning to a conversation, read its latest exchanges before sending a new instruction. A short question such as What changed, and what still needs verification?
can help you reorient, but the answer still needs review.
Parallel conversations are not isolated workspaces
Two sessions pointed at the same working directory can edit the same files. Separate conversation histories do not prevent conflicting changes, shared test-state interference or one agent reading another agent’s unfinished work.
Use separate working copies or deliberately prepared Git worktrees when tasks might overlap. Set those up and verify their branches on the Mac before treating them as separate projects. Rokid Claude does not automatically create worktrees for every session.
A safer example
One session explains a module without changing files. Another drafts documentation in a separate working copy. You review their results on the Mac before combining anything. This has clearer boundaries than sending two agents to refactor the same module at once.
Claude access limits and the Mac’s available resources still apply. Parallel does not mean unlimited.
Multiple sessions are not multiple connected hosts
Sessions on your selected relay are different from saved host profiles. The glasses can remember several named relay connections but connect to one host at a time. That profile switch is not an automatic Claude account change or a cross-host session dashboard.
If a session disappears after changing hosts, first verify which Mac you are connected to. Its repositories and Claude history may be different. For missing projects or stale session history, use the diagnostic checklist rather than creating another duplicate conversation.
Based on the current Rokid Claude application and setup flow. Early-access behavior and compatibility may change.