Repository navigation
Windows/WSL Onboarding Experience from a Vibe Coder: Usage, Recovery and Migration #3338
Replies: 1 comment 2 replies
|
Thanks, @ExtraGreasy. This is genuinely useful, and you did attach it the right way. A first-user account from Windows/WSL, with Claude Code and Codex teams running, is exactly the view we can't easily get ourselves. The one-page summary and the action list make it easy to find the part we need, and the report keeps what OpenRig did apart from native-client limits, your own setup and local glue, which helps a lot. We'll use it as evidence for the onboarding and recovery work already under way, and your five priorities at the top give it a useful order. Your note that the relocation and the two hook and restore repairs were accepted locally is clear too. We read those as your local changes, not as something in a published release. One question, since the report lists the first installation as still unknown: do you remember roughly how you first installed OpenRig, for example by asking your coding agent to set it up, or by running the install command yourself? Knowing where the very first step started would help us place the setup map. |
Uh oh!
There was an error while loading. Please reload this page.
I use OpenRig with AI tools/Platforms and don't have limited conventional software engineering experience. I had AI put together a summary of my startup experience (not to complain but because maybe this information might be helpful finding/fixing bugs or presenting the current onboarding experience from my type of perspective). I currently only have running Claude Code and Codex teams on Windows/WSL on OpenRig, but plan to add more.
Some observations may be familiar to experienced engineers; they show where someone at my knowledge level needed help or could not tell what the system was doing. Again not to make a complaint or anything but I'm just trying to contribute data.
The report has a one-page summary and an index. It covers what worked well, confusing onboarding and status information, usage overhead, hooks and context recovery, automatic notifications, draft protection, pause/resume, and a completed operational-folder migration. It distinguishes OpenRig behavior, native-client/provider limitations, custom glue and local setup mistakes, and separates observed results from explanations or proposals.
The most useful improvements from this experience would be:
The migration update includes the additional repairs it needed: retained hook compatibility after an upgrade, stale recovery markers, a relocation rollback/reapply case, invalid managed-block configuration, backup/worktree complications and missing test prerequisites. Verified measurements are included, and I tried my best to clean up my personal data but please be nice if you find something and point it out to me.
Hoping this helps somehow in the development of OpenRig - If there's anything else you'd like me to investigate or check out that might be useful to you, just ask and I'll have an agent gather up the info lol. This is my first time adding files like this to a GitHub discussions post so hopefully I did it right.
OpenRig-Maintainer-Field-Report-20261116.md
OpenRig-Maintainer-Field-Report-20261116.pdf
All reactions