Free tier available — 500K tokens/month, no credit card required.See Plans →
IDE Setup

STOP COUNTING TOKENS.
START BUILDING AGENTS.

Use Qlaw as your private Copilot replacement in VS Code. Zero telemetry, full control, your infrastructure.

1CONTINUE.DEV

Continue is an open-source AI code assistant extension for VS Code and JetBrains. It supports any OpenAI-compatible API, making it perfect for Qlaw.

  1. Install the Continue extension from VS Code marketplace
  2. Open your Continue config: ~/.continue/config.json
  3. Replace the contents with the config below
  4. Replace ql_YOUR_API_KEY with your actual key from the dashboard
// .continue/config.json
{
  "models": [
    {
      "title": "Qlaw Orchestrator",
      "provider": "openai",
      "model": "qlaw-orchestrator",
      "apiBase": "https://api.qlawai.com/v1",
      "apiKey": "ql_YOUR_API_KEY"
    }
  ],
  "tabAutocompleteModel": {
    "title": "Qlaw Orchestrator",
    "provider": "openai",
    "model": "qlaw-orchestrator",
    "apiBase": "https://api.qlawai.com/v1",
    "apiKey": "ql_YOUR_API_KEY"
  }
}
2TWINNY

Twinny is a lightweight VS Code extension for AI autocomplete. It supports OpenAI-compatible endpoints natively.

  1. Install Twinny from the VS Code marketplace
  2. Open VS Code settings (JSON) and add the config below
  3. Replace ql_YOUR_API_KEY with your actual key
// VS Code settings.json (Twinny extension)
{
  "twinny.provider": "openai-compatible",
  "twinny.apiUrl": "https://api.qlawai.com/v1/chat/completions",
  "twinny.apiKey": "ql_YOUR_API_KEY",
  "twinny.model": "qlaw-orchestrator",
  "twinny.fimProvider": "openai-compatible",
  "twinny.fimApiUrl": "https://api.qlawai.com/v1/chat/completions",
  "twinny.fimApiKey": "ql_YOUR_API_KEY",
  "twinny.fimModel": "qlaw-orchestrator"
}
TIPS
  • Use Qlaw Orchestrator for autocomplete and daily coding — it has full tool calling support.
  • Qlaw Vision handles screenshot and document analysis when used through OpenClaw.
  • Your API key works with any OpenAI-compatible tool — not just the ones listed here.
  • Keep your key in an environment variable instead of hardcoding it.