Bring your agent chats into Pane

Three ways in

One click in Settings, a first-run prompt on new installs, or just ask.

1. 1Find sessions. Open Settings → AI & Agents → Bring sessions into Pane and click Find sessions. Pane lists the chats you used in the last 30 days, one row per tool, with the last 7 days already ticked (at most 3 ticked per checkout). Click a row to choose, then click Bring them in.
2. 2The first-run screen. A new install asks “Bring your N sessions into Pane?”, counting chats running now or used in the last 7 days. Say Yes and Pane brings that set in, groups the work into Sessions and opens a Start here page that lists what came over and what was left out.
3. 3“migrate to Pane”. Say it in any Session, the chat in Pane that runs your agents. This one goes further: it also finds Cursor agent and OpenCode chats, looks inside WSL, and forks a chat that's still running onto a new branch instead of skipping it. It shows you one list and creates nothing until you confirm.

What happens to your chats

Same folder, same chat, nothing deleted.

• → Each repo opens in place. Pane adopts the checkout where it already is as a pane. Several chats in one checkout become tabs in that one pane.
• → Each chat resumes. Every tab starts the chat's own agent with that chat's own session id, so the history is there and the agent carries on.
• → Nothing is deleted. Pane reads each tool's files on your computer, and SQLite databases from a temporary copy. A transcript a tool kept in its own agent folder is copied into your own Claude Code or Codex folder first.
• → Nothing comes in twice. Find sessions and “migrate to Pane” share one record, so running either again only adds what's new.

What's left out, and why

Pane brings a chat in only when it can resume the real thing.

Pane would rather leave a chat out than open a fresh agent and pretend it's the old one. So these stay where they are:

• → Chats run by other agents. Amp, Gemini, Copilot and the rest are listed with a note that Pane can't resume them yet.
• → Chats still running elsewhere, in Find sessions. They're listed but can't be picked, and neither can other chats in the same checkout. For Emdash, Orca and Herdr, having the app open is enough to count as running. Quit them and press Check again, or say “migrate to Pane”, which forks them onto a new branch with your uncommitted files and leaves the original running.
• → A running Cursor chat. Cursor has no way to fork a chat, so “migrate to Pane” leaves it alone. Close it in Cursor and ask again.
• → Runs that aren't chats. claude -p and Agent SDK runs, codex exec runs, and subagent threads.
• → Claude Code chats started in a subfolder. Find sessions can't place them. “migrate to Pane” can.
• → Tools Pane doesn't read. For anything not listed above, try “migrate to Pane”: it looks for any tool that keeps resumable chats and treats it the same way.

One chat, one app

Don't drive the same chat from two apps at once.

Once a chat is open in Pane, keep working on it there. If the old tool and Pane both drive the same chat, they both write to the same transcript. Keep using the old tool for the chats you didn't bring over.

Sources

What we ran

• → Checked against Pane v2.4.214's docs and source on November 5, 2026

Corrections

If anything here is wrong or out of date, tell us and we'll fix it and update the date at the top. Open an issue on GitHub

Sources

• → Pane docs: Bring your existing sessions into Pane (v2.4.214)
• → Pane source: the tools Pane reads
• → Pane source: the agents Pane resumes
• → Pane source: the migrate-to-pane skill