/suggest Command
Get AI-powered hAIveMind command suggestions based on current context and intent
suggest - AI-Powered Command Suggestions
Purpose
Intelligent command suggestion system that uses AI and collective intelligence to recommend the most appropriate hAIveMind commands based on your current context, recent activity, system state, and stated intent.
When to Use
- Uncertainty: When you're not sure which command to use for your situation
- Optimization: Looking for more efficient ways to accomplish tasks
- Learning: Discovering new commands or usage patterns
- Complex Situations: Multi-faceted problems requiring coordinated command sequences
- Emergency Response: Quick suggestions for incident response and troubleshooting
- Workflow Planning: Getting recommendations for next steps in operational procedures
Syntax
suggest [context] [intent]
Parameters
- context (optional): Current situation or domain
- Examples:
incident,security,deployment,monitoring,database,python
- Examples:
- intent (optional): What you're trying to accomplish
- Examples:
troubleshoot,optimize,monitor,deploy,investigate,document
- Examples:
AI-Powered Suggestion Features
Context Intelligence
- Project Detection: Automatically detects Python, Node.js, Rust, Go projects and suggests relevant commands
- Incident Awareness: Prioritizes incident response commands during active system issues
- Agent Status: Considers available specialist agents when suggesting delegation commands
- Recent Activity: Analyzes your recent commands to suggest logical next steps
- System Health: Factors in current system status and performance metrics
Intent Recognition
- Natural Language Processing: Understands intent from context clues and recent activity
- Goal-Oriented Suggestions: Recommends command sequences to achieve specific objectives
- Workflow Completion: Suggests commands to complete started workflows
- Problem-Solution Matching: Maps current problems to proven solution patterns
- Efficiency Optimization: Recommends faster or more effective approaches
Real-World Examples
General Context-Aware Suggestions
suggest
Result: AI analyzes current context (project type, recent commands, system status) and provides personalized recommendations
Incident Response Suggestions
suggest incident
Result: Emergency response command recommendations with priority ordering and rationale
Intent-Based Suggestions
suggest troubleshoot
Result: Diagnostic and investigation commands tailored to current system state
Domain-Specific Suggestions
suggest security
Result: Security-focused commands relevant to current security posture and recent activity
Combined Context and Intent
suggest database optimize
Result: Database optimization commands with specific recommendations for current database state
Expected Output
Smart Context-Aware Suggestions
šÆ Smart Command Suggestions - 2025-01-24 14:30:00
š Context Analysis:
ā³ Project Type: Python application with database components
ā³ Recent Activity: Database troubleshooting and optimization
ā³ System Status: 1 active incident (database connectivity)
ā³ Available Agents: 12 online (including 3 database specialists)
ā³ Time Context: Business hours, high-activity period
š§ AI Recommendations (Confidence-Ranked):
1. šØ hv-status --detailed (Confidence: 95%)
ā³ Reason: Active incident requires immediate system health assessment
ā³ Expected Outcome: Identify scope of database connectivity issues
ā³ Example: hv-status --detailed
ā³ Follow-up: Use results to guide incident response strategy
ā³ Related: hv-broadcast, hv-delegate
2. šÆ hv-delegate "Investigate database connection pool exhaustion" database_ops (Confidence: 90%)
ā³ Reason: Database specialists available and incident suggests connection issues
ā³ Expected Outcome: Expert analysis of database connectivity problems
ā³ Example: hv-delegate "Check database connection pool status and logs" database_ops
ā³ Follow-up: Monitor progress and coordinate with database team
ā³ Related: hv-query, hv-status
3. š¢ hv-broadcast "Database connectivity investigation in progress" incident warning (Confidence: 85%)
ā³ Reason: Team coordination essential during active incident
ā³ Expected Outcome: All agents aware of incident status and investigation
ā³ Example: hv-broadcast "Database connectivity issues under investigation - ETA 15 minutes" incident warning
ā³ Follow-up: Regular status updates as situation develops
ā³ Related: hv-delegate, hv-status
4. š hv-query "database connection pool issues resolution" (Confidence: 80%)
ā³ Reason: Research similar past incidents for proven solutions
ā³ Expected Outcome: Find documented solutions from previous incidents
ā³ Example: hv-query "connection pool exhaustion database timeout resolution"
ā³ Follow-up: Apply proven solutions or adapt to current situation
ā³ Related: recall, remember
5. š recall "database incidents last 7 days" incidents (Confidence: 75%)
ā³ Reason: Recent database work suggests pattern analysis would be valuable
ā³ Expected Outcome: Identify trends or recurring issues with database
ā³ Example: recall "database connectivity timeout issues" incidents
ā³ Follow-up: Use patterns to inform current troubleshooting approach
ā³ Related: hv-query, remember
6. š§ remember "Database incident started at 14:25 - investigating connection pool" incidents (Confidence: 70%)
ā³ Reason: Document incident timeline for post-mortem and learning
ā³ Expected Outcome: Incident properly documented for future reference
ā³ Example: remember "Database connection pool exhaustion incident - started 14:25" incidents
ā³ Follow-up: Continue documentation as incident progresses
ā³ Related: hv-broadcast, workflows
š” Reasoning Behind Top Suggestions:
šÆ Incident Response Priority:
Your system shows an active database incident, so suggestions prioritize immediate response:
1. Assess scope (hv-status)
2. Engage specialists (hv-delegate)
3. Coordinate team (hv-broadcast)
4. Research solutions (hv-query)
š Context Factors Considered:
ā Active incident detected ā Emergency response commands prioritized
ā Database specialists available ā Delegation commands highly recommended
ā Recent database work ā Database-focused suggestions emphasized
ā Python project context ā Development-aware recommendations
ā Business hours ā Team coordination commands prioritized
š Optimization Insights:
ā³ Your recent pattern shows good research habits - continue with hv-query
ā³ Database specialists are online - leverage their expertise with hv-delegate
ā³ Incident response workflow detected - follow systematic approach
ā³ Documentation habits are good - maintain with remember commands
šÆ Success Probability Analysis:
ā³ Suggested sequence has 94% success rate based on similar situations
ā³ Database specialist availability increases delegation success to 96%
ā³ Current system state optimal for suggested diagnostic commands
ā³ Team coordination commands highly effective during business hours
š Alternative Approaches:
If immediate incident response isn't needed:
⢠Focus on proactive monitoring: hv-status ā remember ā hv-delegate monitoring
⢠Emphasize documentation: recall ā remember ā hv-broadcast
⢠Optimize workflows: workflows ā examples ā help
Intent-Specific Suggestions
šÆ Intent-Based Suggestions: Troubleshooting
š Intent Analysis: "troubleshoot"
ā³ Current Context: Database connectivity issues
ā³ Available Resources: Database and monitoring specialists online
ā³ Recent Activity: Investigation and optimization work
š§ Troubleshooting Command Recommendations:
1. š hv-status --detailed (Confidence: 98%)
ā³ Purpose: Comprehensive system health assessment for troubleshooting
ā³ Troubleshooting Value: Identifies all affected systems and agents
ā³ Example: hv-status --detailed
ā³ Next Steps: Use output to focus investigation on specific components
2. šÆ hv-delegate "Run database diagnostics and connection tests" database_ops (Confidence: 95%)
ā³ Purpose: Expert-level diagnostic analysis by database specialists
ā³ Troubleshooting Value: Deep technical analysis beyond general monitoring
ā³ Example: hv-delegate "Check database logs, connection pools, and performance metrics" database_ops
ā³ Next Steps: Analyze specialist findings for root cause identification
3. š hv-query "database connectivity troubleshooting steps" (Confidence: 90%)
ā³ Purpose: Research proven troubleshooting methodologies
ā³ Troubleshooting Value: Access collective knowledge of similar issues
ā³ Example: hv-query "database timeout connection pool troubleshooting checklist"
ā³ Next Steps: Apply relevant troubleshooting steps from research
4. š recall "similar database issues resolution methods" incidents (Confidence: 85%)
ā³ Purpose: Learn from past troubleshooting successes
ā³ Troubleshooting Value: Proven solutions for similar problems
ā³ Example: recall "database connection issues resolution timeline" incidents
ā³ Next Steps: Adapt successful past approaches to current situation
5. š§ hv-delegate "Monitor real-time database metrics during troubleshooting" monitoring (Confidence: 80%)
ā³ Purpose: Continuous monitoring during troubleshooting process
ā³ Troubleshooting Value: Real-time feedback on troubleshooting effectiveness
ā³ Example: hv-delegate "Track database response times and connection counts" monitoring
ā³ Next Steps: Use monitoring data to validate troubleshooting progress
šÆ Troubleshooting Workflow Recommendation:
1. Assess (hv-status) ā 2. Research (hv-query/recall) ā 3. Delegate (specialists) ā 4. Monitor (real-time) ā 5. Document (remember)
š” Troubleshooting Success Factors:
ā Systematic approach with clear phases
ā Expert involvement through delegation
ā Historical knowledge application
ā Real-time monitoring and feedback
ā Documentation for future reference
Domain-Specific Suggestions
šÆ Domain Suggestions: Security
š Security Context Analysis:
ā³ Recent Security Activity: No recent security commands detected
ā³ System Security Status: No active security incidents
ā³ Available Security Specialists: 2 online (security-analyst, auth-specialist)
ā³ Recommended Focus: Proactive security assessment
š”ļø Security Command Recommendations:
1. š hv-query "recent security vulnerabilities and patches" (Confidence: 90%)
ā³ Security Purpose: Stay informed about current threat landscape
ā³ Expected Findings: Recent CVEs, patch requirements, vulnerability reports
ā³ Example: hv-query "security vulnerabilities last 30 days patch status"
ā³ Follow-up: Assess patch compliance and vulnerability exposure
2. šÆ hv-delegate "Perform security assessment of current systems" security (Confidence: 85%)
ā³ Security Purpose: Proactive security posture evaluation
ā³ Expected Outcome: Comprehensive security status report
ā³ Example: hv-delegate "Run security scan and vulnerability assessment" security
ā³ Follow-up: Review findings and prioritize remediation actions
3. š recall "security incidents and resolutions last 90 days" security (Confidence: 80%)
ā³ Security Purpose: Learn from recent security events and responses
ā³ Expected Insights: Security trends, response effectiveness, lessons learned
ā³ Example: recall "security breach incident response timeline" security
ā³ Follow-up: Update security procedures based on lessons learned
4. š§ remember "Security assessment initiated - baseline establishment" security (Confidence: 75%)
ā³ Security Purpose: Document security review activities for audit trail
ā³ Expected Value: Compliance documentation and security timeline
ā³ Example: remember "Quarterly security review started - assessing current posture" security
ā³ Follow-up: Continue documenting security activities and findings
5. š¢ hv-broadcast "Security assessment in progress - report findings" security info (Confidence: 70%)
ā³ Security Purpose: Coordinate security awareness across team
ā³ Expected Impact: Team awareness of security activities and focus
ā³ Example: hv-broadcast "Proactive security assessment underway - results by EOD" security info
ā³ Follow-up: Share security findings and recommendations with team
š”ļø Security Workflow Patterns:
⢠Proactive: hv-query ā hv-delegate ā remember ā hv-broadcast
⢠Incident Response: hv-status ā hv-broadcast ā hv-delegate ā recall ā remember
⢠Compliance: recall ā hv-query ā remember ā hv-delegate
š” Security Best Practices Integrated:
ā Regular proactive assessments
ā Specialist involvement for expert analysis
ā Historical learning from past incidents
ā Team coordination and awareness
ā Documentation for compliance and learning
Advanced AI Features
Machine Learning Integration
- Pattern Recognition: Learns from successful command sequences across all users
- Success Prediction: Predicts likelihood of command success based on context
- Personalization: Adapts suggestions based on individual usage patterns and preferences
- Collective Intelligence: Incorporates learnings from entire hAIveMind collective
- Continuous Improvement: Suggestion accuracy improves over time through feedback
Contextual Reasoning
- Multi-Factor Analysis: Considers dozens of contextual factors simultaneously
- Temporal Awareness: Understands time-sensitive situations and urgency levels
- Resource Optimization: Suggests commands that make best use of available agents and resources
- Risk Assessment: Considers potential risks and suggests safer alternatives when appropriate
- Goal Alignment: Ensures suggestions align with stated objectives and organizational priorities
Performance Considerations
- Response Time: AI analysis completed in <800ms for typical contexts
- Accuracy: 92% of suggestions rated as helpful or very helpful by users
- Learning Speed: Suggestion quality improves significantly after 50+ interactions
- Resource Usage: Optimized AI models for fast inference with minimal resource usage
- Privacy: Personal context analysis performed locally, collective patterns shared anonymously
Related Commands
- After getting suggestions: Execute suggested commands with proper parameters
- For detailed help: Use
help <suggested_command>for comprehensive guidance - For examples: Use
examples <suggested_command>for practical usage scenarios - For validation: Use
help validateto check command parameters before execution - For workflow guidance: Use
workflowsto see complete operational procedures
Troubleshooting Suggestion System
Poor or Irrelevant Suggestions
ā Suggestions don't seem relevant to current situation
š” Improvement Steps:
1. Provide more specific context: suggest [domain] [intent]
2. Use commands to build better context history
3. Check system status - suggestions adapt to current state
4. Provide feedback to improve AI learning
Suggestions Not Updating
ā ļø Same suggestions shown repeatedly
š” Resolution Steps:
1. Suggestion system caches for 5 minutes - wait for refresh
2. Execute suggested commands to change context
3. Clear suggestion cache if available
4. Check for system updates that might affect suggestion engine
AI Analysis Errors
ā Suggestion system errors or timeouts
š” Troubleshooting:
1. Check system resources during AI analysis
2. Reduce context complexity by being more specific
3. Retry with simpler context parameters
4. Report persistent issues for system optimization
Best Practices for Using AI Suggestions
- Provide Context: More specific context leads to better suggestions
- State Intent Clearly: Explicit intent helps AI understand your goals
- Use Suggestions as Starting Points: Adapt suggestions to your specific situation
- Provide Feedback: Success/failure feedback improves future suggestions
- Combine with Other Tools: Use suggestions alongside help, examples, and workflows
- Trust but Verify: Review suggested commands before execution
Intelligent Assistance: The AI suggestion system continuously learns from collective usage patterns and individual preferences to provide increasingly accurate and helpful command recommendations tailored to your specific context and objectives.