Access and billing

|

​

Overview

Two separate things decide whether a coding task can run: whether the starting point is available to your organization, and whether the turn can be paid for. They fail differently and are fixed differently, so it’s worth keeping them apart.

​

Access

Coding Agent is in beta and is not one switch. Access is granted to your organization first, and then separately for each way of starting a task — the app, chat, each finishing touch, pull request fixes, security fixes, approved plans, and the Change Stack panel. The starting point availability may depend on your platform and plan. The practical consequences:

• Seeing one starting point does not mean the others are enabled. An organization can have Autofix on a pull request while the standalone app is not yet available to it.
• Access fails closed. A starting point your organization hasn’t been granted isn’t offered, rather than failing when you use it.
• If a starting point documented here is missing for your organization, contact support.

For which providers each starting point supports, see Where each starting point is available.

​

Provider authorization

Coding Agent delivers changes with your own Git provider authorization, not with a shared service account. You need a valid, current authorization for the provider account you’re delivering as. If it has expired or been revoked, delivery is refused until you reauthorize. This is what keeps branch protections, repository permissions, and your provider’s audit trail meaningful. See Who pushes, and who wrote it.

​

Who can see a task

Tasks are visible to your organization by default, so a teammate can pick up where you left off. A task’s author can make it private, which restricts its prompts, files, activity, and attachments to the author alone — including for anyone who follows a direct link. The author can switch it back at any time. See Control who can see a task.

​

Free turns

A turn is one run of the agent against one instruction. Starting a task is a turn; every message you send it afterwards — a steer, a queued follow-up, a revision request — starts another. Some first turns are free, because they come from an action CodeRabbit offered you rather than one you asked for: The free turn is the first one on those tasks. Steering the task, asking for a revision, or queueing a follow-up all start further turns, and those are billed normally.

​

Agent minutes

Beyond the free turns above, a turn needs one of:

• available trial credits,
• an organization configured for unlimited turns, or
• an active agent minutes add-on, which meters usage.

An administrator activates the agent minutes add-on in the organization’s billing settings. Until it is active, paid turns are refused with a message saying metered billing is not enabled for the organization.

​

Monthly spend cap

An administrator can set a monthly cap on metered agent minutes. Once accumulated spend for the month reaches the cap, new paid turns are refused. The cap stops future spending and nothing else: existing tasks, their history, and any work already delivered are untouched. Raise or remove the cap in billing settings to start paid turns again. Two of these are ordinary eligibility outcomes, and the message tells you which: A turn can also be blocked when CodeRabbit can’t verify the organization’s billing at all — an ambiguous or unavailable subscription, rather than a decision about your entitlement. That is a temporary condition, not something to configure; if it persists, contact support.

​

Consumed minutes

Organizations can see the coding minutes already consumed, shown alongside the billing notice and in the task experience. This display is rolled out separately from the rest of Coding Agent, so it may not be visible even where tasks are working normally.

​

What’s next