Add the Windows .cmd launcher already used by browser-use/desktop
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
Research direction
Start by comparing the existing POSIX launcher at sdk/browser-harness-js with app/src/main/hl/stock/browser-harness-js/sdk/browser-harness-js.cmd from browser-use/desktop. Add the Windows launcher beside the standalone CLI, preserving delegation through Git for Windows bash.exe and the requested ERRORLEVEL behavior; done means it works as a normal command from cmd.exe and PowerShell.
Written by the indexing model from the issue text.
Description
Hi! I hit a small Windows setup issue with the standalone repo. The shipped CLI is the extensionless POSIX sdk/browser-harness-js script, and the setup docs only describe symlinking it on macOS/Linux. From cmd.exe / PowerShell, that does not give a normal Windows command entry point.
I noticed browser-use/desktop already carries a Windows launcher at:
app/src/main/hl/stock/browser-harness-js/sdk/browser-harness-js.cmd
and its bootstrap test explicitly checks that the .cmd exists and delegates through Git for Windows bash.exe.
I copied that launcher next to the standalone CLI (with a tiny local ERRORLEVEL propagation tweak) and it has been working well on Windows 11.
Would it make sense to include the same .cmd launcher in this repo too, so standalone installs work naturally from Windows shells/PATHEXT? If so, I would be happy to send a small focused PR.
- Dominant language
- TypeScript
- Stars
- 484
- Forks
- 39
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
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.
More from browser-use/browser-harness-js
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
browser-use/browser-harness-js#8 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in browser-use/browser-harness-js
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100