Skip to content

DocsCoding agents

Coding agents

Run terminal coding agents on your own GPU. Which API each agent speaks, where its configuration lives and which model to use.

Coding agents read your files, run commands and edit code in a loop, sending many requests with tool calls. On Osarai they all run on your own instance, so a long session costs the same hourly price as a short one.

Before you start

  1. A Ready instance running a model with tool calls, for example qwen3.8-27b (Quickstart).
  2. An API key in your shell:
Terminal
export OSARAI_API_KEY="qck_your_key_here"

To keep it in new terminals, add the line to ~/.zshrc or ~/.bashrc (on Windows: setx OSARAI_API_KEY "qck_your_key_here").

Compatibility

AgentAPI it usesConfigurationTested with
opencodeChat Completionsopencode.jsonopencode 1.19
Claude CodeAnthropic MessagesEnvironment or ~/.claude/settings.jsonClaude Code 2.1
Codex CLIResponses~/.codex/config.tomlCodex CLI 0.167
CrushChat Completionscrush.json or crushrcCrush 0.100
Qwen CodeChat CompletionsEnvironment or ~/.qwen/.envQwen Code 0.27
AiderChat CompletionsEnvironment or .aider.conf.ymlAider 0.86
GooseChat Completionscustom_providers/osarai.jsonFrom goose's docs, not run by us
Kilo Code CLIChat Completions~/.config/kilo/kilo.jsonKilo CLI 7.8
Continue CLIChat Completions~/.continue/config.yamlContinue CLI 1.5

Editors work the same way: see Cline, Roo Code, Continue and Zed.

What every setup has in common

SettingValue
Base URL (OpenAI format)https://osarai.xyz/v1
Base URL (Anthropic format)https://osarai.xyz
API keyyour qck_… key
Modelthe id on your instance page, for example qwen3.8-27b
Context window131072 for qwen3.8-27b on an RTX 5090 (all models)

Tips for long sessions

  • Tell the agent the real context window (each guide shows where), so it compacts before the model runs out of room.
  • Lower reasoning effort (low) for quick edits and raise it for planning; see reasoning effort.
  • Agents that run commands ask before doing so; review what they want to run.