Cross-platform Python clients instead of shell scripts

[dewwwey]

I struggled to get this working on Windows for a while with the provided shell scripts. Would you be interested in using Python instead?
I forked the repo and tried my hand at Python versions aiming for feature parity. I can create a PR if you are interested.

Cheers

[manzt]

Thanks for offering! I’m not totally opposed, but the shell scripts have fewer dependencies, so I’d prefer to understand the gaps first. Which version of marimo-pair were you using, and were you running it through PowerShell, WSL, Git Bash, or something else? We recently shipped some Windows improvements, so any specific errors would also be helpful.

[dewwwey]

I've asked an agent (GLM 5.2 in Crush) to reproduce the problems I encountered earlier, I updated the skill beforehand.

For the marimo-pair shell scripts on Windows, I hit three distinct problems:

1. **WSL path translation**: `bash` resolves to `C:\WINDOWS\system32\bash.exe` (WSL), which can't open Windows paths like `C:/Users/.../execute-code.sh` — it needs Linux-style `/mnt/c/Users/.../`. A user following the skill's documented `bash scripts/execute-code.sh` invocation gets "No such file or directory."
2. **CRLF line endings break the script**: The scripts live on the Windows filesystem with `\r\n` endings, so `/bin/bash` inside WSL reads `set -euo pipefail\r` and fails with `invalid option name` before doing anything. The script needs to be `tr -d '\r'`-filtered or have LF-only endings to run.
3. **`-c` quoting is mangled across shell boundaries**: Passing `-c "print('connected')"` through the `mvdan/sh → bash.exe → /bin/bash` chain strips the single quotes, so the kernel receives `print(connected)` (a `NameError`). Only stdin input (`-`) survives intact.

Net effect: none of the skill's documented `bash scripts/execute-code.sh ... -c "..."` examples work unmodified on Windows — they require path translation, line-ending normalization, and avoiding `-c` in favor of stdin.

As for dependencies, I made sure the Python-versions are stdlib only - so it adds no additional dependencies at all.

[sanzoghenzo]

Hi, just started with marimo pair on my windows laptop with oh-my-pi, these are the issues encrountered.

At first I got discover-servers.sh needs jq on PATH. indeed, I didn't have it installed, neither on windows nor in WSL. but the LLM (GPT 5.3 Codex, the only one provided by my company) went ahead and started the (already started) marimo, found port conflicts, restarted marimo, and finally got connected.

I tried a second time, after installing jq on WSL. the script returned

127.0.0.1:2718 is running on the Windows host (PID 27488) but answered at no address reachable from WSL.
WSL's NAT network cannot reach a service bound to 127.0.0.1 on the host. Options:
   - restart marimo on the host with --host 0.0.0.0 (reachable from WSL at 172.22.144.1)
   - or switch WSL to mirrored networking: add 'networkingMode=mirrored' under [wsl2] in %USERPROFILE%\.wslconfig, then run 'wsl --shutdown'
   - or run these scripts from Git Bash / PowerShell on the Windows side
If marimo is no longer running, PID 27488 may belong to an unrelated process that reused the id.

Then the model got confused about the host environment, because it tested direct access with curl (that is available in powershell as an alias) and assumed it was inside the WSL, but then each bash invocation failed. After many attempts, it wrote a javascript marimoExec function to execute python code inside marimo (python backend is unavailable since I used marimo sandboxed and there are no venvs in the working directory).
It worked, but it burned something like 10K tokens.

[venkashank]

I would prefer having the option of using python scripts in leau of bash while on windows. Wsl and cygwin are not options for many corporate users of marimo.

[manzt]

Hi there, thank you for your patience on this. We are currently working on migrating the tools (Bash scripts) bundled in the marimo-pair skill into a CLI that we ship with marimo itself for agents (under marimo pair which can be invoked by the agent via uvx marimo pair).

• feat(pair): add an agent-facing CLI for live notebook sessions marimo#10777

In the meantime, I would be open to shipping a standalone Python script in the skill here.