💭 Feature Requests
We want the LIMO Pro + MyCobot + YOLO system to evolve with the needs of its users and contributors.
This page explains how to submit feature requests, how they’re evaluated, and how we decide on implementation priority.
📌 Current Community Requests
| Feature | Description | Status |
|---|---|---|
| Multi-object queue handling | Detect, store, and collect multiple targets in a single mission | Under Review |
| Web dashboard control | Browser-based UI for monitoring and manual override | Planned |
| Voice command support | Control robot states using voice inputs | Planned |
| Configurable YOLO classes | Switch detection targets without retraining | Accepted |
| Health diagnostics node | Monitors CPU, battery, motor status | Accepted |
📨 Request Submission Process
- GitHub Issues
- Discord
- Go to the Project GitHub Repository.
- Click New Issue → Select Feature Request.
- Fill in:
- Feature name
- Problem it solves
- Proposed implementation
- Priority level
- Join the Discord server.
- Post your request in the #feature-requests channel.
- A maintainer will tag it for tracking.
⚖️ Evaluation Criteria
When deciding whether to implement a feature, we consider:
- Impact — Will it significantly improve workflow or capabilities?
- Feasibility — Can it be implemented with available hardware and time?
- Performance Cost — Will it slow down detection, navigation, or arm control?
- Safety — Does it introduce any risk to the robot, objects, or users?
- Maintainability — Can it be supported long-term without major rework?
🏷 Implementation Priorities
| Priority | Definition | Example |
|---|---|---|
| High | Critical for performance, reliability, or safety | Health diagnostics node |
| Medium | Improves usability or flexibility | Voice command support |
| Low | Nice-to-have but non-essential | Fun voice feedback variations |
Pro Tip
The fastest way to get your feature accepted is to submit a proof-of-concept or working prototype along with your request.
📖 See How to Contribute Your Feature