Skip to main content
Kilo CLI is a fork of OpenCode , so both connect to Fortytwo the same way. Only the commands and the config file differ.
Before you start: create a Fortytwo API key and buy credits — see Quickstart, step 1. Give each agent its own key with a Spend limit.
1

Install Kilo CLI

2

Add Fortytwo to the config

Open ~/.config/kilo/kilo.jsonc and add the fortytwo provider. For a new file:
~ is your home folder. Folders that start with a dot, such as .pi, .config or .codex, are hidden. To show them: Cmd+Shift+. in Finder on macOS, View → Show → Hidden items in File Explorer on Windows, Ctrl+H in most Linux file managers.
~/.config/kilo/kilo.jsonc
If the file has other settings, add fortytwo inside its provider object. If you set up Kilo Code in VS Code, Fortytwo is already in this file: skip this step.
3

Connect Fortytwo

  1. Start Kilo in your project folder:
  1. Type /connect, search for Fortytwo and select it. Kilo CLI: Fortytwo in the Connect a provider list
  2. Paste your API key and press Enter. The field shows the key as plain text, so do not share your screen at this moment.
  3. Kilo opens the model list. Choose Qwen3.8 27B. Kilo CLI: Qwen3.8 27B under Fortytwo
  4. In Select variant, choose medium to turn on reasoning. The prompt shows Qwen3.8 27B Fortytwo · medium. Kilo CLI: Select variant with medium selected
4

Start a task

Type a task and press Enter. Kilo may ask before it runs a command; choose Allow once or Allow always. To change the model later, type /models; to change the reasoning level, type /variants.Kilo CLI: task done on Qwen3.8 27B Fortytwo with variant medium
The model ID inside these tools is fortytwo/qwen/qwen3.8-27b: the provider ID, then the Fortytwo model ID. More options: Kilo custom models , OpenCode custom provider .
Something not working with your agent, or using one we have not listed? Tell us in the platform: Feedback for ideas and small bugs, Contact support if it blocks your work, or Report a security issue.
Last modified on October 26, 2026