Get Unstuck
Troubleshooting
Quick checks for missing projects, sessions, approvals, analytics, and Quick Agent responses.
A project is missing
- Open the Project menu and choose Add Project….
- Confirm the folder still exists and your macOS account can read it.
- If the project was discovered from an agent session, run that CLI once inside the project and refresh AskTerminal.
Sessions are missing
- Confirm you selected the project where the session actually ran.
- Choose refresh in the project header.
- Verify the relevant CLI is installed, signed in, and can show its own session history.
- For Codex, wait for an active CLI process to finish writing, then refresh.
A session will not resume
- Try resuming the same session directly in its CLI to verify it still exists.
- Check the terminal output for authentication or command errors.
- Start a new session if the original history was deleted or moved.
Approvals do not appear
- Open Settings → Hooks.
- Check the status for the engine you are using.
- Choose Install / Update.
- Quit and reopen AskTerminal, then start a fresh CLI session.
Quick Agent does not open or answer
- Press
Command-Kwhile AskTerminal is active. - Check the engine and workspace under Settings → General.
- Confirm that engine works in a normal terminal.
- Clear the remembered session for that engine if its context is stale.
Analytics is empty
- Select a project with recorded Claude Code or Codex sessions.
- Refresh the project after completing a session.
- Remember that older or partial transcripts may not contain tokens, timestamps, or tool details.
A terminal is stuck
Press Control-C once and wait for the process to stop. If the shell has exited, open a new terminal. Before repeating a failed operation, read the final error lines and confirm the working directory.
Still stuck? Record the app version, macOS version, selected engine, what you expected, and the exact visible error. Avoid sharing API keys, full credentials, or private source code in a support report.