🐛 Bug Reports & Feature Requests
Help shape ClawManager by reporting bugs and requesting features directly from the app.
Built-In Feedback
ClawManager has two feedback buttons in the top-right corner of every agent view. A small bug icon for bug reports and a lightbulb icon for feature requests. Both open a modal where you can describe the issue or idea, and your report gets sent directly to the ClawManager team.
Where to find them
Look for the 🐛 bug icon and 💡 lightbulb icon in the agent header bar at the top of the screen. They are always available regardless of which tab or category you are viewing.
🐛 Reporting a Bug
Click the bug icon to open the bug report modal. Here is what you will see:
1. Select a bug type
Choose the category that best matches your issue:
- • UI / Visual glitch — layout issues, broken elements, rendering problems
- • Connection / Gateway — cannot connect, gateway errors, timeouts
- • Crash / Unexpected close — app closes on its own or freezes completely
- • Performance / Freezing — slow responses, high CPU, lag
- • Auth / Login problem — sign-in failures, token issues
- • Feature not working — something that should work but does not
- • Other — anything that does not fit the above
2. Describe the problem
Write a description of what happened, what you expected, and any steps to reproduce. Minimum 20 characters. The more detail you include, the easier it is for the team to find and fix the issue.
3. Attach screenshots (optional)
You can drag and drop or click to upload up to 3 screenshots. Supported formats are PNG, JPEG, WEBP, and GIF, with a maximum size of 5MB per file. Screenshots help the team understand visual issues immediately.
4. Technical details (auto-collected)
ClawManager automatically collects your OS, platform, app version, screen resolution, current page, and gateway version. You can expand the "Technical Details" section at the bottom of the modal to review exactly what gets sent. No personal data is included.
🔍 Duplicate Detection
As you type your description, ClawManager checks for similar reports that other users have already submitted. If a match is found, you will see an amber notice like:
"3 users reported a similar issue — submit anyway, you may earn Confirmation Points."
You can still submit your report. Confirming an existing bug earns you Confirmation Points once the team reviews it. This helps prioritize the most impactful issues.
💡 Requesting a Feature
Click the lightbulb icon to open the feature request modal. The process is similar to bug reports but with a few extra fields.
1. Select a category
Choose what area the feature falls into:
- • UI / Design — visual improvements, layout changes
- • Integration / Connections — new channels, services, APIs
- • Workflow / Automation — cron, heartbeat, workflows, webhooks
- • Performance — speed, efficiency, resource usage
- • Accessibility — usability, screen readers, keyboard navigation
- • Other — anything else
2. Give it a title
A short summary of the feature, up to 100 characters. Think of it as a headline: "Add keyboard shortcuts for tab switching" or "Show token cost per session."
3. Describe the feature
Explain what you want and how it should work. Minimum 20 characters, but more detail helps us build exactly what you need.
4. Use case (optional)
Describe why you need this feature and how you would use it. This context helps the team prioritize and design the feature correctly.
5. Set impact level
Tell us how important this is to your workflow:
- 🟢 Nice to have — would be cool but not essential
- 🟡 Would help my workflow — regular pain point
- 🔴 Blocking / Critical for me — cannot do what I need without it
👍 Upvoting Existing Requests
When you start typing a feature request, ClawManager searches for similar requests that already exist. If matches are found, you will see them listed with their current upvote count and an Upvote button.
Upvoting an existing request is often more effective than submitting a duplicate. It signals demand and helps the team know which features to build next. You can still submit your own request if you think it is different enough.
🏆 Points System
ClawManager rewards users who help improve the product through bug reports and feature requests.
Bug reports
You earn points when the team confirms your bug report. If you confirm a bug that someone else reported first, you may earn Confirmation Points.
Feature requests
You earn 25 points when your feature request gets planned, and 75 points when it ships. Upvoting existing requests also earns points when the feature is delivered.
💡 Tips for Good Reports
For bug reports
- • Include steps to reproduce: "I clicked X, then Y, and saw Z"
- • Mention what you expected vs. what actually happened
- • Attach a screenshot if the issue is visual
- • Note if the issue is consistent or intermittent
For feature requests
- • Focus on the problem, not just the solution
- • Include a use case so the team understands the context
- • Check for similar requests and upvote if one exists
- • Be specific about what "done" looks like for you
🔐 Signed In vs. Anonymous
You can submit bug reports and feature requests whether or not you are signed in to a ClawManager account. However, signing in has benefits:
Signed in
Reports are linked to your account. You earn points, can track your submissions, and the team can follow up if they need more detail.
Anonymous
Reports are still accepted and reviewed, but points cannot be awarded and the team cannot contact you for follow-up.