Troubleshooting
Start by checking the installed build and enabling logs:
caretz --version
caretz -v -p "hello" # runtime decisions and tool activity
caretz -vv -p "hello" # debug detail
Without -v, -p prints only the final answer, as raw text on stdout, so it
pipes cleanly into other tools; errors still go to stderr. -v and -vv add
the model, request, and tool activity on stderr.
Sandbox errors on a specific platform are covered in Linux and macOS .
In this section
Model and connection errorsNo model selected, 404s, auth errors, failed setup tests.
Missing tools and web searchA tool isn't available, or WebSearch doesn't work.
Sandbox errorsPermission denied, blocked network, and disabling the sandbox.
Skills and sessionsSkills or agents not found, sessions that won't reopen.
Terminal and ACPKeyboard input, interruption, and Zed/ACP setup.