CLI troubleshooting

Common problems

No profile found

Run:

convoy config show
convoy config list

Then either pass --profile explicitly or add the current directory to the right profile with convoy paths add.

Authentication failed

Check that the API key is valid for the target deployment and that the user still has access to the project.

`connect` starts but threads do not run

Check:

the selected profile points at the correct project
a supported runtime is installed locally
the thread is targeting a compatible CLI type

Claude CLI not found

Install Claude Code locally before using live thread execution with the Claude runtime.

Config files look wrong

Re-run:

convoy init mcp --force

or inspect the generated config file before overwriting it.

A managed container or service stopped

Start with convoy env status --env dev on your host. Read saved operational logs with convoy service logs --env dev, without --follow. This works when the service stopped but the container remains running. See Diagnose a stopped service for recent-log commands, retention and the stopped-container limitation.