Dragging a tab should move the live thing.
Zed's 1.24.1 pre-release lets a terminal tab move into the Agent Panel. The merged pull request says the implementation reuses the existing terminal instance, preserves its title and state, removes it from the source pane, and activates it as an Agent terminal. A regression test covers the drag.[1]
That is the right unit of movement. A screenshot, copied command, or fresh shell can look similar while losing the running process, scrollback, working directory, and environment. Reusing the instance keeps continuity where a visual imitation would break it.
A panel move is successful when the session survives, not when the rectangle lands.
Preserved text still needs preserved structure.
OpenAI's Codex 0.162.1 fixed a related presentation failure in asynchronous questions. One terminal line had erased line endings and shifted hyperlink ranges away from the visible text. The repair wraps and annotates each logical line, keeps blank lines, accepts LF and CRLF endings, and tests narrow and wide widths.[2]
The lesson is smaller than a universal design rule. Terminal content has structure. A transfer that keeps every character but changes its line boundaries can still change what a person reads or where a link points.
Working directory is part of authority.
Claude Code 2.1.296 fixed plugin methods that ran in the main session's working directory instead of the calling agent's directory. The release also says those methods had ignored the turn held by the calling hook.[3] This is adjacent evidence, not a report about Zed. It shows why placement and execution context must remain separate in a review.
A terminal inside an agent panel may feel agent-owned even when the process, directory, credentials, and approval path came from somewhere else. The interface should name what moved and what did not. If the product cannot expose that record, write it into the handoff.
Test return, not only arrival.
A useful transfer test checks the live process before and after the move. It records the directory, confirms that old output remains readable, sends one harmless command, and moves the terminal back. The final check verifies that the same session returned and that no duplicate shell remained behind.
Do not infer credential safety from continuity. Preserving a terminal preserves its risks too. Use a disposable project, a harmless process, and a command with no network or write side effects for the first test.