Troubleshooting

Start with the guide for the surface you're using. Each one explains where logs live and how to recover.

CLICopy Anchor Link

Check what Hull has loaded and where it keeps its files:

hull debug config   # the resolved configuration
hull debug paths    # config, data, cache and state directories
hull auth list      # connected providers and provider environment variables

To see logs as Hull runs, start it with --print-logs, and add --log-level DEBUG for more detail:

hull --print-logs --log-level DEBUG

Common problemsCopy Anchor Link

Hull asks me to sign in again, or models are missingCopy Anchor Link

Your sign-in may have expired, or you may be working in a different account from the one with your plan. Sign in again (see Sign in) and check you're on the right personal or organization account.

My project's instructions or config aren't usedCopy Anchor Link

Project files only load when the project is trusted. In the CLI, run hull trust in the project. In VS Code, trust the workspace. Then start a new session. See Settings.

A tool fails with a sandbox errorCopy Anchor Link

When the sandbox is on, tools can't write outside the workspace or reach the network unless you allow it. Hull refuses to run a tool if it can't enforce the sandbox, rather than running it unprotected. See Sandboxing.

The CLI crashes with "Illegal instruction"Copy Anchor Link

Your CPU doesn't support AVX. Reinstall with curl -fsSL https://withhull.com/cli/install | bash, which picks the baseline build automatically.

Contact supportCopy Anchor Link

Email support@withhull.com. Include your platform, the Hull version (hull --version, or About in the app or extension), what you expected, what happened, and any relevant log output. Remove secrets such as API keys before you send logs.