> For the complete documentation index, see [llms.txt](https://docs.zenml.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenml.io/kitaru/get-help/troubleshooting.md). # Troubleshooting Diagnose connection, worker, and replay problems. Most problems are one of three things: the client can't reach the server, no worker is claiming the work, or the replayed subprocess is missing something from its environment. Work down the chain. ## Start with the diagnostics ```bash kitaru status # who am I, which server, which context kitaru doctor # connection and environment checks kitaru version ``` The CLI and SDK read `KITARU_API_URL` and `KITARU_API_KEY` from the environment; `kitaru login` stores credentials per server context (`kitaru context list` shows them). When a script fails with `KITARU_API_URL is not set`, it's the environment, not the server. ## Nothing is happening A replay, import, or evaluation that sits in `pending` almost always means **no worker is claiming it**: * Is a worker running? `kitaru worker list` shows workers and liveness. * Can this worker claim this task? A worker started with `--claim` or `--selector` skips tasks outside its scope; a bare `kitaru worker start` claims anything except an API import or analyzer that needs provider credentials from the worker's environment, which only a worker started with `--selector kitaru/requires-credentials=` claims. * Watch the job directly: `kitaru job watch ` shows tasks moving through `pending → claimed → running`. ## A replay fails `kitaru job get ` carries the failing task's error and a tail of the subprocess's stderr. The usual suspects: * **The agent version has no run command:** register it with `--command`; that command is what the worker executes. * **Missing dependencies or keys:** the subprocess runs in the worker's environment. Start the worker in the same virtualenv as your agent, with the provider keys exported. * **A tool call missed under `on_miss="fail"`:** the fork took a path the recording doesn't answer. See [Tool policies](/kitaru/guides/tool-policies.md) for the options. ## The server The server's health endpoint is `GET /health`; Docker Compose users can check `docker compose ps` and `docker compose logs server`. The interactive API reference lives at `/docs` on your server. ## Get help Still stuck? All three of these reach a human: * [Slack community](https://kitaru.ai/slack) for questions and quick pointers. * [kitaru.ai/help](https://kitaru.ai/help) to report a bug; it goes straight to GitHub issues. Attach the session or job ID and the failing command's output, and it gets fixed fastest. * when email is easier. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.zenml.io/kitaru/get-help/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.