wxt dev keyboard shortcut handler captures all stdin in tmux
Open
@nishu-murmu is already working on this.
Since Jul 4, 2026.
pending-triage
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When running wxt dev inside tmux, stdin appears hijacked by the dev process. Keystrokes typed in the browser are consumed by the keyboard shortcut handler instead of reaching the browser instance
Reproduction
- start a tmux session
- run
wxt dev - type something inside the launched browser instance
Steps to reproduce
No response
System Info
System:
OS: macOS 26.3.1
CPU: (8) arm64 Apple M1 Pro
Memory: 101.02 MB / 16.00 GB
Shell: 4.1.2 - /opt/homebrew/bin/fish
Binaries:
Node: 22.15.0 - /Users/simonkrenn/.local/share/mise/installs/node/22.15.0/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.9.2 - /Users/simonkrenn/.local/share/mise/installs/node/22.15.0/bin/npm
pnpm: 8.12.0 - /opt/homebrew/bin/pnpm
bun: 1.3.5 - /Users/simonkrenn/.bun/bin/bun
Browsers:
Chrome: 147.0.7727.56
Safari: 26.3.1
npmPackages:
wxt: ^0.20.22 => 0.20.22
Used Package Manager
pnpm
Validations
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.