Resume a Claude Cowork conversation in Claude Code.

Cowork locks the model for the life of a session. cowork2code moves the whole session — conversation, files, and MCP servers — into Claude Code, where the model is just a flag. Pick the thread back up on any model you want.

$ uv tool install git+https://github.com/looptech-ai/cowork2code View on GitHub

One line, the CLI's on your PATH. Want the MCP server too? git clone … && ./install.sh

Claude Coworklocked

LLM-productivity emerging trends

claude-haiku-4-5
model is fixed for the session
Claude Codeunlocked

LLM-productivity emerging trends

opus-4-8[1m]
switch the model with /model, anytime

The essential idea

The whole session comes across

A Cowork session is a working environment, not just a chat log. cowork2code carries all of it into Claude Code — and never touches the original.

01

The conversation

Re-homed as a native Claude Code session you resume with claude --resume on any model.

02

Every working file

The session's outputs/ and memory/ are copied into your target directory.

03

The MCP servers

Written to a ready-to-use .mcp.json so Claude Code reconnects them automatically.

04

Skills & plugins

Already shared with Claude Code on your machine — available the moment you resume. The sidecar records which the session used.

How it works

Three commands, same conversation

It isn't a converter. A Cowork session already stores its transcript in Claude Code's own format — cowork2code re-homes it, rewrites the paths, and hands you the resume command.

cowork2code — zsh
$ cowork2code list
2026-06-12 09:41 claude-haiku-4-5-20251001 Research: emerging LLM trends id=local_e518…
 
$ cowork2code rehome --title "emerging" --into ~/dev/llm-resume
Session: Research: emerging LLM trends (claude-haiku-4-5 -> opus-4-8[1m])
Copied 3 files · MCP servers -> .mcp.json · notes -> COWORK_SESSION.md
 
cd ~/dev/llm-resume && claude --resume a1803cbc… --model 'opus-4-8[1m]'
 
$ cd ~/dev/llm-resume && claude --resume a1803cbc… --model 'opus-4-8[1m]'
# the full conversation loads — now on Opus.

Two ways to drive it

A CLI you run, and an MCP an agent runs

Command line

cowork2code

For you. List your sessions, then re-home one into a working directory.

  • Select by --title, --id, or --from
  • Target a fresh dir (--into) or the original (--original)
  • --dry-run, --launch, --new-id, --model
Local MCP server

cowork2code (MCP)

For an agent. Ask Claude Code in plain language; it does the migration for you.

  • cowork_session_list — sessions as structured JSON
  • cowork_session_rehome — migrates and returns the resume command
  • Registered automatically by ./install.sh