I have filed a few issues on Github. The first one is a week old and hasn’t been looked at. I’ve uncovered a few plumbing issues today as well.
Most of what Wingman ships is already readable: the VS Code base and the bundled Codex engine are open source, and the wingman-dashboard extension ships as unminified JavaScript. Publishing the source here would cost little and would help in a few concrete ways:
- Contributions instead of reports. Several of the open issues are one-line fixes. With the source here, they could arrive as pull requests.
- Packaging for more distributions. Packagers for Arch, Fedora and others could build Wingman properly instead of repackaging the
.deb. - Trust. For a tool that runs an agent with shell access on developers' machines, being able to review the code is a strong selling point, especially for a European company competing with much larger vendors.
If publishing the whole codebase isn't an option, opening just the Linux launcher (/usr/bin/wingman) and the packaging scripts would already cover most of the fixes above.
Either way, it would help to know whether issues here are monitored. If not, could the README point to the preferred channel?
