openclaw - 💡(How to fix) Fix [Feature]: Issue outreach

Summary

OpenClaw has been experiencing issues over the past month, with many users not only complaining but also opening tickets. It seems that the people working to solve these problems often don’t encounter them firsthand, relying instead on logical reasoning to decide what changes are needed, rather than testing on a system that actually has the issue. It might help to note in the report if the person reporting is willing to have a session with someone, provide access so the problem can be investigated, and, once a bug fix is made, have someone affected test it to confirm if it resolves the issue.

Problem to solve

Actually seeing an issue first hand and have a direct line with someone with an issue to test a bugfix.

Proposed solution

Have an extra option when someone opens an issue if they are willing to give access to a community member that wants to fix the issue.

This person can be contacted, a session can be held, and a fix can be made and provided to the person who has the issue. If the issue is fixed (also witnessed by the person who created the fix), this fix has a priority to end up in the next release.

Alternatives considered

No response

Impact

When the fixer doesn’t experience the issue firsthand, they can’t be 100% sure their solution will work. Yet tickets get closed, new versions roll out, and people with the same problem end up complaining again. A better way to involve the public is to give them the fixes to try out—if they work, those should get priority for release. This way, fixers who test their solutions can see them implemented in the product faster.

Evidence/examples

No response

Additional information

No response