AI NewsDev toolsAnnouncement

Kilo adds ChatGPT Business plan support for Sign in with ChatGPT

Kilo's coding tools now accept a corporate ChatGPT Business account for sign-in. A team's Kilo requests draw from the organisation's ChatGPT allowance instead of a personal plan or an API key.

AI News

Editorial2 min read

LinkedInX
Screenshot from the Kilo announcement showing the Sign in with ChatGPT flow for a ChatGPT Business plan

Image: Kilo Code

Why it mattersA company already paying for ChatGPT Business can point its coding tool at the same pool. There is one admin, one bill and one usage limit for the whole team.

Kilo Code has added Business plan support for its "Sign in with ChatGPT" feature. The company announced the change on its blog. The feature lets a developer log in to Kilo's coding tools with a corporate OpenAI account. Their coding requests then draw from the organisation's centralised ChatGPT allowance. Personal ChatGPT Plus and Pro accounts were already supported. Business plans were not.

Kilo's own wording: a developer picks "Continue with ChatGPT" in Kilo. The developer then signs in with the corporate OpenAI account. The feature covers Kilo's Desktop IDE, its extensions, its cloud agents and its CLI.

What it replaces

Before the change, a team on ChatGPT Business had three options for using OpenAI models inside Kilo. The first was a separate, personal ChatGPT Plus or Pro account for each developer. The second was a company OpenAI API key, paid by usage and managed outside the Business plan. The third was a different provider. Each path meant a second bill and a second usage pool.

The new flow replaces all three for a team on ChatGPT Business. A developer signs in to Kilo through the Business account. Their Kilo work then draws from the organisation's existing Business allowance.

What the admin controls

Kilo says the admin controls on the OpenAI side carry over. The post quotes OpenAI's documentation. Business admins control which apps their teams may use. They also control how much of each member's subscription allowance each app can consume.

An admin can turn Kilo access off for a specific user or for the whole workspace. An admin can also cap how much of each member's monthly allowance a given app may use. The cap means a developer running long Claude Code sessions in Kilo cannot use up another developer's share.

What the user side looks like

The developer flow is OAuth. No OpenAI API key is stored on the developer's machine. Kilo cites the lack of local key handling as one reason for the change. A developer who leaves the team no longer carries a working API key with them.

Kilo supports several coding model vendors. So this change is not about which models are reachable. It is about who pays for each call. For teams already on ChatGPT Business, the answer is now the Business plan.

What it does not cover

The announcement does not give a price for Kilo itself. Kilo runs on a separate subscription. The post does not name a date for ChatGPT Enterprise support. OpenAI's Business plan is the plan directly below Enterprise. The post does not give any number for how many Kilo customers have asked for this flow.

Kilo's blog is the only source for the feature. It is a vendor announcement about the vendor's own product. A team considering the move should check its own ChatGPT Business admin panel for the app-level caps the post names.

Source

SourceKilo Code

This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.

Share
LinkedInX
Start a project