[Feature Request] Let a Claude Design conversation be shared/transferred to a different Claude account than the one it was created under
The request
Let a Claude Design conversation be shared or transferred to a different Claude account than the one it was created under.
Why
A Claude Design conversation lives entirely server-side, tied to the account that started it — unlike, say, a Claude Code CLI transcript, which is a local file the user can actually get to regardless of which account a given window happens to be logged into. If I'm running more than one Claude account (which is explicitly permitted) and a Design conversation was started under account A, there's no way to bring that conversation, or its output, over to a session running under account B. The only workaround is re-describing the whole thing from scratch in the second account, which defeats the point of the conversation existing at all.
This gets more painful specifically because Design work is meant to hand off to a paired Code session for implementation (see #77281 / #77551) — if the Code session that needs to consume that handoff happens to be running under a different account than the Design conversation, the conversation itself becomes stranded. It's not just "I'd like to view it elsewhere," it's "the natural next step of this workflow requires an account boundary to not exist."
What would fix it
Any of:
- A "share to another of my accounts" action on a Design conversation, similar to a shareable-link model but that actually opens/imports into a session under the target account.
- Export of a Design conversation (or at minimum its final state/output) in a form that can be re-imported as a live, continuable conversation under a different account — not just a static read-only artifact.
- If Design conversations are ever addressable by a stable ID, let that ID be resolvable across any account the same person is authenticated to, rather than scoped to the creating account only.
Related
Not a duplicate of any of these, but same general area (Design's isolation from the rest of the toolchain, and from account-switching in particular):
- #77281 — Design can't talk directly to its paired Code session; handoff is manual
- #77551 — no coordination workflow between Design and Code for asset handoff
- #77878 / #77620 / #75024 / #74387 — a cluster of Design auth/access failures around project grants and OAuth, different specific bugs but the same theme of Design's account/access boundary being fragile