Knowledge and Collaboration: Warp Drive, teams, and the Admin Panel. # Team Admin Panel Canonical page: [/knowledge-and-collaboration/admin-panel/](https://docs.warp.dev/knowledge-and-collaboration/admin-panel/) > Centralized management for team administrators to configure workspace settings enforced across all team members. The Admin Panel gives team administrators centralized control over organization-wide Warp settings, including agent autonomy, privacy controls, billing limits, codebase indexing, and sharing policies. Settings configured in the Admin Panel are enforced across all team members and override individual preferences. ## What is the Admin Panel? [Section titled “What is the Admin Panel?”](#what-is-the-admin-panel) The [Admin Panel](https://app.warp.dev/admin/) provides team administrators with centralized control over organization-wide settings in Warp. It allows you to manage workspace settings that are enforced across all members of your team. **Key features:** * **AI Settings** - Control agent autonomy, permissions, and allowlists across your team * **Privacy Controls** - Configure data collection and enterprise secret redaction * **Billing Management** - Set spending limits and manage usage-based pricing * **Code Settings** - Control codebase indexing and context features * **Sharing Policies** - Manage link sharing and collaboration permissions ## Accessing the Admin Panel [Section titled “Accessing the Admin Panel”](#accessing-the-admin-panel) Team administrators can access the Admin Panel directly from the [Warp Admin Panel](https://app.warp.dev/admin/).  Admin Panel main interface. ## How settings enforcement works [Section titled “How settings enforcement works”](#how-settings-enforcement-works) The Admin Panel uses a tier-based policy system to determine which settings administrators can control: ### Toggleable vs. fixed settings [Section titled “Toggleable vs. fixed settings”](#toggleable-vs-fixed-settings) **Toggleable settings** can be modified by team administrators. These appear as dropdown menus with options like: * Enabled/Disabled for boolean settings * Specific autonomy levels for AI settings * Respect User Setting to allow individual control **Fixed settings** are determined by your billing tier and cannot be changed. These appear with a message: “Configuring this setting is not available on your plan.” ### Setting Inheritance [Section titled “Setting Inheritance”](#setting-inheritance) When administrators configure organization-wide settings: 1. **Organization enforced** - Setting applies to all team members regardless of individual preferences 2. **Respect user setting** - Allows individual team members to control the setting themselves 3. **Tier restricted** - Setting is locked to default values based on billing plan ### User Experience [Section titled “User Experience”](#user-experience) When organization settings override individual preferences: * Users see their personal settings grayed out * A message indicates “your organization has configured this setting” * Users cannot modify settings that are organizationally enforced ## Plan Limitations [Section titled “Plan Limitations”](#plan-limitations) The features available in the Admin Panel vary by billing tier: **Free Tier** * Most settings are fixed and non-toggleable * Limited Codebase Context and sharing features **Business Plans** * Most settings become toggleable by administrators * Enhanced AI autonomy control * Advanced sharing and privacy features **Enterprise Plans** * Full admin control over all settings * Enterprise secret redaction * Custom LLM integration * Advanced compliance features For complete details about what’s included in each plan, see [Warp pricing](https://www.warp.dev/pricing). ## Admin Panel sections [Section titled “Admin Panel sections”](#admin-panel-sections) The Admin Panel is organized into five main sections, each focused on a specific area of team management: ### AI Settings [Section titled “AI Settings”](#ai-settings) Configure how Agents behave across your organization, including autonomy levels and command permissions. #### General AI Settings [Section titled “General AI Settings”](#general-ai-settings) **AI in Remote Sessions** Controls whether AI features are available during SSH sessions and remote connections. Enterprise plans can toggle this setting, while Free tier teams have it enabled by default. **Prompt Summarization Caching** When conversations become long enough to require summarization, this setting allows the summary to be cached temporarily by the LLM provider to improve performance. #### Autonomy Settings [Section titled “Autonomy Settings”](#autonomy-settings) Configure how much independence Agents have when performing different actions: **Apply Code Diffs** * Agent Decides - Prompt for review before applying code diffs (currently behaves the same as Always Ask) * Always Ask - Require explicit approval before applying any code changes * Always Allow - Apply code diffs without confirmation * Respect User Setting - Allow individual users to control this setting **Create Plans** Controls whether Agents can create structured task plans without user approval. **Execute Commands** Manages Agent’s ability to run terminal commands autonomously. **Read Files** Controls Agent access to reading files in the codebase. #### Directory and Command Control [Section titled “Directory and Command Control”](#directory-and-command-control) **Directory Allowlist** Specify directories where Agents can read files without restriction. Use paths like `~/git/repo1` to grant access to specific project folders. **Command Allowlist** Regular expressions matching commands that Agent Mode can execute without asking permission. Common examples: * `grep .*` - Text search commands * `ls(\\s.*)?` - Directory listing * `which .*` - Finding executable locations **Command Denylist** Regular expressions for commands that always require explicit user approval, even if they would normally be allowed. Examples: * `rm -rf.*` - Recursive file deletion * `sudo.*` - Administrative commands * `curl.*` - Network requests Caution Command denylist rules take precedence over allowlist rules and agent autonomy settings. If a command matches the denylist, user permission will always be required. ### Privacy Settings [Section titled “Privacy Settings”](#privacy-settings) Manage data collection and security policies for your organization. **UGC Data Collection** Controls how Warp collects and uses user-generated content to improve the service: * Disabled - No UGC data collection * Enabled - Allow data collection for service improvement * Respect User Setting - Let individual users decide **Enterprise Secret Redaction** When enabled, applies regex patterns to prevent secrets from being sent to Warp servers or LLM providers. This feature is available on Enterprise plans and includes: * Automatic detection of common secret patterns * Custom regex patterns for organization-specific secrets * Unconditional application across all team members ### Code Settings [Section titled “Code Settings”](#code-settings) Control codebase indexing and AI code features for your team. **Codebase Context** Determines whether Warp indexes your team’s Git repositories to provide context for AI features: * Disabled - No codebase indexing * Enabled - Index codebases for improved AI responses * Respect User Setting - Allow individual control Higher tier plans support more indexed repositories and larger file limits per codebase. ### Billing Settings [Section titled “Billing Settings”](#billing-settings) Configure billing preferences and spending controls. **Usage Based Pricing** Enable pay-as-you-go billing for credits beyond your plan’s included quota. When enabled, you can set: **Monthly Spending Limit** Set a maximum monthly overage spending limit to control costs. The system displays current overage usage including: * Total overage credits used * Current month’s overage costs ### Sharing Settings [Section titled “Sharing Settings”](#sharing-settings) Control how team members can share Warp Drive objects and collaborate. **Direct Link Sharing** Allow team members to share Notebooks, Workflows, and other objects via direct links. **Anyone with Link Sharing** Enable public access to shared objects - anyone with the link can view the content without being a team member. # Session Sharing Canonical page: [/knowledge-and-collaboration/session-sharing/](https://docs.warp.dev/knowledge-and-collaboration/session-sharing/) > Share terminal sessions with teammates for collaboration, debugging, and knowledge sharing. Session sharing documentation has moved to the Agent Platform section. See the articles below for details on sharing sessions: * **[Agent Session Sharing](/agent-platform/local-agents/session-sharing/)** - Share agent sessions with your team for review and collaboration. * **[Viewing Cloud Agent Runs](/agent-platform/cloud-agents/viewing-cloud-agent-runs/)** - Share session context from cloud agent runs. # Team management Canonical page: [/knowledge-and-collaboration/teams/](https://docs.warp.dev/knowledge-and-collaboration/teams/) > Create or join a team to collaborate with others in Warp. A Warp team is a group of users who collaborate through a shared workspace in Warp Drive. Teams share Workflows, Notebooks, Prompts, Rules, and Environment Variables, with role-based permissions for admins and members. Each Warp user can belong to one team at a time. ## What is a team? [Section titled “What is a team?”](#what-is-a-team) A team is a group of Warp users who can collaborate on the command line together. Warp teams can share a dedicated workspace in Warp Drive. [Learn about pricing](https://www.warp.dev/pricing) and see our [Pricing FAQ](/support-and-community/plans-and-billing/pricing-faqs/).  ## Creating a team [Section titled “Creating a team”](#creating-a-team) You can create a new team in the following ways: * Warp Drive, + Create a team * **Settings** > **Teams** Before you can invite team members, you will need to give your team a meaningful name. We suggest using a name to represent your organization, company, or project.  If you create a team, you become the team’s admin and will be the only person who can delete the team. Reference [Team roles and permissions](/knowledge-and-collaboration/teams/#team-roles-and-permissions) for more info. ### Inviting new team members [Section titled “Inviting new team members”](#inviting-new-team-members) Under **Settings** > **Teams** you can copy the invite link for your Warp team and paste it to your clipboard. Caution If you’re on a paid plan, upgrading will automatically include all team members in your billing. Adding new members after upgrading will also add them as paid seats. For more details on how team member billing works, please see our [billing FAQs](/support-and-community/plans-and-billing/pricing-faqs/#what-counts-as-a-team-member-and-how-does-billing-work-for-members).  Teams settings panel. When you share this link with your teammates directly (we suggest using a secure channel like Slack or email), they will be able to join your team in Warp. ## Restricting team invites by domain [Section titled “Restricting team invites by domain”](#restricting-team-invites-by-domain) Sometimes you may want to control your team so that people can only join if they also authenticate with a specific email domain, such as your company’s email domain. Toggle on Restrict by domain to set an explicit allowlist. If you share an invite link with somebody who’s using Warp with a domain that does not match your allowlist, they will be prompted to authenticate from an emailed link sent to a matching domain to join your team. ## Joining a team [Section titled “Joining a team”](#joining-a-team) If you have received an invite link, you can use that link to sign up or log in and join your team in Warp. If your team is using domain restriction, you will need to authenticate you have access to a specific domain before you can join your team. ## Leaving and deleting teams [Section titled “Leaving and deleting teams”](#leaving-and-deleting-teams) If you’re a member of a team, you can visit **Settings** > **Teams** to leave a team at any time. Team admins (who created teams) may delete a team only after removing all team members. On Build, Max, and Business plans, [add-on credits](/support-and-community/plans-and-billing/add-on-credits/) are scoped to each individual user but **tied to the team** they were purchased under. Membership changes affect access: * **A user leaves a team** - You lose access to any add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin. * **An admin removes a member** - That member loses access to any add-on credits tied to the team. If they rejoin later, they regain access to any unused, non-expired credits. The admin pays a prorated rate for the seat when the user rejoins. * **An admin deletes the team** - Any remaining add-on credits tied to the team are no longer usable. Add-on credits require an active subscription. Downgrading to the Free plan forfeits access to add-on credits tied to your team. ## Team discoverability [Section titled “Team discoverability”](#team-discoverability) Team admins can make their teams discoverable to colleagues from the same email domain. This feature is available under **Settings** > **Teams** > **Make team discoverable**. ## Transferring team admin [Section titled “Transferring team admin”](#transferring-team-admin) Team admins can transfer their role to another team member by going to **Settings** > **Teams** > **Transfer admin** and selecting the member to whom you’d like to transfer the admin role. ## Team roles and permissions [Section titled “Team roles and permissions”](#team-roles-and-permissions) Caution If you’re a Team admin, and you choose to [delete your Warp](/support-and-community/privacy-and-security/privacy/#manage-your-data) account, the deletion flow will require that you assign a team member as the new admin. | Action | Admin | Member | | --------------------------------------------------------------------------------- | ---------------------------------------------------------- | ------------------------------------ | | Description | The Warp user who created the team. There can only be one. | Team members who belong to the team. | | Create a team | ✓ | | | Restrict by domain | ✓ | | | Invite members | ✓ | ✓ | | Remove team members | ✓ | | | Leave a team | | ✓ | | Delete a team | ✓ | | | Transfer admin | ✓ | | | [Manage billing](/support-and-community/plans-and-billing/plans-pricing-refunds/) | ✓ | | # Warp Drive overview Canonical page: [/knowledge-and-collaboration/warp-drive/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/) > Warp Drive is a workspace in your terminal where you can save Workflows, Notebooks, Prompts, and Environment Variables for personal use or to share with a team. Warp Drive is a built-in workspace for saving and sharing Workflows, Notebooks, Prompts, and Environment Variables across your team. All objects sync in real time, so you and your team always have access to the latest versions, whether you’re working locally or collaborating across an organization. ## What is Warp Drive? [Section titled “What is Warp Drive?”](#what-is-warp-drive) All objects stored in Warp Drive sync immediately as they’re updated, so you and your team will always have access to the latest versions.  ## How to access it [Section titled “How to access it”](#how-to-access-it) * macOS Warp Drive is accessible from the status bar in Warp, from the [Warp Drive web experience](/knowledge-and-collaboration/warp-drive/web/), or you can toggle the Warp Drive side panel with `CMD-\`. * Windows Warp Drive is accessible from the status bar in Warp, from the [Warp Drive web experience](/knowledge-and-collaboration/warp-drive/web/), or you can toggle the Warp Drive side panel with `CTRL-SHIFT-\`. * Linux Warp Drive is accessible from the status bar in Warp, from the [Warp Drive web experience](/knowledge-and-collaboration/warp-drive/web/), or you can toggle the Warp Drive side panel with `CTRL-SHIFT-\`.  The Warp Drive icon in the top-left corner. ## Workspaces in Warp Drive [Section titled “Workspaces in Warp Drive”](#workspaces-in-warp-drive) When you open the Warp Drive panel, you will find a personal workspace where you can store your Workflows, Notebooks, Prompts, and Environment Variables and organize them into folders.  If you are a member of a team using Warp Drive, your team’s workspace will also be available in the side panel.  ## Organizing objects in Warp Drive with your team [Section titled “Organizing objects in Warp Drive with your team”](#organizing-objects-in-warp-drive-with-your-team) * Objects (e.g. Workflows, Notebooks, Prompts, and Environment Variables) and folders in Warp Drive can be sorted alphabetically and by the last updated * Any objects moved from your personal workspace into a team’s workspace will be shared with all members of your team * It is not currently possible to move an item back from a team’s workspace into a personal workspace; if you shared something inadvertently, you should copy the contents of the object to your clipboard, recreate it in your personal workspace, and then delete the object from your team workspace * It is not currently possible to drag a folder of personal Workflows into a team workspace; you will need to move objects one at a time ## Using Warp Drive offline [Section titled “Using Warp Drive offline”](#using-warp-drive-offline) In offline mode, some files will be read-only. You can still create and edit files while offline in your personal space. They will only be saved locally and will not be synced. They cannot be moved into a team or deleted until you are back online.  Warp Drive operating in offline mode. ## Navigating Warp Drive with your keyboard [Section titled “Navigating Warp Drive with your keyboard”](#navigating-warp-drive-with-your-keyboard) To avoid going back and forth between your mouse and keyboard, you can use your keyboard to navigate through Warp Drive once you have either opened Warp Drive or switched focus to the Warp Drive panel. (You can also click on a blank area within Warp Drive.) The object you are navigating with your keyboard will be highlighted in an accented color. You can take these keyboard actions within Warp Drive: * macOS * Press `UP`/`DOWN` or `j`/`k` to navigate to the object you want. * Press `Enter` to 1) execute an object, 2) open/collapse a workspace or folder, or 3) open the trash. * Press `CMD-ENTER` to open an object’s context menu. * Press `CMD-SHIFT-(` and `CMD-SHIFT-)` to switch focus between the terminal and Warp Drive. * Press `LEFT-ARROW` to collapse a workspace or folder * Press `RIGHT-ARROW` to open a workspace or folder * Press `Esc` to return to Warp Drive from your trash. * Windows * Press `UP`/`DOWN` or `j`/`k` to navigate to the object you want. * Press `Enter` to 1) execute an object, 2) open/collapse a workspace or folder, or 3) open the trash. * Press `CTRL-ENTER` to open an object’s context menu. * Press `CTRL-SHIFT-(` and `CTRL-SHIFT-)` to switch focus between the terminal and Warp Drive. * Press `LEFT-ARROW` to collapse a workspace or folder * Press `RIGHT-ARROW` to open a workspace or folder * Press `Esc` to return to Warp Drive from your trash. * Linux * Press `UP`/`DOWN` or `j`/`k` to navigate to the object you want. * Press `Enter` to 1) execute an object, 2) open/collapse a workspace or folder, or 3) open the trash. * Press `CTRL-ENTER` to open an object’s context menu. * Press `CTRL-SHIFT-(` and `CTRL-SHIFT-)` to switch focus between the terminal and Warp Drive. * Press `LEFT-ARROW` to collapse a workspace or folder * Press `RIGHT-ARROW` to open a workspace or folder * Press `Esc` to return to Warp Drive from your trash.  Navigation states in the Warp Drive sidebar. To switch between panels using your keyboard, you can use the “Switch Focus to Left Panel” and “Switch Focus to Right Panel” commands in the [Command Palette](/terminal/command-palette/).  ## Import and Export [Section titled “Import and Export”](#import-and-export) Every object in Warp Drive can be exported to or imported from a file. When importing or exporting, objects are converted as follows: * [Workflows](/knowledge-and-collaboration/warp-drive/workflows/) import from and export to YAML (.yaml, .yml) * [Prompts](/knowledge-and-collaboration/warp-drive/prompts/) import isn’t supported at this time, but you can export to YAML (.yaml, .yml) * [Notebooks](/knowledge-and-collaboration/warp-drive/notebooks/) import from and export to MARKDOWN (.md) * [Environment Variables](/knowledge-and-collaboration/warp-drive/environment-variables/) import isn’t supported at this time, but you can export to DOTENV (.env) ### Importing files into Warp Drive [Section titled “Importing files into Warp Drive”](#importing-files-into-warp-drive) To import a local file or directory, `RIGHT-CLICK` on a folder or click **+** on a workspace and choose “Import.” If importing a directory, supported files in the directory and its sub-directories will be imported into a matching folder structure.  The import dialog for adding local files to Warp Drive. ### Exporting files from Warp Drive [Section titled “Exporting files from Warp Drive”](#exporting-files-from-warp-drive) To export a single Warp Drive object, `RIGHT-CLICK` on an object and choose “Export” from the menu, then select a directory for export. To export all Warp Drive objects, Open the [Command Palette](/terminal/command-palette/#how-to-access-it), search for and select “Export all Warp Drive objects”, then select a directory for export. ## Sharing your drive objects [Section titled “Sharing your drive objects”](#sharing-your-drive-objects) Every object in Warp Drive can be shared. There are three ways to share objects: * **Teams:** All members of a Warp team have full access to the objects in its Drive. * **Direct Sharing:** Objects can be shared directly with individuals by email. * **Link-based Sharing:** You can make an object public to anyone with the link, including those without Warp accounts. ### Sharing a drive object using links [Section titled “Sharing a drive object using links”](#sharing-a-drive-object-using-links) To share a Drive object, navigate to the object’s overflow menu, and choose “Copy link”. Once the link is successfully copied to your clipboard, you can share it with teammates and reference your object in your codebase, documentation, or communication channels like Slack.  The Copy link option in the right-click menu. ### Managing permissions [Section titled “Managing permissions”](#managing-permissions) To manage a Drive object’s permissions, navigate to its overflow menu and choose “Share”. If the object is open, you can also use the [Command Palette](/terminal/command-palette/#how-to-access-it) and search for “Share pane”, or click the share button in the pane header:  The share button in the pane header. This opens a dialog that lists the current sharing settings and allows you to change them:  Warp Drive sharing dialog. In this dialog, you can: * Invite other users directly using the email input at the top. * Change or remove the public link-based access level. * Update the access level for individual users, or remove their access. Permissions are inherited from parent folders. For example, if a folder was shared with edit permissions, then the user would also be able to edit all objects inside the folder or its subfolders. Owners and their teammates always have full access. When sharing an object, you can choose between view and edit access. | | Can view | Can edit | Full access | | ----------------------------------- | -------- | -------- | ----------- | | Read a notebook | ✓ | ✓ | ✓ | | Execute a Workflow | ✓ | ✓ | ✓ | | Use env vars | ✓ | ✓ | ✓ | | Edit contents | | ✓ | ✓ | | Create objects in a folder | | ✓ | ✓ | | Trash or untrash | | ✓ | ✓ | | Delete permanently | | | ✓ | | Modify permissions | | | ✓ | | Move to a different folder or drive | | | ✓ | ## Troubleshooting Warp Drive [Section titled “Troubleshooting Warp Drive”](#troubleshooting-warp-drive) * If you were previously using Warp on your own and were later invited to join a team, you may need to exit, update, and restart the Warp app to gain access to your team’s shared drive and commands * Navigating to Settings > Teams in Warp should also force a metadata update for you, which will ensure you have access to the latest versions of Workflows in your team’s drive # Agent Mode Context Canonical page: [/knowledge-and-collaboration/warp-drive/agent-mode-context/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/agent-mode-context/) > Agents use your Warp Drive content—Workflows, Notebooks, Rules, MCP Servers, and Environment Variables—for context-aware responses. Warp’s agents automatically pull context from your Warp Drive contents, including Workflows, Notebooks, Environment Variables, Rules, and MCP Servers, to generate responses tailored to your personal and team developer workflows. Referenced objects appear as citations in the conversation. ## Objects used as context [Section titled “Objects used as context”](#objects-used-as-context) Agents can automatically pull in relevant context from: * **Workflows** - Saved commands and scripts * **Notebooks** - Documentation and notes * **Environment Variables** - Configuration values * **Rules** - Guidelines that shape agent behavior (see [Rules](/agent-platform/capabilities/rules/)) * **MCP Servers** - External tools and data sources (see [MCP](/agent-platform/capabilities/mcp/)) When a Warp Drive object is pulled as context, it will be displayed in the conversation as a citation under “References” or “Derived from”. ## Settings [Section titled “Settings”](#settings) Enabled by default, this can be toggled in **Settings** > **Agents** > **Knowledge** > **Warp Drive as Agent Mode Context**. ## Related [Section titled “Related”](#related) * [AI-Integrated Objects](/knowledge-and-collaboration/warp-drive/ai-objects/) - Overview of all AI-related objects in Warp Drive # AI-Integrated Objects Canonical page: [/knowledge-and-collaboration/warp-drive/ai-objects/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/ai-objects/) > Access Rules, MCP Servers, Skills, and Prompts in Warp Drive to give agents personalized context. Warp Drive includes several object types that integrate with Warp’s agents to provide personalized, context-aware assistance. These objects help agents understand your coding standards, connect to external tools, and follow your preferred workflows. ## Rules [Section titled “Rules”](#rules) Rules are reusable guidelines that inform how agents respond to your prompts. They help tailor responses to match your coding standards, project conventions, and personal preferences. **Access from Warp Drive:** **Personal** > **Rules** Warp supports two types of rules: * **Global Rules** - Apply across all projects and contexts * **Project Rules** - Live in your codebase (as `AGENTS.md` or `WARP.md` files) and apply automatically when working within that project ## MCP Servers [Section titled “MCP Servers”](#mcp-servers) MCP (Model Context Protocol) servers extend Warp’s agents with custom tools and data sources through a standardized interface. They act as plugins that let agents access external services like GitHub, Sentry, Linear, Slack, and more. **Access from Warp Drive:** **Personal** > **MCP Servers** MCP servers can be: * **CLI-based** - Local commands that Warp launches and manages * **URL-based** - Remote endpoints using Streamable HTTP or SSE ## Skills [Section titled “Skills”](#skills) Skills are reusable instruction sets that teach agents how to perform specific tasks. Unlike Rules (which provide guidelines), Skills define complete workflows that agents can invoke when relevant. Skills are file-based (stored as `SKILL.md` files in your project or home directory) rather than cloud-synced objects, but they integrate closely with Warp Drive workflows. * **Project Skills** - Live in `.agents/skills/`, `.warp/skills/`, or similar directories in your repository * **Global Skills** - Live in `~/.agents/skills/` or similar directories in your home folder ## Prompts [Section titled “Prompts”](#prompts) Prompts are parameterized natural language queries you can save and reuse with Agent Mode. They allow you to save complex AI workflows and execute them quickly from the Command Palette. **Access from Warp Drive:** Click **+** and select “Prompt”, or browse existing prompts in your personal or team workspace. ## How agents use these objects [Section titled “How agents use these objects”](#how-agents-use-these-objects) When you start an agent conversation, Warp automatically provides relevant context from your Warp Drive objects: * **Rules** guide agent behavior and responses based on your preferences * **MCP Servers** give agents access to external tools and data sources * **Skills** provide task-specific instructions agents can invoke * **Prompts** let you trigger predefined workflows quickly When an object is used as context, it appears in the conversation under “References” or “Derived from.” ## Related [Section titled “Related”](#related) * [Rules](/agent-platform/capabilities/rules/) - Create guidelines for agent behavior * [MCP Servers](/agent-platform/capabilities/mcp/) - Connect external tools and data sources * [Skills](/agent-platform/capabilities/skills/) - Define reusable task workflows * [Prompts](/knowledge-and-collaboration/warp-drive/prompts/) - Save and reuse parameterized agent prompts * [Agent Profiles & Permissions](/agent-platform/capabilities/agent-profiles-permissions/) - Control agent autonomy and tool access # Environment variables Canonical page: [/knowledge-and-collaboration/warp-drive/environment-variables/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/environment-variables/) > Save or sync environment variables to load into your terminal sessions. Environment Variables in Warp Drive let you save, sync, and load environment variables into your terminal sessions with a click. Support for both static values and dynamic secrets from external managers like 1Password, LastPass, and Hashicorp Vault keeps credentials secure and out of source code. ## What are environment variables in Warp? [Section titled “What are environment variables in Warp?”](#what-are-environment-variables-in-warp) Environment variables in Warp are similar to .env files, except you can: * Load them into your terminal session with a click. * Use them in parameterized workflows. * Dynamically reference secrets from external managers. ## How to create and edit environment variables [Section titled “How to create and edit environment variables”](#how-to-create-and-edit-environment-variables) You can create new environment variables through: * [Warp Drive](/knowledge-and-collaboration/warp-drive/), + → Environment variable * [Command Palette](/terminal/command-palette/), create new team or personal environment variables Any of these entry points will open the environment variables editor where you can name and describe your environment variables.  ## Managing individual environment variables [Section titled “Managing individual environment variables”](#managing-individual-environment-variables) Warp supports two types of environment variables: static variables and dynamic variables. ### Static variables [Section titled “Static variables”](#static-variables) Static variables are similar to .env files. You create the variables by entering raw strings of text. Each variable has a variable name and a corresponding value.  After you save the environment variable, you can click it to load it into your terminal session.  When you use static variables, Warp stores them securely in Warp Drive.\ \ Note: Static variables should not be used to replace a secret manager. Please use dynamic variables for any sensitive information. ### Dynamic variables [Section titled “Dynamic variables”](#dynamic-variables) Dynamic variables let you reference secrets that are stored securely outside of Warp in external secret managers, such as 1Password or LastPass. You can use custom commands to create dynamic variables for any system with a public API or CLI, such as AWS or Hashicorp Vault. ### **How to create and edit dynamic environment variables** [Section titled “How to create and edit dynamic environment variables”](#how-to-create-and-edit-dynamic-environment-variables) To create a new dynamic variable: 1. Open the environment variable editor. 2. Use the key icon to reveal the dynamic variable menu. 3. Select an integrated password manager or “Command” to write your own custom integration.  #### **Integrated password managers** [Section titled “Integrated password managers”](#integrated-password-managers) Before you get started, please ensure you have the CLI installed for your tool of choice and follow the instructions to enable the CLI: * [1Password CLI](https://developer.1password.com/docs/cli/get-started/) * [LastPass CLI](https://github.com/lastpass/lastpass-cli) Then, you can click the key icon and select your manager from the dropdown menu.  The CLI will require you to authenticate and then provide you with a list of available secrets.  ### **How to write a custom secret command** [Section titled “How to write a custom secret command”](#how-to-write-a-custom-secret-command) Reference the documentation for your external secret manager. Then, write a custom command to retrieve secrets. For example, you can write a command using the [Hashicorp Vault CLI](https://developer.hashicorp.com/vault/docs/commands) to retrieve and load the password field for the staging server. When using secret commands, Warp stores the command but never the actual secrets. The secrets are referenced and loaded into a terminal session at runtime. ```plaintext // vault kv get -field=password secret/staging/app/server/creds ```  ### Using environment variables [Section titled “Using environment variables”](#using-environment-variables) There are three ways to invoke your environment variables and load them into a terminal session: 1. [Click to load into a current section](/knowledge-and-collaboration/warp-drive/environment-variables/#click-to-load-into-a-current-session) 2. [Click to load into a subshell](/knowledge-and-collaboration/warp-drive/environment-variables/#click-to-load-into-a-subshell) 3. [Select to load in with a workflow](/knowledge-and-collaboration/warp-drive/environment-variables/#select-to-load-with-a-workflow) #### Click to load into a current session [Section titled “Click to load into a current session”](#click-to-load-into-a-current-session) First, click your environment variable from Warp Drive or the Command Palette. Then, review the confirmation block. If your environment variables are correct, hit enter to load them into your session.   These environment variables will now be present for the remainder of your session. #### Click to load into a subshell [Section titled “Click to load into a subshell”](#click-to-load-into-a-subshell) To load environment variables into a subshell, you will need to open [Warp Drive](/knowledge-and-collaboration/warp-drive/) and locate your environment variable in the Warp Drive index. You can then use the overflow menu to select “Load in subshell.” Loading an environment into a subshell reduces the risk of your environment variables accidentally contaminating your workspace. The subshell is clearly defined and once you exit it, any environment variables set by Warp Environment Variables will be cleared, unless they are already present in the parent session.   #### Select to load with a workflow [Section titled “Select to load with a workflow”](#select-to-load-with-a-workflow) Any time you run a workflow, you can select from existing environment variables. This allows you to dynamically inject environment variables into a parameterized workflow so you can use a single workflow command in multiple environments, such as production and staging. For example, you may have a workflow to create a new team that uses the environment variable $SERVER\_URL. By using the environment variables dropdown in the workflow card, you can dynamically inject the necessary variables. This ensures the workflow references the appropriate values so the command runs with the relevant environment-specific information. These environment variables will now be present for the remainder of your session until you clear them or overwrite them with a different environment.  ### Import and export environment variables in Warp Drive [Section titled “Import and export environment variables in Warp Drive”](#import-and-export-environment-variables-in-warp-drive) Please see our [Warp Drive Import and Export](/knowledge-and-collaboration/warp-drive/#import-and-export) instructions. # Warp Drive Notebooks Canonical page: [/knowledge-and-collaboration/warp-drive/notebooks/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/notebooks/) > Save interactive playbooks to simplify onboarding and development. Notebooks are interactive, runnable documents in Warp Drive that combine markdown text with executable shell command blocks. Use them for onboarding playbooks, debugging runbooks, and development workflows that teammates can search, share, and execute directly from the terminal. ### What is a Notebook? [Section titled “What is a Notebook?”](#what-is-a-notebook) Notebooks are runnable documentation consisting of markdown text and list elements, code blocks, and runnable shell snippets that can be automatically executed in your terminal session. Notebooks are searchable and accessible through the [Command Palette](/terminal/command-palette/) so you can access and run your documentation without ever leaving the terminal. You can also export Notebooks in .md format at any time. ### How to save and edit notebooks [Section titled “How to save and edit notebooks”](#how-to-save-and-edit-notebooks) You can create a new notebook from various entry points in Warp * macOS * From Warp Drive, + > New notebook * From the [Command Palette](/terminal/command-palette/), create a new team or personal notebook. * Windows * From Warp Drive, + > New notebook * From the [Command Palette](/terminal/command-palette/), create a new team or personal notebook. * Linux * From Warp Drive, + > New notebook * From the [Command Palette](/terminal/command-palette/), create a new team or personal notebook. Any of these entry points will open the notebook editor where you can: * Title your notebook. * Start adding text and code elements.  Editing a Notebook. ### Working with Notebooks [Section titled “Working with Notebooks”](#working-with-notebooks) #### Adding new elements [Section titled “Adding new elements”](#adding-new-elements) Notebook elements (text, code, list items) can be added in several ways: * Using the appropriate markdown shortcut (e.g. ### for Heading 3). * Typing /, which will open up a selection menu of supported elements. * Pressing the + icon which appears when hovering over a line and selecting from the menu of supported elements.  Available Markdown element types in the Notebook editor. #### Styling existing elements [Section titled “Styling existing elements”](#styling-existing-elements) Existing notebook elements can be styled in several ways: * Selecting an existing element and selecting text decorations (like bold, italics, or inline code) from the hover menu. * Using markdown syntax for text stylings like \*\*bold\*\* or \*italic\*. * Selecting an existing element and changing the overall type of the element via the dropdown element menu.  #### Using Command and Code Blocks [Section titled “Using Command and Code Blocks”](#using-command-and-code-blocks) Command and code blocks have several unique properties such as syntax highlighting and quick actions that make working with code-based documentation simple. You can create a code or command block by either: * Selecting Command or Code from the new element menu * Typing ` ``` ` (triple backticks) Once you’ve inserted your code block you can select the language at the bottom of the block from numerous options which will apply the appropriate syntax highlighting if available (or default to Code if your language is not found). All code and command blocks will apply syntax highlighting and provide a quick copy button for easy access.  A code block with syntax highlighting in a Notebook. #### Special properties of command blocks [Section titled “Special properties of command blocks”](#special-properties-of-command-blocks) If you insert a Command block or specify the language as “Shell”, Warp provides extra functionality to simplify terminal work. #### Executing Command Blocks [Section titled “Executing Command Blocks”](#executing-command-blocks) Developers can execute shell command blocks by: * macOS * Using the insert button at the bottom of the block * Pressing `CMD-ENTER` while the block is selected (a blue highlight will appear) * Windows * Using the insert button at the bottom of the block * Pressing `CTRL-ENTER` while the block is selected (a blue highlight will appear) * Linux * Using the insert button at the bottom of the block * Pressing `CTRL-ENTER` while the block is selected (a blue highlight will appear) The command text will be inserted into the developer’s active terminal session, or a new session if none are active.  The run button on a command block in a Notebook. #### Adding arguments to Command Blocks [Section titled “Adding arguments to Command Blocks”](#adding-arguments-to-command-blocks) Command blocks accept parameters in the same format as [Workflows](/knowledge-and-collaboration/warp-drive/workflows/). To add an argument to your command block, use `{{double_curly_brackets}}` to specify your argument term.  A command block with editable parameters. #### Navigating command blocks with the keyboard [Section titled “Navigating command blocks with the keyboard”](#navigating-command-blocks-with-the-keyboard) Command Blocks also support keyboard navigation. There are two ways to enter the keyboard navigation mode: * macOS * Clicking on a shell block. * Pressing `CMD-UP` or `CMD-DOWN.` Once a command block is selected, press `CMD-ENTER` to insert it into the terminal input. You can also use `UP, DOWN, CMD-UP`, and `CMD-DOWN` to navigate between command blocks. While the Notebook is focused, press `CMD-L` to switch focus back to the terminal without inserting a command. * Windows * Clicking on a shell block. * Pressing `CTRL-UP` or `CTRL-DOWN.` Once a command block is selected, press `CTRL-ENTER` to insert it into the terminal input. You can also use `UP, DOWN, CTRL-UP,` and `CTRL-DOWN` to navigate between command blocks. While the Notebook is focused, press `CTRL-L` to switch focus back to the terminal without inserting a command. * Linux * Clicking on a shell block. * Pressing `CTRL-UP` or `CTRL-DOWN.` Once a command block is selected, press `CTRL-ENTER` to insert it into the terminal input. You can also use `UP, DOWN, CTRL-UP,` and `CTRL-DOWN` to navigate between command blocks. While the Notebook is focused, press `CTRL-L` to switch focus back to the terminal without inserting a command. #### Adding existing Workflows to notebooks [Section titled “Adding existing Workflows to notebooks”](#adding-existing-workflows-to-notebooks) If you have existing [Workflows](/knowledge-and-collaboration/warp-drive/workflows/) that you’d like to insert into your notebook rather than duplicating their content, you can select Embedded Workflow from the new element menu and select from the available Workflows. Once embedded in a notebook, the workflow will be executable like a regular command block. To edit the content of the embedded workflow, you will need to edit the source workflow which can be found by searching for the title in the [Command Palette](/terminal/command-palette/).  Embedding an existing workflow in a notebook. ### Working with Notebooks in a team [Section titled “Working with Notebooks in a team”](#working-with-notebooks-in-a-team) If the notebook is shared with a team, all team members will have access to edit the notebook and updates will sync immediately for all members of the team.  A Notebook displayed in view mode. ### Import and export notebooks in Warp Drive [Section titled “Import and export notebooks in Warp Drive”](#import-and-export-notebooks-in-warp-drive) Please see our [Warp Drive Import and Export](/knowledge-and-collaboration/warp-drive/#import-and-export) instructions. # Warp Drive prompts Canonical page: [/knowledge-and-collaboration/warp-drive/prompts/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/prompts/) > Save and reuse parameterized Agent Mode prompts to run on-demand. Prompts are parameterized natural language queries you can save in Warp Drive and reuse with agents. Name a prompt, add arguments for dynamic values, and execute it from the Command Palette or Warp Drive to repeat complex agent workflows without retyping. ## What is a prompt? [Section titled “What is a prompt?”](#what-is-a-prompt) A prompt is a parameterized natural language query you can name and save in Warp to use with [Agent Mode](/agent-platform/local-agents/interacting-with-agents/). Prompts are searchable and easily accessed from the [Command Palette](/terminal/command-palette/) so you can find and execute them without switching context. They allow you to save and reuse specific and complex AI workflows, making it easier to repeat multi-step tasks with Agent Mode.  Command view of a Prompt in Warp Drive. ### Demo: Trigger reusable actions with saved prompts [Section titled “Demo: Trigger reusable actions with saved prompts”](#demo-trigger-reusable-actions-with-saved-prompts) Here’s an example from [Warp Guides](/guides/), where Zach walks through what prompts he uses for PRs and Git commits:  There are other great examples of prompts on [Do Things](https://dothings.warp.dev/) and [Warp Guides](/guides/). ## How to save and edit prompts [Section titled “How to save and edit prompts”](#how-to-save-and-edit-prompts) You can create a new prompt from Warp Drive by clicking the + button and selecting “Prompt”. * Name your prompt * Edit the natural language query along with any arguments (also known as parameters) * Add a meaningful description that will be indexed for search (optional) * Add arguments, descriptions for arguments, and default values (optional)  Edit view of a Prompt in Warp Drive. Once a prompt has been created, you can edit it at any time, as long as you have access to an internet connection. ### Working with arguments [Section titled “Working with arguments”](#working-with-arguments) In the prompt editor, you can add arguments manually with “New argument” or by typing in double curly braces (`{{argument}}`) within the command field. If you select “New argument” while you have text selected, Warp will wrap that text in curly braces to create an argument. There are some rules for creating valid arguments: * Argument names can only include characters `A-Za-z0-9`, hyphens `-` and underscores `_` * The first character of an argument cannot be a number Arguments can be one of two types: text or enum. By default, all new arguments are text type. #### Enum type arguments [Section titled “Enum type arguments”](#enum-type-arguments) Enums allow you to specify expected inputs to a prompt argument. When you insert a prompt with enums into the input editor, you will be prompted with suggestions for filling in the argument. You can open the suggestions menu by pressing `SHIFT-TAB` while selecting an argument. For detailed information about creating and using enum type arguments, please see the [Enum type arguments section in Workflows documentation](/knowledge-and-collaboration/warp-drive/workflows/#enum-type-arguments). ### Editing prompts with a team [Section titled “Editing prompts with a team”](#editing-prompts-with-a-team) If the prompt is shared with a team, all team members will have access to edit it and updates will sync immediately for all members of the team. If a prompt in the Warp Drive has been edited by another team member or a user on another device while you are attempting to edit the same prompt, you will not be able to save changes; you will need to check out the latest version and try again. ## How to execute prompts [Section titled “How to execute prompts”](#how-to-execute-prompts) You can execute a prompt in several ways: * From Warp Drive, click the prompt * From the [Command Palette](/terminal/command-palette/) or [Command Search](/terminal/entry/command-search/), search for a prompt by name or type “prompts:” to see all available prompts and your prompt history * When a prompt is selected, you can use `SHIFT-TAB` to cycle through the arguments.  Searching for Prompts in the Command Palette.  Searching for Prompts in Command Search. These options will paste the prompt into your active terminal input. Prompt names and any relevant descriptions and arguments will be displayed in a dialog, so you can understand how to use the prompt. You can make any adjustments you need to the arguments before running the prompt in your input editor. ### Import and export prompts in Warp Drive [Section titled “Import and export prompts in Warp Drive”](#import-and-export-prompts-in-warp-drive) Please see our [Warp Drive Import and Export](/knowledge-and-collaboration/warp-drive/#import-and-export) instructions. # Warp Drive on the web Canonical page: [/knowledge-and-collaboration/warp-drive/web/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/web/) > Access your Warp Drive objects and shared sessions from any browser or touch screen device, including mobile phones, tablets, and touch-enabled laptops. Warp Drive on the Web lets you view and edit Warp Drive objects and shared sessions directly in any browser, including mobile devices and tablets. Access Workflows, Notebooks, Prompts, and session transcripts from anywhere without installing the Warp desktop app. ## What is Warp on the web? [Section titled “What is Warp on the web?”](#what-is-warp-on-the-web) Warp Drive on the Web lets you view and edit your Warp Drive objects and shared sessions directly in the browser, on any device.  A web-based rendering of a Team Workflow. ## How to access Warp on the web [Section titled “How to access Warp on the web”](#how-to-access-warp-on-the-web) Warp’s web-based viewing experience can currently be accessed via: * The [`app.warp.dev/app` homepage](https://app.warp.dev/app) * [Drive Object](/knowledge-and-collaboration/warp-drive/#sharing-your-drive-objects) Links * [Session Sharing](/knowledge-and-collaboration/session-sharing/#how-to-allow-access-to-collaborators-in-your-session) Links Caution You can edit and view web-based objects and sessions as normal. The one exception is executing a command from a workflow or notebook since there is no shell session running on the web. ## Managing your view preferences - web or desktop [Section titled “Managing your view preferences - web or desktop”](#managing-your-view-preferences---web-or-desktop) If the Warp app is installed, links will open on the desktop by default. You can manage whether Warp links open in Warp’s desktop app or the browser in multiple ways: 1. The first time you follow a link, if Warp is not installed, you will be prompted to download it. You can dismiss the popup to stay on the web.  2. This preference can be changed at any point in **Settings** > **Features** > **General** > **Open links in desktop app** Note that this setting is only available while on the web-based version of Warp.  Setting managing how to open links. 3. You can always switch between web and desktop views on a case-by-case basis. 1. To switch from a web-view to Desktop for a given object, open the *overflow menu > Open link on Desktop.*  2. To stay on the web for a given object despite a global Desktop preference, follow the *View on the web* option that is part of the redirect screen to Desktop.  ## Supported Browsers [Section titled “Supported Browsers”](#supported-browsers) Warp on the web supports all modern browsers, including: **Desktop** * Chrome * Firefox * Safari **Mobile** * iOS Safari 15+ * Android Chrome 58+ * Samsung Internet 7.2+ ## Touch screen and mobile support [Section titled “Touch screen and mobile support”](#touch-screen-and-mobile-support) Warp supports all touch screen devices, including mobile phones, tablets, and touch-enabled laptops. Touch input works on both the web and the desktop app. ### Supported gestures [Section titled “Supported gestures”](#supported-gestures) * **Touch and scroll** - Vertical and horizontal scrolling work as expected * **Double tap** - Select text or elements * **Long press (hold)** - Open context menu (equivalent to right-click) ## Related features [Section titled “Related features”](#related-features) * [Warp Drive](/knowledge-and-collaboration/warp-drive/) - Store and share workflows, prompts, and environment variables * [Session Sharing](/knowledge-and-collaboration/session-sharing/) - Collaborate with others in real-time terminal sessions # Warp Drive Workflows Canonical page: [/knowledge-and-collaboration/warp-drive/workflows/](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/workflows/) > Save parameterized commands as Workflows and execute them on-demand from Warp Drive. Workflows are parameterized commands you can name, save, and share in Warp Drive. Define arguments with default values, add descriptions for search, and execute workflows from the Command Palette or Warp Drive to run frequently used commands without retyping them. ## What is a workflow? [Section titled “What is a workflow?”](#what-is-a-workflow) A workflow is a parameterized command you can name and save in Warp with descriptions and arguments. Workflows are searchable and easily accessed from the [Command Palette](/terminal/command-palette/) so you can find and execute them without switching contexts. ## How to save and edit workflows [Section titled “How to save and edit workflows”](#how-to-save-and-edit-workflows) You can create a new workflow from various entry points in Warp: * From Warp Drive, + > New workflow * Using Block Actions, Save as Workflow * From agent results, Save as Workflow * From the [Command Palette](/terminal/command-palette/), Create a New Personal Workflow Any of these entry points will open the workflow editor where you can: * Name your workflow * Edit the command along with any arguments (also known as parameters) * Add a meaningful description that will be indexed for search (optional) * Add arguments, descriptions for arguments, and default values (optional)  Workflows save / edit pane.  ### Working with arguments [Section titled “Working with arguments”](#working-with-arguments) In the workflow editor, you can add arguments manually with “New argument” or by typing in double curly braces (`{{argument}}`) within the command field. If you select “New argument” while you have text selected, Warp will wrap that text in curly braces to create an argument. There are some rules for creating valid arguments: * Argument names can only include characters `A-Za-z0-9`, hyphens `-` and underscores `_` * The first character of an argument cannot be a number Arguments can be one of two types: text or enum. By default, all new arguments are text type. #### Enum type arguments [Section titled “Enum type arguments”](#enum-type-arguments) Enums allow you to specify expected inputs to a workflow argument. When you insert a workflow with enums into the input editor, you will be prompted with suggestions for filling in the argument. You can open the suggestions menu by pressing `SHIFT-TAB` while selecting an argument. [Enum Input Suggestions Demo](https://www.loom.com/embed/b2f54eeef2f247a8bbcf87698b2a4287) To create an enum type argument: 1. Navigate to the “default value” field of an argument. 2. Select the “Enum” type. 3. Click “New” to create a new enum, or select an existing one from the dropdown menu. 4. If you selected “New”, you can choose to create a “Static” enum or “Dynamic” enum. Dynamic enums are associated with a shell command whose output is parsed to determine the set of valid values for that argument. [Enum Creation Demo](https://www.loom.com/embed/b429ab7f7014418e9591e505fd71af83) ### Working with aliases [Section titled “Working with aliases”](#working-with-aliases) Workflow aliases allow you to create personalized shortcuts and custom configurations for your frequently used workflows. These aliases provide enhanced flexibility in how you use and configure workflows. Aliases are personal to your account, not shared with everyone who has the workflow. If settings sync is enabled, they’ll be synced across devices logged in to your account. Aliases can set default values for each [argument](/knowledge-and-collaboration/warp-drive/workflows/#working-with-arguments), but don’t have to. Aliases can have [Environmental Variables](/knowledge-and-collaboration/warp-drive/environment-variables/) associated with them. ### Editing workflows [Section titled “Editing workflows”](#editing-workflows) Once a workflow has been created, you can edit it at any time, as long as you have access to an internet connection.  The edit menu for a Workflow in Warp Drive. #### AI Autofill [Section titled “AI Autofill”](#ai-autofill) Workflows also have the option to use an [agent](/agent-platform/local-agents/overview/) to automatically generate a title, descriptions, or parameters. * Create or edit a Workflow, in the edit view you should see the option to AutoFill. * Warp will fill in the fields based on the Workflow you’re creating. [](/assets/terminal/Edit-workflows-autofill.mp4) ### Editing workflows with a team [Section titled “Editing workflows with a team”](#editing-workflows-with-a-team) If the workflow is shared with a team, all team members will have access to edit the workflow and updates will sync immediately for all members of the team. If a workflow in the Warp Drive has been edited by another team member or a user on another device while you are attempting to edit the same workflow, you will not be able to save changes; you will need to check out the latest version and try again. ## How to execute workflows [Section titled “How to execute workflows”](#how-to-execute-workflows) You can execute a workflow in several ways: * From Warp Drive, click the workflow * From the [Command Palette](/terminal/command-palette/), search for a workflow you’d like to execute, click or select, and enter * From [Command Search](/terminal/entry/command-search/), search for a workflow you’d like to execute, click or select, and enter. * When a workflow is selected, you can use `SHIFT-TAB` to cycle through the arguments.  Searching for Workflows in the Command Palette. These options will paste the workflow into your active terminal input. Workflow names and any relevant descriptions and arguments will be displayed in a dialog, so you can understand how to use the workflow.  Executing a Workflow from Warp Drive. You make any adjustments you need to the arguments (or the command itself) before running the command in your input editor.  ## Support for YAML Workflows [Section titled “Support for YAML Workflows”](#support-for-yaml-workflows) Warp will indefinitely support the [YAML Workflows](/terminal/entry/yaml-workflows/), which includes personal and community workflows sourced from an open-source repository. If needed, you can continue to access your `.yaml` file workflows using [Command Search](/terminal/entry/command-search/) or the [Command Palette](/terminal/command-palette/). However, these file-based workflows will not be available to access, organize, or share in Warp Drive. ### Import and export workflows in Warp Drive [Section titled “Import and export workflows in Warp Drive”](#import-and-export-workflows-in-warp-drive) Please see our [Warp Drive Import and Export](/knowledge-and-collaboration/warp-drive/#import-and-export) instructions.