Feature Request: Add `wsl` / `wsl.exe` command support
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 81.1k
- Forks
- 5.1k
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 40
Description
Feature Request: RTK support for wsl and wsl.exe commands
Background
Running rtk discover --all on a Windows 11 + WSL2 hybrid environment showed:
| Command | Count (30 days) |
|---|---|
wsl |
523 |
wsl.exe |
56 |
These are the most-used unhandled commands by far, with zero RTK coverage.
Use Case
On Windows with WSL2, nearly every Linux tool invocation goes through wsl:
wsl -d Ubuntu -- git status
wsl -d Ubuntu -- npm run build
wsl -d Ubuntu -- python3 script.py
The output is often large (file listings, build logs, test results) — exactly where RTK filtering saves the most tokens.
Proposed Behavior
rtk wsl [args] should:
- Pass the command through to
wsl/wsl.exe - Apply the same output filtering/truncation as other RTK commands
- Optionally detect the inner command (e.g.
wsl -- git status→ apply git filtering rules)
Environment
- OS: Windows 11 Pro
- RTK version: 0.40.0
- Shell: PowerShell + WSL2 Ubuntu
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.
Research direction
The issue names no files or tests; start by tracing how RTK dispatches existing command wrappers and applies output filtering. Compare handling of wsl -d Ubuntu -- git status with the existing git filtering rules. Done means both wsl and wsl.exe pass through correctly and their output receives the intended filtering, with coverage in the relevant CLI tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100