Skip to main content
Warp Drive is the cloud synchronization layer built into Warp. It stores your terminal objects — workflows, notebooks, environment variable collections, MCP servers, AI facts, and shared sessions — and automatically syncs them across every device you’re signed into and every teammate on your plan. Instead of manually exporting and importing scripts, Drive turns your team’s accumulated shell knowledge into a shared, always-current library that’s available the moment you open Warp.

The Drive panel

The Drive panel is a collapsible sidebar inside Warp that gives you a tree-style view of all your Drive objects. You can open it from the left rail or via the keyboard. From the panel you can:
  • Browse and search personal and team objects
  • Create new workflows, notebooks, and folders
  • Drag objects into folders to organize your library
  • Open the sharing dialog for any object
  • Import objects from a file or export them for distribution
The Drive panel is powered by the DriveIndex view internally. The sidebar (DrivePanel) is responsible for interactions with the rest of the workspace, while DriveIndex handles the internal Drive tree and filtering.

Personal vs. team objects

Every Drive object belongs to an owner, which is either you personally or a team you are a member of.

Personal objects

Visible only to you. Sync across all devices where you are signed in with the same account. Good for your own snippets and work-in-progress notebooks.

Team objects

Visible to every member of your team plan. Any team member can view, run, or fork a team workflow without you having to send them a file.

Object types

Drive stores several distinct object types, each represented by its own icon in the panel.

Workflows

Reusable shell commands with named parameters. Workflows can be run directly from Drive, triggered by aliases, or surfaced by the AI agent.

Agent Mode Workflows

Prompt templates for the Warp AI agent. These extend the agent with custom instructions that can be invoked by name.

Notebooks

Rich markdown documents that live alongside your terminal. Notebooks can contain code blocks, prose, and AI-generated plans (AI Documents).

AI Facts

Persistent knowledge snippets that the AI agent draws on when generating responses. Store project conventions, codebase notes, and domain knowledge.

Env Var Collections

Named sets of environment variables that you can inject into a shell session in one click, including in sub-shells.

MCP Servers

Model Context Protocol server configurations that the AI agent can call as tools. Stored and synced through Drive so the whole team shares access.

How sync works

When you create or edit a Drive object, Warp serializes it and syncs it to the Warp cloud. Changes propagate to your other devices and to teammates within seconds. Warp uses a SyncId per object to track versions, and the local SQLite database (via Diesel ORM) acts as the persistent cache so Drive objects are available even when you are offline.
Objects created locally while offline are queued and uploaded automatically when your connection is restored — you do not need to manually trigger a sync.

Folders

You can organize Drive objects into folders, including nested folders. Folders themselves are Drive objects and sync like any other item. The trash is a special folder; use Empty Trash from the Drive panel menu to permanently delete trashed objects.

Settings

Drive-specific preferences — such as default sort order and panel width — are stored in user preferences and persist across sessions. The minimum panel width is 250 px and the maximum is 75 % of the window width.

Build docs developers (and LLMs) love