You plan a feature in the Claude app. The decisions, the trade-offs and the spec all live in that chat. Then you open Claude Code to build it, and it knows none of it. That transition, from planning in Claude to building in Claude Code, is where context gets lost. There is no built-in way to transfer a Claude chat into a Claude Code session, so most people paste a rushed summary and lose the details. The cleaner way is a handoff doc. Have Claude compact the chat into one doc, stash it on DocStash, and hand Claude Code the link.
Why a Claude chat doesn't carry over
The Claude app and Claude Code keep separate histories. A Claude Code session starts fresh in your project, so the chat where you worked everything out stays behind.
- No transfer. Claude Code can't open or resume a conversation from the Claude app.
- Copy and paste doesn't stick. A pasted summary lives in one session. The next one starts empty.
- Context drifts. Once the build starts, the plan changes, and the chat you planned in falls out of date.
A handoff doc fixes all three, with one doc that holds the plan, a link Claude Code can read, and a place to keep it current while you build.
The usual workarounds, and why they're more work than they need to be
People have found ways to bridge the transition. They work, but each one adds steps you repeat every time.
- A CLAUDE.md file in the project folder. Ask Claude for a summary, copy it into a Markdown file, save it as
CLAUDE.mdor reference it from there so Claude Code reads it at the start of a session. Every change to the plan means another round of copying and saving by hand. - Pasting a summary into the first message. The quickest option, but the summary lives only in that one session. Start a new session and you paste it again, and whatever changed during the build never makes it back.
- Browser extensions and local bridges. Third-party tools that copy the chat to your machine and feed it to Claude Code. One more thing to install, trust with your chats, and keep working.
A handoff doc skips all of it: no files to manage, nothing to install, and the same link works for every session after.
Hand off with one link
DocStash is a home for the docs your AI makes. Connect it to Claude once and Claude Code has it too. Have Claude compact the chat into a handoff doc and stash it, and you get one link that Claude Code reads at the start of a session. The transfer takes one prompt on each side.
Transfer a Claude chat to Claude Code
- Connect Claude to DocStash. Add DocStash as a connector in Claude. Connectors sync across your Claude account, so Claude Code signed in with the same account has it too.
- Ask Claude for a handoff. In the chat, say "Compact this whole chat into a handoff doc for Claude Code and stash it on DocStash." Claude writes the decisions, the spec and the open questions, then saves it.
- Hand it to Claude Code. In your project, start Claude Code and say "Continue from docstash.ai/<slug>. Build it." Claude Code reads the doc and starts from the plan.
- Keep it current. When the build changes the plan, ask Claude Code to update the same doc. The link stays the same, and Activity keeps every version.
FAQ
Can Claude Code open my Claude app chats?
No. Claude Code and the Claude app keep separate histories, so a Claude Code session can't see your chats. A handoff doc is how the context crosses over.
Does this transfer the whole chat?
No. Claude writes a compact handoff doc with what still matters, not the raw transcript. DocStash only stores that doc.
Can I hand off the other way, from Claude Code back to Claude?
Yes. Ask Claude Code to update the handoff doc, then open it in a Claude chat to review the build or plan the next step.
Is the handoff doc private?
Yes. It stays private until you choose to publish it or share it with specific people.
Hand off from Claude to Claude Code
Connect Claude to DocStash and move any plan into a build from one link.
Get started