Skip to main content

Workspaces, credits, and Builder settings

Hosted Builder is workspace-scoped. Settings and limits are designed to reflect that.

Switch workspaces from the top bar​

Use the workspace switcher in the Builder header to:

  • confirm which workspace you are working in
  • move between Builder-enabled workspaces
  • compare plan and Builder credit posture across workspaces
  • open the current workspace back in OXVO

If enabled in your environment, Builder can also create a new workspace directly from the switcher flow.

What the workspace card shows​

The Workspace section in Settings summarizes the current Builder context:

  • account name
  • role
  • plan
  • remaining AI credits
  • credit reset date
  • project storage limit

This is the fastest way to answer, "Can this workspace support the next thing I want to build?"

Managed model access​

In hosted Builder, model access is workspace-managed rather than user-managed.

The Managed Model Access section tells you:

  • which providers are enabled
  • how many models are available
  • how Builder billing works for model usage
  • whether your workspace has access to paid build tools

If you do not see the models you expect, the change usually needs to happen in the OXVO workspace, not inside a single Builder project.

Workflow defaults​

Builder settings can shape how teams work day to day.

Common workflow controls include:

  • default chat mode
  • auto approve behavior
  • auto fix problems
  • auto expand preview
  • chat completion notifications

Teams should review these carefully before enabling more automation.

AI defaults​

Builder also exposes app-building defaults such as:

  • thinking budget
  • max chat turns in context
  • max tool-call steps
  • context compaction behavior

These settings help control speed, cost, and response style for ongoing Builder sessions.

Integrations in Settings​

The hosted Builder settings area is also where teams review connected services such as:

  • GitHub
  • Vercel
  • Supabase
  • Neon

Use project-level surfaces when the integration is specific to one app. Use workspace settings when the integration affects the broader Builder environment.

Agent permissions and MCP​

Builder can expose additional operational controls for:

  • agent tool permissions
  • HTTP MCP configuration
  • telemetry preferences

These settings matter most for teams using Builder in a more controlled or multi-user environment.

When to go back to OXVO​

Use OXVO itself when you need to manage:

  • workspace billing
  • plan changes
  • account-level administration
  • Builder access for members

Builder is where you build apps. OXVO is still where the workspace is governed.