Cloud sessions (ultraplan) cannot deliver changes to user repos — patch transfer corrupts diffs

Summary

/ultraplan cloud sessions can generate changes but have no reliable mechanism to deliver them to the user's repo. The only current option is git format-patch copied through the web UI clipboard, which corrupts unified diffs.

What happened

/ultraplan ran in a cloud sandbox, made 467 insertions across 8 files, committed cleanly — but could not push to the remote. The session produced a git format-patch that the user had to copy-paste to their local machine. The patch was corrupted during transfer in two ways:

1. Duplicate hunk header. A @@ line was doubled, causing git am to fail immediately and leave the repo in a stuck "am session" state.
2. Blank line lost its + prefix. A +\n line inside added content was reduced to bare \n, breaking the unified diff format. This required byte-level inspection to diagnose.

Fixing required understanding unified diff internals. A typical user would have been stuck.

Suggestions (in order of impact)

• Best: Let cloud sessions push to the user's remote (scoped OAuth token or deploy key for the session duration)
• Good: Provide a claude code pull <session-id> CLI command that fetches the session's commits over an authenticated channel (not clipboard)
• Minimal: If patch files remain the mechanism, serve them as downloadable binary files (not rendered text), so byte-level content survives intact