Fix Terminal.app Crashing or Not Opening on macOS

What Causes This Issue

Terminal.app failures on macOS typically stem from corrupted preference files, broken shell configurations, or system permission errors. Users in the Apple Support Community report this problem across macOS Sonoma and Sequoia, often after system updates or third-party shell installations. The Terminal.app binary itself rarely breaks; instead, launch daemons, plist files, or shell initialization scripts trigger crashes on startup.

Common triggers include a malformed .zshrc or .bash_profile, a damaged com.apple.Terminal.plist, or Full Disk Access restrictions blocking the app from reading required directories. In some cases, a stuck WindowServer session or corrupted saved window state prevents the main window from rendering.

Step-by-Step Fixes

1. Delete the Terminal preference file — This is the most reliable fix reported by users in the Apple Support Community. Close Terminal, open Finder, press Command+Shift+G, paste ~/Library/Preferences/, locate com.apple.Terminal.plist, move it to Trash, then relaunch Terminal. A fresh plist regenerates with defaults.
2. Clear saved window state — If Terminal opens but shows no window or freezes, the saved state may be corrupt. In Finder, go to ~/Library/Saved Application State/, find com.apple.Terminal.savedState/, delete the folder, then restart Terminal.
3. Verify shell configuration files — A syntax error in .zshrc, .zprofile, or .bash_profile crashes the shell on launch. Boot into Safe Mode (hold Shift at startup), open Terminal, and rename suspect files: mv ~/.zshrc ~/.zshrc.bak. Test launch. If fixed, edit the backup to isolate the bad line.
4. Grant Full Disk Access to Terminal — Open System Settings → Privacy & Security → Full Disk Access. Ensure Terminal.app is listed and enabled. If missing, click the + button, press Command+Shift+G, navigate to /System/Applications/Utilities/Terminal.app, and add it.
5. Reset Terminal to factory defaults via command line — If you can open a shell via another method (SSH, another terminal emulator), run: defaults delete com.apple.Terminal then killall cfprefsd. This wipes all custom profiles, window groups, and keyboard mappings.
6. Reinstall Terminal using macOS Recovery — As a last resort before reinstalling macOS, boot into macOS Recovery (hold Command+R on Intel, hold Power on Apple Silicon), open Terminal from the Utilities menu, and run: csrutil disable (if SIP blocks), then copy a clean Terminal.app from the recovery image to /System/Applications/Utilities/. Re-enable SIP after.

Additional Solutions

Create a new user account — Test if the issue is user-specific. In System Settings → Users & Groups, add a test account, log in, and launch Terminal. If it works, the problem lives in your user library.

Check for third-party kernel extensions — Some security tools or virtualization software install kexts that interfere with pseudo-terminal allocation. Run kextstat | grep -v com.apple in a working shell to list non-Apple kexts. Uninstall suspect vendors.

Repair disk permissions via Disk Utility — While modern macOS manages permissions automatically, First Aid on the startup volume can resolve underlying filesystem inconsistencies affecting app launches.

Disable WindowServer hardware acceleration — Some users in the Apple Support Community found that toggling defaults write com.apple.WindowServer CWMetalForceNoAccel -bool true and rebooting resolved blank Terminal windows on certain GPU configurations.

Use an alternative terminal temporarily — Install iTerm2, Alacritty, or WezTerm via Homebrew (brew install --cask iterm2) to maintain workflow while troubleshooting the native app.

When to Contact Apple Support

Open a support case if:

• Terminal fails on a brand-new user account with default settings
• Console.app shows repeated com.apple.Terminal crash logs citing dyld or libsystem errors
• The app bundle at /System/Applications/Utilities/Terminal.app shows modified timestamps or missing Info.plist
• Multiple system utilities (Activity Monitor, Console, Disk Utility) also fail to launch

Bring the system diagnostics (run sudo sysdiagnose in a working shell) and any crash reports from ~/Library/Logs/DiagnosticReports/.

FAQ

Why does Terminal open then immediately close?
This almost always indicates a shell startup script error. The app launches, spawns your login shell, the shell hits a syntax error or failed command in .zshrc, exits, and Terminal closes the window. Fix the script or rename it as described in step 3.

Can I fix this without losing my custom profiles?
Yes. Before deleting com.apple.Terminal.plist, export your profiles: Terminal → Settings → Profiles → gear icon → Export Profiles. Save the .terminal file, then re-import after the reset.

Does reinstalling macOS fix Terminal?
A clean install resolves it, but an in-place upgrade (reinstalling macOS from Recovery without erasing) often repairs system binaries and permissions while preserving data. Try that first.

Is this related to the WorldTUI project discussed online?
No. WorldTUI is an independent terminal UI library. The issue here affects Apple’s native Terminal.app and is unrelated to third-party terminal emulators or AI-trained terminal models.

Why do my Terminal tabs show “Process completed” and won’t run commands?
The shell exited immediately. Check Settings → Profiles → Shell → Startup → Run command — ensure it’s set to /bin/zsh (or your preferred shell) and Run inside shell is unchecked unless intentional.