@problems. When you mention problems, Elastic sees the complete list of diagnostics with file locations, error messages, and severity levels.
How Problem Mentions Work
When you type@problems in the chat input, Elastic automatically gathers:
- All errors: Critical issues that prevent compilation/execution
- All warnings: Potential issues that should be addressed
- File locations: Exact line and column numbers
- Error messages: Complete diagnostic information
- Severity levels: Error, warning, info, and hint classifications
Syntax
@problems and Elastic will include all current workspace diagnostics.
What Elastic Sees
When you mention problems, Elastic receives:- Complete error list - Every diagnostic in your workspace
- File paths - Exact location of each issue
- Line numbers - Precise positioning information
- Error messages - Full diagnostic descriptions
- Severity levels - Priority and importance of each issue
- Error codes - Specific diagnostic identifiers when available
Best Practices
When to Use Problem Mentions
- Debugging sessions:
@problems Help me fix all these errors - Code review:
@problems Are these warnings important? - Before deployment:
@problems Clean up before release - Learning:
@problems Explain what these errors mean
Combining with File Mentions
Target specific problematic files:Combining with Terminal Output
Get comprehensive debugging context:Types of Problems Detected
TypeScript/JavaScript Errors
- Type mismatches
- Missing imports
- Undefined variables
- Syntax errors
Linting Issues
- ESLint violations
- Prettier formatting
- Custom rule violations
- Code style inconsistencies
Build Errors
- Compilation failures
- Missing dependencies
- Configuration issues
- Asset problems
Runtime Warnings
- Deprecated API usage
- Performance concerns
- Security vulnerabilities
- Best practice violations
Problem Severity Levels
Errors (Critical)
- Red indicators: Must be fixed
- Block compilation: Prevent builds
- High priority: Address immediately
Warnings (Important)
- Yellow indicators: Should be fixed
- Allow compilation: Don’t block builds
- Medium priority: Address when possible
Info (Informational)
- Blue indicators: Good to know
- Suggestions: Improvements available
- Low priority: Address when convenient
Hints (Subtle)
- Gray indicators: Minor suggestions
- Optimizations: Performance or style
- Lowest priority: Address if desired
Tips for Effective Problem Mentions
- Regular checks: Use
@problemsfrequently during development - Prioritize errors: Fix errors before warnings
- Batch similar issues: Group related problems together
- Understand context: Ask Elastic to explain unfamiliar errors
- Prevent regression: Check problems before committing code
Integration with Memory Bank
Problem mentions help Elastic learn:- Common error patterns: Mistakes you frequently make
- Project-specific issues: Recurring problems in your codebase
- Resolution strategies: How you prefer to fix certain errors
- Code quality standards: Your tolerance for different warning types
Common Use Cases
Debugging Session
Code Quality Review
Pre-commit Cleanup
Learning and Understanding
Batch Error Fixing
Combining with Other Mentions
With File Mentions
With Folder Mentions
With Terminal Output
With Git Changes
Troubleshooting
No Problems Detected
If@problems shows no issues:
- Check if your IDE/editor is running diagnostics
- Verify language servers are active
- Ensure project is properly configured
- Try opening/saving files to trigger diagnostics
Too Many Problems
If overwhelmed by problem count:- Focus on errors first, then warnings
- Use file mentions to target specific areas
- Ask Elastic to prioritize the most critical issues
- Consider filtering by file or directory
Missing Expected Problems
If you expect more problems:- Check if all files are included in your project
- Verify linting and type checking are enabled
- Ensure all necessary extensions are installed
- Try restarting your language server