Anyone else hitting the "this Chat just became a Cowork job" wall?

Now that Cowork is GA, I've been using it a lot more in my day-to-day as an IT Infrastructure Architect, and one thing keeps tripping me up. I'll start a quick Copilot Chat for what feels like a one-shot question (scope a policy, sanity-check a PowerShell snippet, sketch a config), and three or four turns in I realize the work is actually multi-step. Exactly what Cowork was built for. But there's no bridge between the two.

So, I'm stuck with two bad options: restart in Cowork and lose the context I just built up in Chat, or copy/paste fragments across and hope I didn't drop something important.

The other thing that catches me is the credit cost. Chat is a lighter-weight place to explore, and that's where most of my early turns belong. Without a clean bridge, the temptation is to start everything in Cowork "just in case it gets complex," which burns session credits on work that often turned out to be simple. Or I restart Cowork mid-conversation and effectively re-run the same prompts twice. A one-click handoff lets me stay in Chat as long as it makes sense and only graduates to Cowork when the work actually warrants it.

What I'd love to see is a simple "Open in Cowork" action in Chat that brings the conversation, referenced files, and any artifacts already produced into a fresh Cowork session, with my latest prompt as the starting task. Chat stays at the low-friction entry point, and Cowork picks up cleanly when the work grows up.

Curious whether others are running into the same thing, and if anyone has found a workflow that handles this cleanly today. Always interested in how the broader community is solving for it.

I created a User Feedback item for this if anyone wants to upvote it: 

https://feedbackportal.microsoft.com/feedback/idea/448ca034-c36c-f111-9b47-6045bdbd0989