No way for a CLI session to retrieve results from a backgrounded Ultraplan/cloud session without manual browser steps

Title: No way for a CLI session to retrieve results from a backgrounded Ultraplan/cloud session without manual browser steps

Summary

Launching an Ultraplan (or any backgrounded Claude Code web/cloud) session from a local CLI session produces status notifications ("started", "ready", "approved · executing") but gives the CLI agent no way to actually retrieve the session's output. The user ends up manually relaying information between two Claude surfaces that are ostensibly part of the same product.

Steps to reproduce

1. In Claude Code CLI, build a plan and hand it off to Ultraplan for remote refinement.
2. Receive background notifications: session started, session ready (with a claude.ai/code/session_... link), plan approved and executing, "results will land as a PR."
3. Ask the CLI agent to check on progress or review the results.
4. The agent has no authenticated way to read the session page (WebFetch correctly 403s — it has no browser session/cookies), and no PR has been created yet, so it has nothing to inspect.

Expected

Some supported path for the CLI session to either:

• pull the current plan/diff/status from the linked cloud session programmatically, or
• be notified with the actual content (not just a link) when the cloud session reaches a milestone (plan ready, PR opened), or
• clearly document at hand-off time what the user must do manually (e.g. "open the link, and use teleport-back when ready") so there's no ambiguity or wasted back-and-forth guessing what state the remote session is in.

Actual

• The CLI session only receives terse status strings and a URL.
• The URL requires the user's own authenticated browser session; the CLI agent's tools cannot access it (WebFetch has no login context and gets HTTP 403).
• There's no indication in the CLI transcript of what actions are available on the web page (e.g. "teleport back") or when a PR has actually been opened, so the user has to keep checking the web page themselves and relay information back — the automation adds a middle step rather than removing one.

Suggested improvements

• Have the notification include an explicit action list ("open the link to review; use Teleport to bring the branch back to this CLI session; a PR will be opened automatically on completion").
• Consider giving the CLI session an authenticated, scoped way to read back the linked session's plan/status/PR link once it's the same logged-in user who launched it.
• If a PR is the intended terminal artifact, notify with the PR URL directly rather than requiring the user to poll gh pr list.

Environment

• Claude Code CLI (terminal), triggered /code-review-adjacent "Ultraplan" cloud planning flow from a local repo (3ll3d00d/ezbeq).