Skip to content

Support Shift-click bulk selection and bulk delete in Warp Drive #10244

@Jordan-Murray

Description

@Jordan-Murray

Pre-submit Checks

  • I have searched Warp feature requests and there are no exact duplicates
  • I have searched Warp docs and my feature is not there

Describe the solution you'd like?

I would like Warp Drive to support multi-select for saved objects, especially AI-generated Plans, so users can clean up several items at once.

The core interaction I am looking for is familiar file-list behavior:

  • Shift-click a row to select a contiguous visible range.
  • Cmd-click on macOS, or Ctrl-click on Linux/Windows, to toggle individual rows in or out of the selection.
  • Show a compact bulk action surface when multiple objects are selected.
  • In the main Warp Drive index, allow the selected objects to be moved to Trash.
  • In Trash, allow selected objects to be restored or deleted forever.

This should apply to selectable Warp Drive objects such as Plans/notebooks, workflows, folders, and environment-variable collections. It should not select section headers, banners, the workspace picker, or special collection rows.

For delete behavior, I would expect bulk actions to follow the same constraints as the existing single-object actions:

  • Respect online/offline state.
  • Respect shared-object permissions.
  • Respect pending sync / online-only operation constraints.
  • Avoid partial application if one selected object is not eligible.
  • Require confirmation for bulk "Delete forever" in Trash.

Is your feature request related to a problem? Please describe.

Yes. Agent-created Plans can accumulate quickly while iterating on tasks. Today, deleting or cleaning them up requires opening each row's menu and deleting one item at a time. That makes ordinary cleanup slow and fiddly, especially after several planning/replanning loops.

The same problem applies to other Warp Drive objects too, but Plans are the place I hit it most often because they can be temporary artifacts rather than long-lived documents.

Additional context

Adjacent issues I found, but they do not appear to cover this exact request:

I would be happy to contribute a spec PR for this if maintainers think the behavior fits Warp Drive.

Operating system (OS)

Windows

How important is this feature to you?

4 (Very important)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:warp-driveWarp Drive objects, sync, sharing, cloud object management, and persisted artifacts.enhancementNew feature or request.needs-mocksrepro:highThe report includes enough evidence that the issue appears highly reproducible.triagedIssue has received an initial automated triage pass.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions