# Continue


    Connect → Continue

# Use AxForge with Continue

    Continue is an
    open-source coding assistant that runs inside VS Code and JetBrains. It has no model
    of its own — you point it at one, which is what makes it useful here: the same editor
    assistance as a hosted product, running against AxForge.

## Is this the one you want?

Three of the tools on this page live in VS Code, and they are not interchangeable:

      | Tool | Best when you want |  |

        | **Continue** | Chat and inline edits driven by a **config file** you keep in version control, in **VS Code or JetBrains**. Indexes your repo for `@codebase` questions. |  |

        | Cline | An **agent** that plans and edits across files by itself. Configured in the UI, no file to edit. |  |

        | Codex / Claude Code | A **terminal** agent rather than an editor panel. |  |

## 1. Install Continue

It is an extension, not something built into your editor:

      - **VS Code** — Extensions (Ctrl/Cmd+Shift+X),
      search **Continue**, install the one by Continue Dev. Or
      from the marketplace.

      - **JetBrains** — Settings → Plugins → Marketplace → **Continue**.

A Continue icon appears in the sidebar once it is installed.

## 2. Find the config file

Continue keeps one config file per machine, outside your project:

      | System | Path |  |

        | macOS & Linux | `~/.continue/config.yaml` |  |

        | Windows | `%USERPROFILE%\.continue\config.yaml` |  |

Easiest route: open the Continue sidebar and use its settings (gear) to open the
    config — that way you are certainly editing the file it reads.

## 3. Add AxForge

```
name: AxForge
version: 0.0.1
schema: v1
models:
  - name: AxForge Chat
    provider: openai
    model: chat
    apiBase: https://api.axforge.ai/v1
    apiKey: your-axforge-key
    roles: [chat, edit, apply]
  - name: AxForge Embed        # optional, for @codebase indexing
    provider: openai
    model: embeddings
    apiBase: https://api.axforge.ai/v1
    apiKey: your-axforge-key
    roles: [embed]
```

    **Use `config.yaml` (schema `v1`).** The
    older `config.json` still loads but is legacy. `apiBase` must
    include the `/v1`; `provider: openai` calls
    Chat Completions by default.

## 4. Check that it worked

Save the file, then open the Continue sidebar. You should see:

      - **AxForge Chat** in the model picker at the top of the panel. If it is not
      there, Continue did not load the file — see below.

      - A reply that **streams in word by word** when you send "hello". Streaming is
      the sign it is really talking to the API rather than returning an error object.

      - A matching call in the console at
      Billing & usage within a minute or
      two. That is the end-to-end proof: your editor reached our API on your key.

## When it does not work

Three things break, and they look different:

      | What you see | What it means | Fix |  |

        |
          **AxForge Chat is missing** from the picker |
          Continue never read your file, or the YAML is invalid |
          Check you edited the path above, and that indentation is spaces not tabs. Continue shows config errors in its own panel. |
         |

        |
          **401** or "invalid API key" |
          The key is wrong, revoked, or has a stray space |
          Make a new key and paste it whole. Confirm it independently with the self-test. |
         |

        |
          **404**, or a reply that never arrives |
          `apiBase` is missing the `/v1`, or the model name is not one we serve |
          It must end `/v1`. Model ids are on Models & pricing. |
         |

    Still stuck? Run the self-test — it
    tells you in one click whether the problem is your key, your quota or us, so you know
    whether to keep debugging Continue at all.

## Notes

The `embed` role powers Continue's `@codebase` retrieval;
    point it at the `embeddings` model as above. Model names come from
    Models & pricing.

      ← aider
      Cline →



Source: https://axforge.ai/docs/connect/continue/