[DOCS] Logical contradiction between Teleport requirements and Cloud Environment "Outcome" flow

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

The "Requirements for teleporting" table vs. the "Environment configuration" outcome flow.

Current Documentation

Under "Requirements for teleporting":

"Branch available: The branch from the web session must have been pushed to the remote. Teleport automatically fetches and checks it out."

Under "Environment configuration" (Outcome):

"4. Outcome: When Claude completes its work, it will push the branch to remote. You will be able to create a PR for the branch."

Under "What is Claude Code on the web?":

"Claude Code is also available on the Claude iOS app for kicking off tasks on the go and monitoring work in progress... teleport web sessions back to your terminal to continue locally."

What's Wrong or Missing?

There is a logical gap in the workflow description. The documentation suggests that users can teleport a session to their terminal to continue "work in progress." However, the technical requirements state that teleporting is only possible if the branch has already been pushed to the remote repository.

Contradictorily, the "Outcome" section states that the branch is pushed to remote only "When Claude completes its work." This implies that a user cannot actually teleport a session that is truly "in progress" or active, because the necessary remote branch wouldn't exist until the session is finished.

Suggested Improvement

The documentation should clarify at what point the remote branch is created and pushed. Specifically:

1. Does Claude push a "work-in-progress" branch as soon as the first edit is made?
2. If the user must wait until the "Outcome" phase (completion), the "work in progress" monitoring language should be clarified to specify that local continuation is only possible after a push event.

Suggested text for "Requirements for teleporting":
"Branch available: Claude creates and pushes a branch to your remote repository as soon as edits begin [or clarify the specific trigger]. This branch must be visible on the remote for Teleport to fetch and check it out locally."

Impact

High - Prevents users from using a feature

Additional Context

• Related Documentation: https://code.claude.com/docs/en/claude-code-on-the-web
• User Impact: A user attempting to follow the "monitoring work in progress" advice might try to /teleport an active session only to receive a "Branch not found" error because the agent hasn't reached the "Outcome" stage yet.