Troubleshooting
import { Aside } from ‘@astrojs/starlight/components’;
Installation Issues
Section titled “Installation Issues””The Terminal” is damaged and can’t be opened
Section titled “”The Terminal” is damaged and can’t be opened”This is a macOS Gatekeeper message. The Terminal is Apple Notarized, so this shouldn’t happen, but if it does:
- Right-click the app in Applications
- Select Open from the context menu
- Click Open in the dialog
Alternatively, run:
xattr -cr /Applications/The\ Terminal.appApp doesn’t launch
Section titled “App doesn’t launch”Check Console.app for crash logs:
open -g /Applications/Utilities/Console.appLook for entries from “The Terminal” in the crash reporter.
Terminal Issues
Section titled “Terminal Issues”Shell not loading properly
Section titled “Shell not loading properly”The Terminal uses your login shell by default. If your shell isn’t loading:
- Check your default shell:
echo $SHELL - Verify the shell path exists:
which zshorwhich bash - Check Settings > Terminal > Default Shell
Colors look wrong
Section titled “Colors look wrong”If ANSI colors don’t match your expectations:
- Verify your
TERMenvironment variable:echo $TERM - Try changing the theme in Settings > Appearance
- Check if your
.zshrc/.bashrcforces a specificTERMvalue
Slow terminal performance
Section titled “Slow terminal performance”If the terminal feels sluggish:
- Reduce scrollback buffer: Settings > Terminal > Scrollback Lines (try 5000)
- Check for processes producing excessive output (
toporhtop) - Close unused terminal panels
Browser Issues
Section titled “Browser Issues”Browser panel shows blank page
Section titled “Browser panel shows blank page”- Check the URL bar — make sure the URL is correct
- Try navigating to a known-working URL like
https://example.com - If local dev server: verify the server is running and the port is correct
DevTools API not connecting
Section titled “DevTools API not connecting”If Gee-Code can’t connect to the browser panel:
- Check if the config file exists:
cat ~/.the-terminal/devtools.json - Verify the port is accessible:
curl http://localhost:9876 - Restart The Terminal — the DevTools server starts on launch
Web app not updating after code changes
Section titled “Web app not updating after code changes”If hot reload isn’t reflected in the browser panel:
- Click the reload button in the browser panel
- Check the dev server terminal for errors
- Hard refresh: hold
Shiftand click reload
File Navigator Issues
Section titled “File Navigator Issues”Files not showing
Section titled “Files not showing”- Check if dotfiles are hidden: Settings > File Navigator > Show Dotfiles
- Verify the directory path is correct
- Check file permissions
Git status not updating
Section titled “Git status not updating”The file navigator polls for git status changes. If colors seem stale:
- Wait a few seconds for the next poll
- Click another directory and back to force a refresh
- Check that the directory is inside a git repository
Performance Issues
Section titled “Performance Issues”High memory usage
Section titled “High memory usage”If The Terminal is using more than expected memory:
- Close unused panels (especially multiple browser panels)
- Reduce terminal scrollback buffer
- Close unused Spaces
- Restart The Terminal to clear any accumulated state
High CPU usage
Section titled “High CPU usage”- Check for runaway processes in terminal panels
- Disable background git fetch if not needed
- Close the Observability panel if monitoring is intensive
Updating
Section titled “Updating”Auto-update not working
Section titled “Auto-update not working”- Check Settings > Workspace > Auto-Update is enabled
- Verify network connectivity
- Manually download the latest DMG from the website
Getting Help
Section titled “Getting Help”If you’re stuck:
- Check the Gee-Code community for known issues
- Include your Terminal version, macOS version, and steps to reproduce
Next Steps
Section titled “Next Steps”- System Requirements — verify your setup
- Settings — adjust configuration