[DOCS] Contradictory statements regarding "pushing" terminal sessions to the web

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/claude-code-on-the-web

Section/Topic

The section titled "Moving tasks between web and terminal", specifically the note box and the "From terminal to web" subsection.

Current Documentation

The documentation currently states in a Note box:

"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."

Immediately following this, under "From terminal to web", it states:

"Start a message with & inside Claude Code to send a task to run on the web... This creates a new web session on claude.ai with your current conversation context."

What's Wrong or Missing?

These two statements are contradictory and confusing to the reader.

The first sentence explicitly says "you can't push an existing terminal session to the web." However, the very next sentence explains that using & creates a web session "with your current conversation context."

To a user, sending the "current conversation context" from the terminal to the web is pushing the session data. The distinction appears to be technical (you cannot resume the specific local Session ID on the web) rather than functional (you can't move your work to the web), but the phrasing "can't push" makes it sound like no data transfer is possible at all.

Suggested Improvement

The documentation should clarify the technical distinction between "resuming a session ID" and "forking context."

Suggested Revision:

"Session synchronization has specific limitations: while you can pull web sessions into your terminal to resume them, you cannot resume an existing terminal session ID on the web. However, you can fork your current terminal conversation history into a new web session."

Impact

High - Prevents users from using a feature

Additional Context

This clarification is important because users reading "you can't push" might stop reading there and assume they cannot offload their current local context to the cloud, even though the feature exists via the & command.