> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sourcebot.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# V5 to V6 Guide

This guide walks you through upgrading your Sourcebot deployment from v5 to v6.

## Breaking Changes

### Every deployment must be activated

<Note>
  **Who's affected:** Deployments on the free plan. Deployments with an active paid subscription are not affected.
</Note>

#### Description

In v5, a deployment without a license ran on the free plan. Starting in v6, the free plan is replaced by the **Basic** plan, which is free but requires an activation code. A deployment without a valid license enters **restricted mode** when it starts.

In restricted mode:

* Search, Ask, file browsing, the REST API, and the MCP server are blocked. API requests return HTTP `403` with the `DEPLOYMENT_RESTRICTED` error code.
* Users can still sign in with a password or single sign-on, and owners can still open **Settings** to fix the license.

<Warning>
  Activation codes are validated by the Sourcebot license server at `https://deployments.sourcebot.dev`. Your deployment must be able to reach it over HTTPS. If your deployment can't reach the license server for 7 days, it enters restricted mode until it reconnects. Deployments without outbound internet access need an [offline license key](/docs/activating-a-subscription#license-key-offline-licensing).
</Warning>

#### Action Items

1. Sign in as an owner and go to **Settings → License**.
2. Enter your email address to request an activation code. The code is sent to that address.
3. Enter the activation code. Sourcebot leaves restricted mode once the license server confirms the code.

If you already have an activation code from v5, you can enter it instead of requesting a new one.

### The Basic plan is limited to five active users

<Note>
  **Who's affected:** Deployments on the Basic plan with more than five active users.
</Note>

#### Description

The Basic plan allows up to five active users. If your deployment has more than five active users after you activate it, it stays in [restricted mode](#every-deployment-must-be-activated) until the number of active users is five or fewer. No users are removed automatically.

Only active users count toward the limit. Pending users (who have never signed in) and suspended users don't count. Once the limit is reached, new users can't join through invites, access requests, sign-up, or SCIM.

#### Action Items

Do one of the following:

* Go to **Settings → Members** and suspend or remove users until five or fewer are active.
* Upgrade to a paid plan from **Settings → License**. Paid plans don't limit the number of users. See the [pricing page](https://www.sourcebot.dev/pricing) for more details.

### Anonymous access is no longer available

<Note>
  **Who's affected:** Deployments that let users browse without signing in, using the **Settings → Security** toggle, the `FORCE_ENABLE_ANONYMOUS_ACCESS` environment variable, or the `enablePublicAccess` config setting.
</Note>

#### Description

In v5, deployments on the free plan could enable anonymous access. Starting in v6, users must sign in to use Sourcebot, even if anonymous access was enabled before upgrading.

The `FORCE_ENABLE_ANONYMOUS_ACCESS` environment variable has been removed, and the `enablePublicAccess` config setting no longer has any effect.

#### Action Items

* Remove `FORCE_ENABLE_ANONYMOUS_ACCESS` from your environment and `enablePublicAccess` from your [config file](/docs/configuration/config-file).
* Make sure everyone who used Sourcebot anonymously has an account, or can create one.
* If you have questions about this change, [contact us](mailto:support@sourcebot.dev).

### API and MCP requests are rate limited

<Note>
  **Who's affected:** Deployments on the Basic plan, and deployments with a paid subscription purchased on v6. Paid subscriptions purchased on v5 are not affected.
</Note>

#### Description

Starting in v6, each user can make up to 10,000 API requests per day. The following count as one request each:

* REST API requests for search, files, repositories, connections, code navigation, and git history (blame, diffs, and commits).
* MCP tool calls.

Using Sourcebot in the browser doesn't count.

The limit resets every day at 00:00 UTC. Once a user reaches it, their API and MCP requests fail with HTTP `429` and the `API_RATE_LIMIT_EXCEEDED` error code until the limit resets. Other users aren't affected. See [Rate Limiting](/docs/api-reference/rate-limiting) for details.

#### Action Items

If your users need more than 10,000 requests per day, [contact us](mailto:support@sourcebot.dev).

### `SOURCEBOT_TELEMETRY_DISABLED` has been removed

<Note>
  **Who's affected:** Deployments that set `SOURCEBOT_TELEMETRY_DISABLED=true`.
</Note>

#### Description

The `SOURCEBOT_TELEMETRY_DISABLED` environment variable has been removed. Starting in v6, telemetry is only disabled when your license includes it. If you set `SOURCEBOT_TELEMETRY_DISABLED=true` in v5, telemetry turns back on after upgrading unless your license disables it.

#### Action Items

* Remove `SOURCEBOT_TELEMETRY_DISABLED` from your environment.
* If you need telemetry disabled, [contact us](mailto:support@sourcebot.dev) about a license that includes it.

### AI Search Assist has been removed

<Note>
  **Who's affected:** Deployments with a language model configured whose users used the wand icon in the search bar.
</Note>

#### Description

AI Search Assist, which turned a natural-language description into a code search query, has been removed. The wand icon no longer appears in the search bar.

#### Action Items

* No changes are needed. To ask questions about your code in natural language, use [Ask Sourcebot](/docs/features/ask/ask-sourcebot).

## Upgrading

<Warning>
  Before upgrading, review the [Breaking Changes](#breaking-changes) section and complete any actions that apply to your deployment.
</Warning>

### Docker Compose

1. Pull the latest image

```bash wrap icon="terminal" theme={null}
docker compose pull
```

2. Restart your deployment

```bash wrap icon="terminal" theme={null}
docker compose up -d
```

### Helm chart

1. Refresh the chart repository

```bash wrap icon="terminal" theme={null}
helm repo update
```

2. Upgrade the release

```bash wrap icon="terminal" theme={null}
helm upgrade sourcebot sourcebot/sourcebot \
  -f values.yaml \
  --set-json "sourcebot.config=$(cat config.json)"
```

### After upgrading

If your deployment wasn't activated before upgrading, it starts in restricted mode. Sign in as an owner and follow the steps in [Every deployment must be activated](#every-deployment-must-be-activated) to restore access.

## Troubleshooting

Having trouble upgrading from v5 to v6? Reach out to us at [support@sourcebot.dev](mailto:support@sourcebot.dev) and we'll help you get your deployment working.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.