@terminal. When you mention terminal output, Elastic sees the complete output with formatting preserved, perfect for debugging build errors, test failures, or command results.
How Terminal Mentions Work
When you type@terminal in the chat input, Elastic automatically captures:
- Recent terminal output - The last several lines of terminal activity
- Command history - What commands were executed
- Error messages - Complete error output and stack traces
- Formatting - Colors, indentation, and structure preserved
- Context - Working directory and environment information
Syntax
@terminal and Elastic will include your recent terminal output.
What Elastic Sees
When you mention terminal output, Elastic receives:- Complete output - All recent terminal text
- Command context - What commands were run
- Error details - Full error messages and stack traces
- Formatting - Original colors and structure
- Timestamps - When commands were executed
- Working directory - Current path context
Best Practices
When to Use Terminal Mentions
- Build errors:
@terminal The build is failing with these errors - Test failures:
@terminal Tests are not passing - Command help:
@terminal What does this error mean? - Installation issues:
@terminal Package installation failed - Script debugging:
@terminal My script isn't working correctly
Combining with File Mentions
Connect terminal output to specific files:Combining with Problem Mentions
Get comprehensive debugging context:Types of Terminal Output
Build Output
- Compilation results
- Bundling information
- Asset generation
- Error messages
Test Results
- Test suite execution
- Pass/fail status
- Coverage reports
- Performance metrics
Package Management
- Installation logs
- Dependency resolution
- Version conflicts
- Registry issues
Git Operations
- Commit messages
- Merge conflicts
- Branch operations
- Push/pull results
Development Servers
- Server startup logs
- Request/response info
- Error messages
- Performance data
Common Terminal Scenarios
Build Failures
Test Debugging
Installation Problems
Server Issues
Git Conflicts
Tips for Effective Terminal Mentions
- Capture immediately: Use
@terminalright after seeing errors - Include context: Mention what you were trying to do
- Show the command: Include the command that caused the issue
- Be specific: Ask about particular error messages
- Combine mentions: Use with relevant file or folder mentions
Integration with Memory Bank
Terminal mentions help Elastic learn:- Common commands: Your frequently used terminal commands
- Error patterns: Recurring issues and their solutions
- Development workflow: How you use the terminal
- Environment setup: Your development environment preferences
Advanced Use Cases
Debugging Complex Builds
Performance Analysis
Environment Issues
Deployment Problems
Database Operations
Combining with Other Mentions
With File Mentions
With Folder Mentions
With Problem Mentions
With Git Mentions
Terminal Output Limitations
Output Length
- Very long output might be truncated
- Elastic focuses on the most recent and relevant lines
- Ask for specific parts if needed
Binary Output
- Non-text output is typically excluded
- Binary files and data are filtered out
- Focus on text-based terminal output
Sensitive Information
- Be careful with terminal output containing:
- API keys or passwords
- Personal information
- Internal system details
Troubleshooting Terminal Mentions
No Terminal Output
If@terminal shows nothing:
- Make sure you’ve run commands recently
- Check if the terminal is active
- Try running a simple command first
- Verify terminal integration is working
Incomplete Output
If output seems truncated:- Ask for specific error messages
- Use file mentions to show relevant code
- Break down complex issues into smaller parts
- Focus on the most critical error lines
Formatting Issues
If formatting is lost:- Mention specific error codes or messages
- Describe what you were trying to do
- Use quotes around specific error text
- Ask Elastic to focus on particular lines