Repository navigation
Windows Support #88
Description
Activity
Thanks for asking. Not on native Windows today. OpenRig is built on tmux, and every agent runs in its own tmux session, so it needs macOS or Linux.
We haven't tested it under WSL2, where tmux does run. If you try it there, we'd like to hear what works and what breaks. There's no Windows plan to share right now.
— dev-planner@v-openrig-build, on behalf of @mvschwarz
One more pointer we should have included: there's an open community pull request, #32, that includes Windows boot fixes using psmux, with the contributor's own Windows test results in the thread. It isn't merged, and we've said we'll separate the shared improvements from any Windows support claim, so it's not a supported path yet. If you're up for trying it, feedback on that PR would help.
— dev-planner@v-openrig-build, on behalf of @mvschwarz
Thanks, @dajiaohuang, for the WSL2 test this thread asked for: a real rig with a Codex seat and a Pi seat on 0.6.6, through
rig send,rig capture,rig downandrig up, and resume, with the earlier markers recalled after the restore. Thanks too for writing down the setup lessons, especially that a managed Pi seat needs its credentials in its own agent directory. #956, your build fix for a native Windows checkout, is in review. On native Windows support itself, including your fork experiment, there's no decision yet; we'll reply here.A correction to our last comment: we thanked you "especially that a managed Pi seat needs its credentials in its own agent directory", which made that sound like the only way. A global Pi login isn't shared with managed seats automatically, and a seat can get its credentials in either of two ways: configure the provider in the seat's own agent directory (
PI_CODING_AGENT_DIR, inauth.jsonormodels.json), or, for a model provider whose API key variable OpenRig passes through, set that key in the daemon's environment, add it torecovery.provider_auth_env_allowlist, use the model as<provider>/<id>, then restart the daemon and relaunch the seat.Thanks, @dajiaohuang, for the WSL2 report. It's really cool that there's now a path for people to use OpenRig on Windows. WSL2 is OpenRig's Windows route for now, because it's what we can support and maintain, and your setup is now in the getting-started guide as a reported working setup (#960, on main, not in a release yet). #956 is in review, with a change request from us on that thread.
We're genuinely excited about native Windows as something we could support eventually, but before committing to it we want to understand what keeping it working would cost, so we're treating it as a research question. Your native experiment and what you've found, including today's update, are welcome input to that research. That isn't a promise to upstream it, and we're not asking you for more work on it.
What are you trying to do, and what stops you today?
This repo looks promising but it unfortunately looks like it doesn't support Windows? Any plans?
What would you like OpenRig to do?
Support Windows
How do you handle it now?
No response
OpenRig version
No response