Skip to content
BytesBrains
Client Integration Guide

Connecting VS Code to BytesBrains Cruise

A complete walkthrough to install the official extension, configure your Cruise API key, choose model lanes in GitHub Copilot Chat, and run autonomous agent sessions.

Free ExtensionVS Code 1.104+Tested & Verified
Install from MarketplaceCreate API Key
Step 1

Before you start: workspace and credit check

Cruise authenticates every request through a workspace. Before configuring your editor, verify that your account is active and has an available balance.

  1. Sign in to your account: Sign in at bytesbrains.com/login using the account associated with your workspace or job application.
  2. Verify your workspace: Ensure you have an active workspace selected (if your account shows cruiseGrantState: no_workspace, create or select a workspace first).
  3. Check your credit balance: Open the Cruise Spend Dashboard or the Credits tab. Candidates completing a practical assessment should verify that their complimentary $5.00 task grant is visible on their balance.
Deliberate budget allocation
For candidates, your $5.00 grant is shared between your coding agent requests in VS Code and automated wrok.in pull request reviews. Monitor your usage as you build.
Step 2

Issue a dedicated API key

For clean access auditing and hygiene, issue a key dedicated specifically to VS Code rather than reusing credentials across tools.

  1. Navigate to the Keys tab in your Cruise dashboard.
  2. Click Create Key and enter a descriptive name, such as vscode-agent.
  3. Select the relevant project for your work.
  4. Copy the key immediately. Active Cruise production keys begin with the prefix cru_live_.

Security note: Never commit your Cruise API key into source control or store it in workspace files. The key will be entered directly into VS Code’s secure credential storage.

Step 3

Connect the client: install extension and select model

The BytesBrains Cruise extension integrates with VS Code’s Language Model API and GitHub Copilot Chat.

  1. Install the extension: Install directly from the Visual Studio Marketplace or search for BytesBrains Cruise in the Extensions tab (Cmd+Shift+X / Ctrl+Shift+X).
    (Using VSCodium or Gitpod? Install from Open VSX).
  2. Enter your API key: Open GitHub Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I). When prompted by the Cruise extension, paste your Cruise API key.
  3. Select a Cruise lane in the model picker: In the model dropdown at the bottom of Copilot Chat, select: bb/agentic-coding (Agentic Coding).
  4. Switch to agent mode: Toggle Copilot Chat into Agent Mode to allow the assistant to read files, run tests, and perform iterative multi-file edits.
Step 4

Check it works: run a prompt and observe spend

Verify that your connection is live and that requests are accurately recorded on your Cruise ledger.

  1. In Copilot Chat with bb/agentic-coding selected, submit a test instruction:
    Explain the workspace structure and outline the entry points.
  2. Observe the response stream in the chat window.
  3. Open the Cruise Spend Dashboard. Confirm that the call appears in your per-request ledger, showing the serving provider model, token counts, and the exact dollar amount deducted.
Step 5

Choosing a lane: dynamic routing and resilience

Instead of hardcoding a single static model name, Cruise routes calls using Lanes. A lane represents the task requirements rather than a rigid vendor ID:

  • bb/agentic-coding: Recommended for coding agents, complex refactoring, and test writing. Cruise allocates the optimal model underneath at that hour’s spot pricing.
  • bb/chat-assistant: Recommended for exploratory questions, architectural debates, and documentation writing.
  • Automatic fallback: If a specific provider model experiences downtime or high latency, Cruise automatically fails over to an equivalent member model so your coding session is never blocked.
Step 6

When it refuses: errors and what to do

When an agent prompt cannot be served, Cruise returns clear, actionable error codes directly in VS Code:

wallet_exhaustedHTTP 402

Wallet Exhausted

The workspace prepaid credit balance has reached zero ($0.00). Requests are refused until funds are added.

What to do: Top up your workspace balance in the Cruise dashboard under Credits & Billing.
Candidate note: Do not top up personal funds. Contact the hiring team via your application page to request review or grant extension.
budget_exhaustedHTTP 429

Project Budget Cap Reached

The project hard budget ceiling set for this key or project has been reached.

What to do: Review and adjust project budget thresholds on the Projects tab in your Cruise workspace.
Candidate note: Check that requests are assigned to your active hiring project, or contact hiring if limits persist.
invalid_api_keyHTTP 401

Invalid or Revoked API Key

The API key provided does not match an active key in your Cruise workspace.

What to do: Check key status or generate a new dedicated key on the Keys tab.
Candidate note: Verify that the key starts with "cru_live_", was copied completely with no leading or trailing whitespace, and is active in your Keys tab.
Notice for hiring candidates
If your workspace balance runs out (wallet_exhausted), do not top up personal funds. Contact the hiring team directly on your application page to explain the situation and request support.
Step 7

Practical task assessment notes

If you are working on a practical task as part of your interview process, remember the following guidelines:

  • Spend deliberately: Your $5.00 grant is calibrated to cover the development cycle, test generation, and review cycles if managed prudently.
  • Automated code reviews with wrok.in: Install the wrok.in GitHub App on your task repository and configure your Cruise key under BYOK. Every PR you open will receive automated reviews.
  • Collaborate with your agent on rework: Direct your VS Code coding agent to read review feedback from wrok.in, propose fixes, commit updates, and reply to review threads.
  • Document your JOURNEY.md: Maintain a JOURNEY.md file in the repository documenting each step, architectural decisions, prompt iterations, and any bugs or feedback encountered in Cruise.
  • Submit on your application page: When your PR is merged and all checks pass, submit the links on your application page.