Use Claude Code in VS Code Without a Team Plan

Start with personal API access, not shared seats

You do not need a team subscription simply because you want coding assistance inside VS Code. Claude Code can use supported API connections, letting an individual developer pay for usage rather than purchase shared seats. The important distinction is that API billing and subscription access are separate arrangements.

This walkthrough uses MyRelay as the personal relay. It gives you one key and one budget across supported providers, and it works with Claude Code. Requests are billed through your MyRelay balance rather than treated as usage included in an unrelated subscription. You still need to configure Claude Code to use that connection.

Prepare a small balance and protect your key

Create a MyRelay account, add an amount you are comfortable spending on a short trial, and generate your personal API key. Start small while you learn how much your usual coding tasks consume. A first session should establish that the connection works, not attempt a complete application rewrite.

Keep the key private. Do not paste it into a conversation, commit it to a repository, or include it in screenshots. If you accidentally expose it, replace it before continuing. Treat a relay key like any other credential that can authorize paid requests.

Choose how Claude Code will run inside VS Code

Install VS Code and open a small project you understand. Then install Claude Code using its current official installation instructions. Those instructions may change, so use the supported method for your operating system rather than copying an old tutorial.

You can work through the Claude Code extension where its current release supports your provider configuration, or run Claude Code in VS Code's integrated terminal. The terminal route still keeps your editor, project, and assistant in one workspace. It is also a useful fallback if the extension's sign-in screen does not expose third-party connection settings.

Point the client at your personal relay

Before starting a coding session, follow MyRelay's current Claude Code setup instructions. Its API base is https://api.myapirelay.com. Use the Claude Code connection method documented there to supply the relay address and your personal key.

Claude Code supports environment-based configuration, but the exact credential field and how VS Code receives those settings matter. Configure the documented values in your local environment or supported client settings, not in your project source. If VS Code was already open when you changed environment settings, close and reopen it so newly launched processes can receive them.

Choose a model identifier exactly as shown in MyRelay's Claude Code instructions. If available for that connection, Claude Sonnet 5.5 is one option to evaluate. Do not assume a menu's display name is also the identifier the client expects. Check the listed price before sending your first request.

Verify one request before doing real work

Ask Claude Code to explain a single function in the open project without changing anything. Keep the request narrow and review any permission prompts before approving them. This gives you a low-risk way to check the connection and see how the assistant handles project context.

Next, inspect MyRelay's request history. Confirm that the request appears, then review its model, token usage, and cost. A successful response alone does not prove you used the intended billing route. If no matching request appears, check the active connection before continuing.

Keep each coding task small enough to price

Once the test works, ask for one bounded change, such as fixing a validation bug or adding a focused test. Request a brief plan first, inspect proposed edits, and run the relevant tests yourself. Avoid granting broad permissions merely to save a few clicks.

Review spending after the first few tasks. Long conversations, large files, and repeated troubleshooting can increase usage even when the requested edit sounds small. Start a fresh session when old context stops helping, and supply only the information needed for the next task. MyRelay's per-request token and cost records give you a practical feedback loop: compare what a task accomplished with what it cost, then adjust your scope before spending more.