Preflight Checklist
Problem Statement
Today there’s a hard split:
• Desktop CLI sessions run locally on my machine. They have full access to my local environment, files, and tooling — but they don’t appear on mobile.
• Web/mobile sessions run in cloud containers tied to a GitHub repo. They sync across devices, but they don’t have access to my local environment.
This forces a choice up front: either I commit to a cloud session (and give up local context) or I commit to a desktop session (and give up mobility). I often don’t know I’ll need mobility until I’m already deep into a desktop session.
Proposed behavior
While the desktop CLI is running and online, expose the live session to the mobile app — read-only at minimum, ideally with the ability to send new prompts and approve tool calls from the phone. The desktop machine remains the execution host; the phone is just another view/controller.
Why this is “the dream”
It removes the device-choice tax. Start work at my desk, walk away, keep going on my phone, come back to my desk — one session, one context, no migration.
Notes
• Auth/pairing could be handled the same way the web app authenticates today.
• Doesn’t require any cloud execution — desktop stays the host.
• Connection drops (laptop sleeps, network blips) could gracefully pause the mobile view until the desktop reconnects.
Proposed Solution
While the desktop CLI is running and online, expose the live session to the mobile app — read-only at minimum, ideally with the ability to send new prompts and approve tool calls from the phone. The desktop machine remains the execution host; the phone is just another view/controller.
Alternative Solutions
None
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
It removes the device-choice tax. Start work at my desk, walk away, keep going on my phone, come back to my desk — one session, one context, no migration.
Notes
• Auth/pairing could be handled the same way the web app authenticates today.
• Doesn’t require any cloud execution — desktop stays the host.
• Connection drops (laptop sleeps, network blips) could gracefully pause the mobile view until the desktop reconnects.
Additional Context
No response
Preflight Checklist
Problem Statement
Today there’s a hard split:
• Desktop CLI sessions run locally on my machine. They have full access to my local environment, files, and tooling — but they don’t appear on mobile.
• Web/mobile sessions run in cloud containers tied to a GitHub repo. They sync across devices, but they don’t have access to my local environment.
This forces a choice up front: either I commit to a cloud session (and give up local context) or I commit to a desktop session (and give up mobility). I often don’t know I’ll need mobility until I’m already deep into a desktop session.
Proposed behavior
While the desktop CLI is running and online, expose the live session to the mobile app — read-only at minimum, ideally with the ability to send new prompts and approve tool calls from the phone. The desktop machine remains the execution host; the phone is just another view/controller.
Why this is “the dream”
It removes the device-choice tax. Start work at my desk, walk away, keep going on my phone, come back to my desk — one session, one context, no migration.
Notes
• Auth/pairing could be handled the same way the web app authenticates today.
• Doesn’t require any cloud execution — desktop stays the host.
• Connection drops (laptop sleeps, network blips) could gracefully pause the mobile view until the desktop reconnects.
Proposed Solution
While the desktop CLI is running and online, expose the live session to the mobile app — read-only at minimum, ideally with the ability to send new prompts and approve tool calls from the phone. The desktop machine remains the execution host; the phone is just another view/controller.
Alternative Solutions
None
Priority
Critical - Blocking my work
Feature Category
CLI commands and flags
Use Case Example
It removes the device-choice tax. Start work at my desk, walk away, keep going on my phone, come back to my desk — one session, one context, no migration.
Notes
• Auth/pairing could be handled the same way the web app authenticates today.
• Doesn’t require any cloud execution — desktop stays the host.
• Connection drops (laptop sleeps, network blips) could gracefully pause the mobile view until the desktop reconnects.
Additional Context
No response