I check the cost before Cline edits a second file

Your coding extension and your AI account do different jobs

Cline and Roo Code are coding assistants that run inside Visual Studio Code. They can read project files, suggest changes, and use tools to help complete a task. The extension provides the workspace experience; an AI service supplies the model that decides what to do next.

Using your own key means connecting the extension to an API account you control. The key is a private credential that authorizes requests, and those requests can cost money. Installing an extension does not, by itself, include the model usage you send through that key.

MyRelay gives an individual one key and one budget across several model families. That can simplify trying either extension without maintaining separate API accounts. The important habit is to start with a small task and inspect the spending before handing over a larger job.

Connect one extension before setting up the other

Choose Cline or Roo Code for your first test rather than configuring both at once. Install the extension from its official marketplace listing, open a small practice project, and find its API provider settings. Setting names can change between releases, so look for the option described as OpenAI-compatible rather than assuming every screen will match an older tutorial.

If you want to use this setup, create a MyRelay account and obtain your personal API key. Keep the key private. Paste it only into the extension’s designated credential field, not into a chat message, project file, or shared screenshot.

In the compatible-provider settings, enter your key and set the API base to https://api.myapirelay.com. Follow the current MyRelay connection instructions if your extension asks for a more specific endpoint format. An OpenAI-compatible connection describes the request format; it does not mean you must choose an OpenAI model.

Next, select an available model. If the extension requires a manually entered model identifier, copy the exact identifier from MyRelay rather than guessing it from a display name. Claude Haiku 4.5 is one option to investigate for small coding tasks. Check its current pricing and any compatibility guidance before starting.

Make the first request deliberately uneventful

Your first test should confirm that the connection works, not ask the assistant to rebuild an application. Open a small file you understand and ask the assistant to explain one function without changing anything. Keep the request narrow enough that you can judge the answer yourself.

For this test, leave automatic approvals off wherever the extension offers that control. Read requests to access files, run commands, or make edits before approving them. A model connection and a permission to act are separate things; a working API key is not a reason to grant unrestricted access.

If the request fails, check the selected provider, API base, credential, and model identifier before repeatedly retrying. A balance or model-availability issue may also be involved. Change one setting at a time so you can tell which adjustment helped.

Check the bill after one small exchange

Once you receive an answer, inspect the request details in MyRelay. Members can see each request’s tokens and cost. Tokens are the units used to measure the text a model receives and produces, including material the extension sends on your behalf.

A short instruction can still lead to substantial usage if the assistant reads several files or takes multiple turns. An agent task is often a sequence of requests, not one question with one fixed price. Your first test gives you a useful reference point, but it is not a guaranteed price for later work.

Set a personal spending allowance for the session. Do not assume that entering an API key creates a hard spending cap. Check which budget controls are actually available, and use the request history to decide when to stop.

Expand the task only after reviewing the first change

For your next task, ask for one small edit and review the proposed changes before continuing. Keep a recoverable copy of your work through version control. If the assistant starts repeating unsuccessful attempts, pause and clarify the problem instead of paying for another loop.

Once this routine feels comfortable, configure the other extension if you still want to compare workflows. Your own key gives you flexibility; small tasks, explicit approvals, and regular cost checks make that flexibility easier to afford.