Configuration and troubleshooting.

#Configuration

Kaitoi Code has an optional JSON config file for defaults: provider, model, command limits, Runtime host, port and autostart, output style, and extra local-file deny patterns.

Create it from inside Code:

/config init

Code prints the new file's location. Edit that file to change defaults for future sessions. To see what is currently loaded:

/config

/provider, /model and /commands change the current session only. They do not rewrite the config file behind your back.

#kaitoi command not found

Restart your terminal after installation, then try again. On Linux, make sure the AppImage is executable.

On Windows, close every terminal window after installing or upgrading. If an old version still opens, check which binary is first in PATH:

where.exe kaitoi
Get-Command kaitoi -All

#Code says it is not logged in

kaitoi connect login

Then restart kaitoi code.

#Runtime is not running

Start it from the dashboard, or:

kaitoi runtime serve

To let Code start Runtime itself when a recipe tool needs it, create the config with /config init, then set runtime.autoStart to true in that file.

#Kaitoi Studio does not show an installed recipe

Check each layer in order:

kaitoi runtime packages
kaitoi status

Then open Settings → Integrations → Runtime, refresh the connection, and confirm the Runtime URL matches the one Kaitoi Connect reports. If you generated a recipe but never installed it, install it first:

kaitoi runtime install ./my-recipe.yaml

#A download link fails

Open the latest release and confirm the installer asset exists:

github.com/kaitoi-labs/kaitoi-cli/releases/latest