Solutions to common issues, error messages, and optimization tips for Agentastic. If you can't find your issue here, visit our community forum.
Quick Fixes
Before diving into specific issues, try these general solutions:
- Restart Agentastic - Quit completely and relaunch
- Check Permissions - System Settings → Privacy & Security
- Update to Latest - Check for updates in Settings
- Clear Cache - Settings → Advanced → Clear Cache
- Reset Settings - Hold
⌥while launching
Installation Issues
"Agentastic can't be opened because it is from an unidentified developer"
Solution:
- Right-click the Agentastic app in Applications
- Select "Open" from the context menu
- Click "Open" in the dialog
- This only needs to be done once
App Won't Launch
Check these:
- macOS version 12.0 or later
- At least 2GB free RAM
- No conflicting apps running
- Check Activity Monitor for stuck processes
Fix:
# Kill any stuck processes
pkill -f agentastic
# Clear launch services
/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
# Try launching again
open -a Agentastic
Menu Bar Icon Missing
Solutions:
- Check if hidden in menu bar (drag to reveal)
- Restart Agentastic
- Reset menu bar:
defaults delete com.agentastic.app NSStatusItem - Check Bartender or similar apps
Permission Issues
Accessibility Permission Not Working
Symptoms:
- Expansions don't trigger
- Keyboard shortcuts don't work
- "Accessibility access required" error
Fix:
- System Settings → Privacy & Security → Accessibility
- Remove Agentastic if present (click
-) - Re-add Agentastic (click
+) - Ensure toggle is ON
- Restart your Mac
Screen Recording Permission
Symptoms:
- Vision mode not working
/screencommands fail- Black screenshots
Fix:
- System Settings → Privacy & Security → Screen Recording
- Toggle Agentastic ON
- Quit and restart Agentastic
- Test with
/screen What do you see?
Note: Vision mode and screen capture features require macOS 14.0 (Sonoma) or later. On macOS 12-13, these features will be disabled.
File Access Issues
Symptoms:
/filescommands fail- "Permission denied" errors
- Can't read/write files
Fix:
- System Settings → Privacy & Security → Files and Folders
- Grant access to needed folders
- Or use Full Disk Access (not recommended)
Expansion Problems
Expansions Not Working
Check:
- Expansion is enabled in settings
- Correct trigger typed
- Followed by space (or configured delimiter)
- Not in excluded app
Debug:
# Check if expansions are loading
agentastic debug expansions
# Test specific expansion
agentastic test "your_trigger"
Unwanted Expansions
Solutions:
- Make trigger more unique
- Enable word boundaries
- Add app to exclusion list
- Use case sensitivity
Example fix:
expansions:
problematic_trigger:
old: "im"
new: ";im" # Add prefix
case_sensitive: true
word_boundaries: true
Expansion in Wrong App
Fix app-specific settings:
apps:
Terminal:
expansions_enabled: false
Xcode:
trigger_key: "tab"
Mail:
auto_capitalize: true
Pattern Matching Issues with Arrow Keys
Symptoms:
- Patterns like
[]or[text]don't trigger after using arrow keys - Expansions fail when editing text mid-word
- Matching resets when navigating
Solution - Enable Cursor-Aware Matching:
# In your config file
enable_cursor_aware_matching: true
What this fixes:
- Maintains pattern state through arrow key navigation
- Allows editing within patterns without breaking detection
- Preserves matching buffer when moving cursor
Debug cursor-aware issues:
# Check if feature is enabled
agentastic config show | grep cursor_aware
# View matching behavior in logs
agentastic log | grep cursor-aware
# Test with specific pattern
agentastic test "[hello]" --cursor-aware
Note: This is an experimental feature. Disable if experiencing unexpected matching behavior.
AI Features Issues
Slow AI Responses
Optimize:
-
Use appropriate model:
/model:fastfor simple tasks/model:smartfor general use/model:geniusonly when needed
-
Check internet speed:
# Test connection ping -c 5 api.agentastic.com -
Clear AI cache:
- Settings → Advanced → Clear AI Cache
AI Not Working
Troubleshoot:
- Check internet connection
- Verify API status: status.agentastic.com
- Test with simple prompt:
@ai Hello - Check firewall/proxy settings
Vision Mode Issues
Common problems:
- Black screen: Grant screen recording permission
- Wrong monitor: Use
/screen:1or/screen:2 - Partial capture: Check display scaling
- Performance: Disable when not needed
Launcher Issues
Launcher Won't Open
Try:
- Check keyboard shortcut conflicts
- Reset launcher shortcut:
defaults write com.agentastic.app launcherShortcut "cmd+space" - Check if another app is intercepting
Launcher Appears Behind Windows
Fix:
defaults write com.agentastic.app launcherLevel "floating"
Options: normal, floating, screen-saver
Launcher Position Issues
Reset position:
defaults delete com.agentastic.app launcherPosition
Or drag to preferred location and it will remember.
Conversation Loading Issues
Bookmarked conversation doesn't load:
- Verify conversation was bookmarked successfully (check Settings → Bookmarks)
- Ensure conversation file isn't corrupted
- Try loading a different conversation to test the feature
- Restart both Settings app and launcher
Conversation appears empty after loading:
- Check that the conversation has actual message content
- Wait a moment for the conversation to fully load
- Try closing and reopening the launcher
- Clear conversation cache in Settings
"Load" button doesn't work:
- Ensure launcher is not already running with a conversation
- Check for permission issues
- Try using keyboard shortcut
⌘+Sto bookmark, then load again - Restart the Settings app
Text Selection Popup Issues
Multiple Popups Appearing
Symptoms:
- Two or more purple popup buttons visible simultaneously
- New popup appears before old one disappears
- Popups overlapping or cluttering the screen
Solution: This issue has been fixed in the latest version. The system now ensures only one popup appears at a time. If you're still experiencing this:
- Update to the latest version of Agentastic
- Ensure
enable_text_selection_timer_monitoringis set tofalse(default) in your config - Restart the launcher
Text Selection Popup Not Appearing
Common causes and fixes:
1. Feature is disabled:
- Open Settings → General settings
- Enable "Text Selection Popup" toggle
- Or add to config:
show_agentastic_shortcut: true
2. Mouse selection not detected:
- Some applications may not trigger mouse selection events properly
- As a last resort, enable timer monitoring in config:
enable_text_selection_timer_monitoring: true # Use with caution - Note: Timer monitoring may cause duplicate popups
3. Accessibility permissions:
- System Settings → Privacy & Security → Accessibility
- Ensure Agentastic is enabled
- Remove and re-add if already present
Popup Appears in Wrong Position
Fix positioning issues:
- Check multi-monitor setup and display arrangement
- Verify display scaling settings
- Reset popup position:
defaults delete com.agentastic.app popupPosition
Popup Disappears Too Quickly
Adjust auto-hide timer: The popup auto-hides after 3 seconds by default. This is not currently configurable but will remain visible if you hover over it.
Memory System Issues
Memory Not Saving
Check:
- Memory enabled in settings
- Channel configured correctly
- Sufficient disk space
- Write permissions
Debug:
# Check memory status
agentastic memory status
# Test memory write
agentastic memory test
Wrong Channel Assignment
Fix routing:
channels:
work:
keywords: ["project", "meeting", "deadline"]
priority: 10 # Higher priority
personal:
keywords: ["home", "family"]
priority: 5
Performance Optimization
High CPU Usage
Reduce load:
- Limit active expansions (<500 recommended)
- Disable unused features
- Reduce AI cache size
- Lower thread pool size
Settings:
performance:
max_expansions: 500
ai_cache_size: "50MB"
thread_pool: 2
idle_timeout: 300
High Memory Usage
Solutions:
- Archive old memory channels
- Clear expansion cache
- Reduce history size
- Restart periodically
Slow Typing
Fix input lag:
- Disable complex expansions
- Reduce middleware pipeline
- Check for app conflicts
- Update to latest version
Error Messages
"API Rate Limit Exceeded"
Meaning: Too many AI requests Fix:
- Wait 60 seconds
- Use
/model:fastmore - Enable smart caching
"Expansion Loop Detected"
Meaning: Expansion triggers itself Fix:
- Change trigger
- Disable recursive expansion
- Add loop protection
"Memory Channel Full"
Meaning: Channel storage limit reached Fix:
- Archive old memories
- Increase retention limit
"Cannot modify protected content" Error
Meaning: The AI attempted to modify content within <permanent_instruction> tags
What happened: The AI tried to edit or delete a section of memory that you've protected with permanent instruction tags.
What to do:
- This is expected behavior - the protection is working correctly
- The protected content has been preserved unchanged
- The AI will learn from this error and avoid modifying that section in future
- If you want the AI to update this content, you must manually edit the memory file and remove or update the
<permanent_instruction>tags
Example error message:
Cannot modify or remove content within <permanent_instruction> tags.
The following protected content is missing or modified:
<permanent_instruction>
Always be encouraging when discussing fitness...
</permanent_instruction>
Please make edits that preserve all permanent instructions.
How to fix:
- Open the memory file directly in a text editor
- Remove the
<permanent_instruction>tags if you want the AI to edit that content - Or manually update the content yourself while keeping the tags
- Save the file
Preventing this error:
- Only use permanent instruction tags for truly critical, unchanging directives
- Place frequently-updated information outside protected tags
- Review protected content occasionally to ensure it's still relevant
"Cannot modify user.md" Error
Meaning: The AI attempted to edit the user.md file
What happened:
The user.md file is completely read-only for the AI - it cannot be modified under any circumstances.
What to do:
- This is expected behavior - user.md is protected for your safety
- If you want to update user.md, edit it manually
- File location:
~/Library/Application Support/agentastic/memory/user.md(macOS)
Why user.md is protected:
- Contains your core preferences and instructions
- Should only be modified intentionally by you
- Prevents accidental overwrites of critical information
- Create new channel
"Permission Denied: [Feature]"
Meaning: Missing system permission Fix: Grant permission in System Settings
Advanced Debugging
Enable Debug Mode
# Start with debug logging
agentastic --debug
# Or set in config
echo "debug: true" >> ~/.config/agentastic/config.yaml
View Logs
# Live log viewing
agentastic log -f
# Filter by component
agentastic log --filter="expansion"
# Export logs
agentastic log export > debug.log
Performance Profiling
# Profile expansions
agentastic profile expansions
# Profile AI requests
agentastic profile ai
# System resource usage
agentastic stats
Reset and Recovery
Reset Specific Components
# Reset expansions
agentastic reset expansions
# Reset AI cache
agentastic reset ai-cache
# Reset memory
agentastic reset memory
# Reset everything
agentastic reset all
Backup and Restore
# Backup all data
agentastic backup create
# Restore from backup
agentastic backup restore "backup-2024-01-15.zip"
# List backups
agentastic backup list
Getting Help
Before Contacting Support
- Check this guide
- Search community forum
- Update to latest version
- Collect debug logs
Information to Provide
- Agentastic version
- macOS version
- Error messages
- Steps to reproduce
- Debug logs
Contact Options
- Forum: community.agentastic.com
- Email: support@agentastic.com
- GitHub: github.com/agentastic/issues
Prevention Tips
Regular Maintenance
- Weekly: Clear cache, review expansions
- Monthly: Archive memories, check permissions
- Quarterly: Review settings, update
Best Practices
- Keep expansions under 1000
- Use appropriate AI models
- Regular backups
- Monitor resource usage
- Update promptly
Remember: Most issues have simple solutions. Start with quick fixes before diving into advanced troubleshooting!