Remote Control Sessions

How one operation works

After you send a message from your iPhone, Klaus hands it to the currently selected desktop session. The engine on the desktop reads the project context, calls the model and tools, and syncs the process and results back to your phone.

Remote use therefore has two boundaries:

• Quitting the app or locking your phone does not move a task already handed to the desktop onto the phone; the desktop continues according to its own state.
• After the desktop quits, loses its network connection, or turns off remote control, the phone cannot start new operations until that device is back online and allows connections again.

Sessions and projects

The device scope determines whose data you are looking at. Choosing "All devices" aggregates the sessions in your account; after you select a specific device, new sessions and operations go to that computer.

From the phone you can browse existing desktop projects, open sessions, create new sessions, and rename, delete, export, or generate debug reports for the sessions you manage. The project directories themselves remain on the desktop — the iPhone does not get direct file access to those directories. Sub-agents dispatched within a session can also have their transcripts expanded and read on the phone.

One boundary worth stating clearly: cross-session communication — "one chat delegating work to another chat" — currently has its entry point only on the desktop. What you see on the iPhone is the results those delegations produced, not a way to initiate them from the phone.

Messages, attachments, and task status

• Text messages go into the current desktop session.
• Images and files are sent to the desktop as attachments of the current message for processing.
• The running reply, tool calls, and status keep syncing to the phone.
• Permission requests that need confirmation appear in the session and can be allowed or denied from the phone.
• When Klaus asks you something back (a follow-up card with options or an input field), it uses the same interaction: choose, fill in, and submit on the phone, or simply dismiss it to stop it from asking.
• Using the stop action asks the desktop to abort the current task.

When the network drops temporarily, the app tries to reconnect. While the UI clearly shows an offline or unstable connection, do not keep resending the same request; reconnect first and confirm the session state, so the task does not receive duplicate instructions once it resumes.