VibeCC Docs
Getting Started
QuickstartAuthenticationModelsErrorsRate LimitsStreamingPricing (Beta)SDKs
Client Guides
Claude CodeOpenAI SDKCursorContinue
Migration
From OpenAI DirectFrom LiteLLMFrom Multi-Key Setup
Release
Release Notes
← Console

Migrating from VibeCC Beta to GA

This guide covers everything you need to update when upgrading from the VibeCC beta (v0.x) to the General Availability release (v1.0).

Breaking changes

API key format

Beta keys started with vcc_beta_sk_. GA keys start with vcc_sk_.

Before (beta):

Authorization: Bearer vcc_beta_sk_abc123

After (GA):

Authorization: Bearer vcc_sk_abc123

Action: Generate a new GA key in Console → API Keys. Beta keys stop working 30 days after your workspace is migrated.

Base URL

The relay endpoint URL has changed.

| Environment | Beta URL | GA URL | |-------------|----------|--------| | Relay (inference) | https://beta.relay.vibecc.io | https://relay.vibecc.io | | Control Plane API | https://beta-api.vibecc.io | https://api.vibecc.io |

Update your ANTHROPIC_BASE_URL or equivalent env var in Claude Code, Cursor, or your application config.

Workspace IDs

Beta workspace IDs used a short numeric format. GA uses full UUIDs.

You will need to update any hardcoded workspace IDs in automation scripts or CI pipelines.

Find your new workspace UUID in Console → Workspaces → Settings.

What's new in GA

  • PromptOps: Version, deploy, and roll back system prompts with zero downtime
  • Conversation history: Full request/response history with replay and search
  • SePay VND payments: Top up your credit balance in Vietnamese Dong
  • Stripe payments: Credit card and international payment support
  • Status page: Real-time incident tracking at status.vibecc.io
  • Weekly digest emails: Monday summary of usage and spend
  • Budget quota warnings: Alerts at 80% and 100% of monthly quota

Migration steps

  1. Export your beta configuration — download snapshot from Console → Settings → Export
  2. Create a GA workspace — sign in at console.vibecc.io and create a new workspace
  3. Recreate provider credentials — add your API keys for Anthropic, OpenAI, etc.
  4. Import routing policies — re-apply any custom routing rules
  5. Generate a new GA API key — Console → API Keys → New Key
  6. Update your tooling — replace beta URL and key in Claude Code / Cursor / .env
  7. Test with a sample request — verify routing and billing work as expected
  8. Decommission beta access — revoke old beta API keys from Console

FAQ

Will my beta usage data be preserved? No. Beta usage history does not transfer to GA. GA tracking starts fresh from the moment your workspace is migrated.

Can I use both beta and GA in parallel during migration? Yes. Beta keys remain valid for 30 days after GA launch. You can run both in parallel during transition.

What happens to my beta invites? Beta invite codes are no longer needed in GA — sign up directly at vibecc.io.

I have a question not covered here. Open a support ticket at console.vibecc.io/support or email support@vibecc.io.