I'm quite incompetent in these matters, so I just asked Sonnet to write down some markdown describing the issue I've experienced. I have no ability to judge its validity so if you see it makes no sense don't bother at all and feel free to close/delete the issue.
I'm using Linux subsystem for Windows (WSL2) and Opencode.
Btw, I love the idea behind this skill!
marimo-pair: Correct Launch Pattern
Problem
When launching marimo for agent pairing (marimo-pair skill), the process silently died shortly after starting. The skill's finding-marimo.md already specifies --no-token, so discovery was not the issue. The actual cause was process detachment.
Using nohup ... & does not survive when the calling shell exits — the process receives SIGHUP and dies. This caused marimo to start, appear alive momentarily, and then silently disappear.
What the skill says to do
The skill's finding-marimo.md prescribes:
uv run marimo edit notebook.py --no-token
launched as a background task. This is correct, but incomplete for headless environments where no browser is available — the gio browser-open attempt causes an error, and without setsid the process dies when the agent's shell exits.
Missing flags
Add setsid, --headless, and < /dev/null to the launch command:
setsid uv run marimo edit examples/examples.py \
--no-token \
--headless \
> /tmp/marimo-examples.log 2>&1 < /dev/null &
setsid — starts the process in a new session, detaching it from the shell's process group so it survives shell exit
--headless — prevents marimo from trying to open a browser (avoids gio errors on headless/remote systems)
< /dev/null — detaches stdin so the process does not hang waiting for input
Verification
# Server is registered and discoverable
bash .agents/skills/marimo-pair/scripts/discover-servers.sh
# Server is responding
curl -s http://localhost:2718/api/sessions
I'm quite incompetent in these matters, so I just asked Sonnet to write down some markdown describing the issue I've experienced. I have no ability to judge its validity so if you see it makes no sense don't bother at all and feel free to close/delete the issue.
I'm using Linux subsystem for Windows (WSL2) and Opencode.
Btw, I love the idea behind this skill!
marimo-pair: Correct Launch Pattern
Problem
When launching marimo for agent pairing (marimo-pair skill), the process silently died shortly after starting. The skill's
finding-marimo.mdalready specifies--no-token, so discovery was not the issue. The actual cause was process detachment.Using
nohup ... &does not survive when the calling shell exits — the process receives SIGHUP and dies. This caused marimo to start, appear alive momentarily, and then silently disappear.What the skill says to do
The skill's
finding-marimo.mdprescribes:launched as a background task. This is correct, but incomplete for headless environments where no browser is available — the
giobrowser-open attempt causes an error, and withoutsetsidthe process dies when the agent's shell exits.Missing flags
Add
setsid,--headless, and< /dev/nullto the launch command:setsid— starts the process in a new session, detaching it from the shell's process group so it survives shell exit--headless— prevents marimo from trying to open a browser (avoidsgioerrors on headless/remote systems)< /dev/null— detaches stdin so the process does not hang waiting for inputVerification