Candor Deploy v1.1.0 — Candor Deploy

Connecting Claude or ChatGPT to Candor works again. “Add Candor” from claude.ai, ChatGPT or Claude Code sends you to the same sign-in the portal uses, then asks which project the assistant may deploy to, and you’re connected — no token to copy. The old consent screen still expected the retired client area, so nobody could get past it.
Organizations. Your workspace is now a project inside an organization, and you can invite people to it by email with a role — owner, admin, developer, viewer or billing. Roles inherit from the organization down to each project and each app, and can be overridden for one project or one app when somebody should have more (or less) there than everywhere else. An invitation can be scoped that way too: invite a contractor to one app and one app is all they can reach. Everything you had is already inside an organization we made for you, and you own it.
Billing belongs to your organization, not to one person’s account. The card on file, the plan, the invoices and the payment emails all attach to the organization now, so a colleague leaving does not take the billing with them, and anyone you give the billing role can handle the card and the plan without also being an owner. Payment emails — card declined, workspace paused, payment received — go to every owner and every billing member, and to nobody else. One card and one subscription cover every project in the organization: usage is billed once, and each plan you have projects on appears as a single line on the invoice with the number of projects on it. Usage is priced at your organization’s highest plan — an organization with a Studio project is charged for usage at Studio’s rate and gets Studio’s included usage across every project in it, so a project still on Free rides on the better deal rather than dragging the rest down to the worse one. Move a project up and the rate follows it the same day, with no charge for the change itself; move the last such project away and it comes back down.
You can now put the card where the bill is. Adding or replacing a payment method happens on your organization’s billing page, not on a personal account page — so if you run two organizations, each one holds its own card and its own invoices instead of both quietly charging the first one. If you would rather have a card per project, choose per-project billing when you create the organization: each project then has its own billing page and its own card, and adding one starts that project billing straight away with its full spending headroom while the rest of the organization is untouched. The choice cannot be switched once billing has started. Plan changes and spend budgets live on the same pages, one project at a time, and your organization’s billing page shows what each project used this month, so a single invoice line still tells you where the money went. Nothing changes for an existing account: the card you already have is the card your organization already uses, and the old account billing page keeps working for one more release.
If you call the API directly: a workspace is created at POST /v1/orgs/{slug}/projects now. The old POST /v1/workspaces answers 410 Gone and names its replacement. Your existing CLI token keeps working — it was migrated to a token scoped to the project it already reached.