DreamLake

Moving files and folders

Drag a file or folder onto another folder in the project's file list. Select several rows with Ctrl/Command-click or Shift-click, then drag one of the selected rows to move the selection. A highlighted folder indicates a valid destination. You can also open a row's context menu and choose Move to…, browse folders, and confirm with Move to [folder name]. Folder rows open subfolders; the breadcrumb shows the location being browsed. The destination summary displays the full target path, and the current location cannot be confirmed. Keyboard users can open the menu with Shift+F10.

Selecting items

A plain click selects one item and opens its preview or folder. Ctrl/Command-click adds or removes an item without opening it. Shift-click selects the continuous range from the last plain or Ctrl/Command click; clicking closer to that starting point shrinks the range. Ctrl/Command+Shift-click adds a range to the existing selection.

With a list row focused, Shift+Arrow keys or Shift+Home/End extend the selection. Ordinary arrow keys only move focus. Ctrl/Command+A selects the currently loaded, visible rows, and Escape clears the selection without closing the preview. Search, content-filter and sort changes clear the old selection; hidden items are never included. The selected count shows when more rows remain unloaded.

Dragging a selected row moves the highlighted selection. Dragging an unselected row selects and moves that item alone. Right-clicking inside a selection preserves it for Move to…; right-clicking outside selects the clicked item. Rename and delete remain actions on the clicked item. Unsupported node types can be selected for browsing but cannot be included in a file-move batch.

The list waits for the server to confirm the move. A successful move offers Undo for ten seconds. Undo checks the current location before moving anything back; a conflicting edit or occupied name can prevent it. Refresh after a network error to check whether the server committed the move before retrying.

What can move

Files and ordinary folders can move inside their existing Project and Episode. Folders carry their descendants. Project roots, Episodes, mounted resources, Bindrs and other specialized nodes cannot be dragged as file selections. A folder containing a Stack, a protected Episode, or a Note the caller cannot refile is rejected by the server. Resource-specific actions remain available on those resources' own surfaces.

Drop targets are folders, an existing Episode within the same Episode boundary, or the Project root. Files and resource mounts cannot be parents. A folder cannot move into itself or its descendants. Cross-project and cross-Episode moves are not supported. Project content-create permission is required.

Atomicity and large folders

A selection contains at most 200 files/folders. The server applies it in one transaction: any collision, stale source path or permission failure rolls back the entire selection. Existing names are never overwritten. Selecting a folder and one of its descendants together is rejected.

Folder descendants do not count toward the 200 selected-item limit. Moving a folder rewrites its descendants' path prefixes in bulk. Storage objects are not copied or deleted; node IDs, object keys and content bytes stay unchanged. Requests are synchronous with a bounded transaction. A timeout rolls back an uncommitted transaction; a lost response can leave the client uncertain about an already committed move.

API and Python

POST /nodes/move accepts:

json
{
  "parentId": "DESTINATION_NODE_ID",
  "nodes": [{ "id": "SOURCE_NODE_ID", "expectedPath": ",project,old-folder," }]
}

Read each source's path from GET /nodes/:id. The response contains nodes: [{id, name, path}] with confirmed locations. A stale path or name collision returns 409. Unsupported types, overlapping selections and invalid destinations return 400. Authorization and Episode protection are checked inside the transaction. The existing PATCH /nodes/:id {parentId} single-node API continues to support its established resource-specific rules.

python
from dreamlake.api._client import DreamLakeClient

client = DreamLakeClient()
client.move_file(file_node_id, destination_folder_id)
client.move_folder(folder_node_id, destination_folder_id)
client.move_nodes([first_node_id, second_node_id], destination_folder_id)

The SDK reads current source paths before submitting a selection. See the CLI move commands for terminal usage.