Sharing individual blocks
Every command block in Warp can be turned into a shareable permalink. Select the block and choose Share block from its toolbar to generate a link. Recipients can view the block’s output in a browser without installing Warp.Block permalinks are public links — anyone with the URL can view the output.
Do not share blocks that contain secrets or private data.
SharedBlockTitleGeneration feature flag is enabled, Warp automatically generates a descriptive title for the block using AI before producing the link.
Sharing terminal sessions
Live session sharing lets you invite teammates into an active terminal session so they can see your output in real time.Creating a shared session
Creating shared sessions is gated by theCreatingSharedSessions feature flag, which is enabled for paying team plans and for users in the session-sharing experiment. When the flag is active, a Share session button appears in the terminal header.
Open the sharing dialog
Click Share in the active terminal’s header, or open the command palette
and search for Share session.
Configure access
Choose who can join:
- Anyone with the link — anyone who has the URL can view the session.
- Team members — only members of your Warp team can join.
- Specific people — add individual email addresses.
SharedSessionWriteToLongRunningCommands is enabled, Write for
long-running commands.Viewing a shared session
Viewing shared sessions is controlled by theViewingSharedSessions feature flag (separate from CreatingSharedSessions). This separation allows Warp to enable viewing for a wider audience independently of creation.
When a teammate opens a session link, Warp joins them as a participant identified by their display name and, if available, avatar. Anonymous participants are shown with a generated display name.
Session ACLs
When theSessionSharingAcls feature flag is enabled, sessions use the same ACL model as Drive objects. The ACL model tracks subjects (individual users, teams, or anyone-with-link) and their access levels:
| Subject type | Description |
|---|---|
User | A specific Warp account, identified by UID. |
PendingUser | An invited user who has not yet accepted (identified by email). |
Team | All members of a Warp team. |
AnyoneWithLink | Public access — no authentication required to join. |
SessionSharingAcls flag can be toggled independently of the session-sharing server’s use_acls flag, which acts as a kill-switch.
Sharing Drive objects
Workflows, notebooks, AI facts, and other Drive objects use the same ACL model as sessions. Open the sharing dialog for any Drive object from the Drive panel’s context menu.Share a workflow
Right-click a workflow in the Drive panel and select Share. Set the
access level and copy the generated link. Recipients who open the link can
view and fork the workflow into their own Drive.
Share a notebook
Open the sharing dialog from the notebook’s title bar. Notebooks support
view and edit permissions — grant Edit to let teammates contribute
directly.
ServerId and resolved through the CloudModel. If an object has not been synced to the server yet, the link will not be available until the sync completes.
SharedWithMe
When theSharedWithMe feature flag is enabled, a Shared with me section appears in the Drive panel showing Drive objects that other users or teams have shared with you. Objects in this section behave like regular Drive objects — you can open, run, or fork them into your personal or team space.
Exporting and importing Drive objects
You can export any Drive object (or a folder of objects) to a local file and import it on another account or share it outside of Warp.Export
Right-click an object or folder in the Drive panel and select Export.
Warp writes a JSON file containing the object’s content and metadata.