[DOCS] Inconsistent terminology regarding "Moving" vs. "One-way handoff" for Web/Terminal tasks
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/claude-code-on-the-web#moving-tasks-between-web-and-terminal
Section/Topic
The "Moving tasks between web and terminal" section and its subsequent note on session handoff.
Current Documentation
The documentation states:
"You can move between local and remote development: send tasks from your terminal to run on the web with the & prefix, or teleport web sessions back to your terminal to continue locally."
It then follows with a Note:
"Session handoff is one-way: you can pull web sessions into your terminal, but you can't push an existing terminal session to the web. The & prefix creates a new web session with your current conversation context."
What's Wrong or Missing?
There is a logical inconsistency in using the phrase "move between" alongside "handoff is one-way."
- The introductory text implies a bidirectional "move" capability.
- The note clarifies that you cannot actually "move" or "push" an active terminal session to the web; you can only initiate a new session that clones the current context.
- This creates confusion for users who might expect their active terminal state (including uncommitted local changes or specific environmental state not captured in the context clone) to migrate to the cloud.
Suggested Improvement
The section should clearly distinguish between Context Cloning (Terminal to Web) and True Handoff/Teleporting (Web to Terminal).
Suggested Text Adjustment:
Change the section header or introductory sentence to:
"Transitioning between local and remote development"
Clarify the & prefix behavior:
"You can initiate remote execution from your terminal by using the & prefix to create a new web session based on your current context. To migrate an active session, use the teleport feature to pull web sessions into your local terminal."
Update the Note to be more explicit:
"Note: Session state migration is one-way (Web to CLI). Using the & prefix in the terminal does not 'upload' your current local session; it creates a separate, new remote session containing a snapshot of your current conversation context."
Impact
High - Prevents users from using a feature
Additional Context
- Related documentation on session management: https://platform.claude.com/docs/en/agent-sdk/sessions
- Documentation on the
&prefix: https://code.claude.com/docs/en/claude-code-on-the-web#from-terminal-to-web
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗