Qoder

Before you start

Install the named client using its official instructions. Pi here means the pi-mono coding agent; Hermes means Nous Research's Hermes Agent.

Once your Inferway account is activated, create a key under Console → API Keys. Use a dedicated key for this client; a project's monthly budget caps what it can spend. Both live and test prefixes use the same inference and billing path; test is an environment label, not a free or simulated inference mode.

Use an Inferway key for Inferway's endpoint. An OpenRouter key belongs to OpenRouter and cannot authenticate to this address.

Keep the key in the client's credential store or your local environment. Do not paste it into a prompt, screenshot, or committed configuration. These examples use bash/zsh on macOS or Linux.

Why this page has no configuration

Qoder IDE's custom models only offer a fixed list of vendors — there is no custom Base URL field — so it cannot point at Inferway.

We tested the Qoder CLI on 2026-09-28 and it does not work with Inferway today. A custom model added through the CLI's model settings is not called from your machine: the request goes through Qoder's servers, which failed to set up the custom model (error 100400), and nothing reached Inferway.

One earlier CLI build did call Inferway directly through a custom provider entry and got a correct reply, but the CLI updated itself during the test and the updated build no longer loads that entry. Because the client updates silently, we do not publish a recipe that could stop working on its own.

As the CLI implements it today, adding a bring-your-own-key model makes the client send the API key you entered, together with the Base URL, to Qoder's servers (/algo/api/v2/byok/config) for validation. Keep that in mind before pasting a key in.

We will test again when Qoder changes how custom models are called; until then, use another client from this list.