Starting a cloud session shows labelled steps, byte sizes, and a clearer cancel message.
What's wrong with this entry?
Starting a cloud session now walks through labelled steps: checking the checkout, packaging and uploading local changes or the repository, then creating the session, with byte sizes and a note on how much history is included. Cancelling tells you whether the create request had already gone out, in which case a session may exist anyway.
- History scope is annotated on the line, for example "with history" or "snapshot without history".
- A fallback line explains that the session will start from the branch tip with file sync off when local changes cannot be packaged.
Cancelled after the create request was sent, so a cloud session may still have been created
Strings lifted out of the shipped bundle, so the claim above can be checked against them.