Move a live agent session to another workspace via CLI/RPC (UI optional)

[cncolder]

Use case

A Paseo agent started in the main-repo workspace creates a git worktree via the project skill (custom path .worktrees/JIRA-123, sparse checkout — steps Paseo cannot do itself), then registers it with Create workspace (isolation: "local"). The session must then continue working in that worktree, and the UI should show the session under the new workspace.

Requested

Allow moving a live agent session across workspaces via CLI/RPC (UI optional):

• RPC like agent.workspace.move.request {agentId, workspaceId} (optionally cwd) that rebinds the live agent record, persists it, and emits agent/workspace updates — without restarting the provider process.
• CLI counterpart for scripting/automation.
• Validation: target workspace must exist and be active; clear error otherwise.

Context

Today the session workspace binding is fixed at creation: the live agent record workspaceId has no setter, the Update agent tool only handles name/labels/mode/model/thinking/features, and there is no move/reparent RPC. The only rebind code path is agentManager.unarchiveSnapshot (archive-resume flow). This is the Paseo equivalent of Cursor's move_agent_to_cloned_root.

Originally filed as issue #3255 (closed as not-a-bug; moving here per the contributing guide).

[viet-initx]

+1, hit this too. Filed the workspace-level sibling of this request (moving a whole workspace, not just a live session, across projects) since the only workaround there today is a lossy re-import: #3453

[axsuul]

I would love this as well because often I will brainstorm something in a session and then once it looks good, I wanna move all that context to the new workspace.

[aaronhall]

+1

Closely related to the UI side of this, I often find myself looking for a "Promote tab to new workspace" option in the context menu.

[apple-ouyang]

Implemented the display-side half of this in #5887: agent tabs can move between workspaces from the tab menu or by dragging onto a sidebar row, and the placement/closed/order state syncs across connected clients through daemon agent labels. The agent keeps running in its original directory. (The daemon-side workspaceId reassignment this discussion describes would be the complementary piece for vanilla clients.)

[apple-ouyang]

I have been carrying a local daemon-side prototype for this request and wanted to document the smallest upstream shape before opening a PR. The complementary display-side half is in #5887; it moves the tab and syncs placement labels, while the agent itself keeps running in its original directory.

Proposed source-only implementation:

• Add agent.workspace.move.request with { agentId, workspaceId } and a matching CLI command. cwd remains unchanged; moving ownership should not implicitly move a worktree or restart a provider.
• Validate that workspaceId exists and is active before mutating anything. Return a structured error for unknown, archived, or archiving targets.
• Run the mutation in the same per-agent lifecycle lane used by metadata updates. For a live agent, update the canonical in-memory ManagedAgent record and persist the snapshot/registry record. For an unloaded agent, update the stored record directly. Preserve provider/session/cwd/labels and only change workspaceId.
• Emit the normal agent state update after persistence. Existing workspace projections and subscriptions can then regroup the agent on every connected client, including vanilla clients. The provider process is not touched.
• Keep this as a first-class RPC rather than a magic label. The local prototype used update_agent_request plus paseo.moveToWorkspace only as a bridge for the installed app; I would not carry that compatibility mechanism into upstream.

The focused tests I would include are: live agent move with no provider restart, unloaded/stored agent move, persistence after reload, broadcast of the new workspaceId, and rejection of unknown/archived targets with no write. If this shape fits the project direction, I can prepare a source-only PR on top of current main.

[starsy]

I also need this for session organization in the Paseo app.

Once I open a session in a workspace, I cannot move it to another workspace. This prevents me from reorganizing existing sessions as my work changes.

Requested scope:

• Allow moving an existing session between workspaces within the same project that share the same project root.
• UI support is required. Add a "Move to workspace…" action that lets me select an eligible destination workspace. CLI or RPC support alone does not meet this need.
• Preserve the session and its conversation history, so I can continue the same session in its new workspace.
• Do not silently change the session's working directory.

My main need is to reorganize sessions within a project. Moving sessions between different projects is outside this request.