Troubleshooting

Start with kaibo doctor. It checks the address, that the server answers, and that your key works, then says what to do next.

You see	It means	Do this
`no address`	The client does not know where kaibo is	Set `KAIBO_URL` to the address you open the dashboard at, or run `kaibo login --url <address>`
`no api key`	No key was given	Create one on the dashboard's projects page, then `kaibo login` or set `KAIBO_KEY`
`could not reach <address>`	Nothing answered	Check the address has no typo and the server is up. Behind a proxy or tunnel, check it forwards `/v1`
401 `unauthenticated`	The key is wrong, revoked or expired	Make a new key. Playground keys last an hour
403 `forbidden`	The key lacks a scope	`forget` needs the `forget` scope. Projects, keys and webhooks need `admin`
403 on `projects create` or `delete`	The key is bound to one project	Use an organization-wide admin key
404 `not_found` on a project id	Wrong id, or another organization's	`kaibo projects` lists yours
409 `conflict` editing a memory	It was already replaced	Recall again and edit the current one
429 `rate_limited`	Too many requests	The SDKs retry using `Retry-After`. Slow down batch jobs
Recall says `no memory matches`	Nothing citable matched	This is the correct answer when memory has nothing. Check the question against `kaibo memories`
Recall returns an old fact, or a memory id stopped working	The newer statement has not been structured yet, or a provisional memory was replaced by the structured one (new id)	Structuring takes a few seconds. `remember(..., { wait: true })` waits for it; do that before you keep ids
A fact is marked unverified	Past its half-life without confirmation	Check it, then `kaibo.verifyMemory(item)` to restart the clock

Webhooks do not arrive

The endpoint must be a public https address. Localhost is rejected. Use a tunnel while developing.
Open the endpoint's delivery log (dashboard, or kaibo webhooks deliveries <id>). It shows the status and your server's response.
Press send test. If the test arrives and real events do not, check the events you subscribed to.
Verification fails: use the raw request body, the right secret, and a server clock within five minutes.

The agent does not see the MCP tools

Restart the agent after adding the server.
Claude Code: run /mcp and check kaibo is connected. Cursor: enable it under Settings, MCP.
Stdio setups (Claude Desktop, Codex) run the kaibo command, so it must be installed and on the PATH the app uses.
Check the key with kaibo doctor in a terminal that has the same environment.