I want to use Warp notebook in multiple tabs / terminals,

Open
#4,911 4 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
cli

Research direction

No files, tests, or implementation entry points are mentioned. Start by reproducing the notebook behavior on macOS with a notebook containing an executed command, then trace how notebook selection is associated with terminal tabs; done means the same notebook can be opened and used independently in multiple tabs without redirecting to the original terminal.

Written by the indexing model from the issue text.

Description

area:warp-drive enhancement triaged
Dupe Check
Describe the bug

when i open a new terminal and click on the notebook, it will take me to the terminal opened with that notebook. So, i have to duplicate the same content of the notebook again if i want to use in multiple tabs.

To reproduce

Simply create a new notebook with some contents.
execute a command from the new notebook content.
Open a new tab / terminal, try to use the same notebook, it will go back to the old opened notebook

Expected behavior

No response

Screenshots

No response

Operating system

MacOS

Operating system and version

Sonoma 12.x

Shell Version

No response

Current Warp version

No response

Regression

No, this bug or issue has existed throughout my experience using Warp

Recent working Warp date

No response

Additional context

No response

Does this block you from using Warp daily?

Yes, this issue prevents me from using Warp daily.

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e

None

Dominant language
Rust
Stars
65.1k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from warpdotdev/warp

All issues in warpdotdev/warp

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.