Skip to main content

August 10, 2026

Highlights​

Two big ideas land together this release: spend you can govern by team, and playbooks you can reuse everywhere.

  • Org admins: Organization Units put cost control where your company already is. Mirror departments and teams in Organization Units, assign people into the tree, and set shared monthly or daily spend limits on any unit. Spend rolls up the branch; a parent cap is a hard stop for everyone underneath. Spot where money is going in analytics with org-unit filters and top-unit cost views. Look for Organization Units in organization settings as we enable it in production.
  • Everyone: meet Skills. Save instructions, formats, and step-by-step guides as skills, then reuse them in App Builder and chat. The AI can apply a matching skill on its own, or you can pick one from the + menu. You can also ask it to pull in a skill from the internet (with a risk check before you use it). Look for the short walkthrough the first time you land in App Builder.
  • Org admins and builders: share skills, and Code is now Workspace. Promote a skill into your organization catalog so the whole team gets it automatically (admins manage it while it is shared; members can still fork). The tool formerly called Code is renamed Workspace; new agents get it by default, which pairs well with skills that include files.

Organization Units and Skills roll out as we enable them for organizations in production. Not every workspace will see every piece on day one.

New features​

Organization Units: structure your company, then cap spend by team​

Org-wide and per-user limits were a start. Real cost control needs the shape of your company: Engineering versus Marketing, Platform versus a nested team.

Organization Units let admins build that hierarchy in organization settings:

  • Create nested departments and teams, rename and move them as the org changes
  • Assign members to a unit (including bulk CSV import)
  • Set shared monthly and/or daily spend limits on a unit so the whole branch shares one budget
  • See rolled-up spend versus limit next to the tree you manage

How the budgets behave:

  • Usage by anyone in a unit and anyone in units beneath it counts toward that unit’s shared spend
  • A parent limit is a hard cap on its entire branch. When the parent is exhausted, descendants stop spending even if a child still has room under its own limit
  • A child can have its own limit (including unlimited at that layer), but it cannot spend more than its parent allows
  • People who are not assigned to a unit keep the existing personal and organization billing rules

In analytics, you can filter by organization unit and see which units are driving tokens and dollar cost, so spend conversations start with a map instead of a guess.

This capability was built earlier and is now being enabled in production. When Organization Units appears in your organization settings, you can start with a simple department tree and add shared budgets when you are ready. Organizations with no unit budgets configured keep today’s personal and org limits unchanged.

Skills you save once and reuse everywhere​

Repeating the same brand rules, report format, or build checklist in every conversation wastes time. Skills fix that.

A skill is a set of instructions (and optional files) you save once. When it can help with what you are doing, the AI finds it and applies it. Prefer to be explicit? Open the + menu next to the prompt and pick the skill yourself. The same library can cover App Builder and chat, so you are not recreating the same playbooks in two places.

You can:

  • Create and manage skills from My Skills
  • Attach skill files (templates, examples, reference docs) so the AI has more than plain instructions
  • Ask the AI to save a skill for you after a good run, then refine it later
  • Import a skill from the internet and get a heads-up when something looks risky

First time in App Builder, a short interactive walkthrough introduces the idea without burying you in settings.

For the full story - creating skills, files, availability, and how discovery works - see the new Skills guide.

An organization skills catalog for admins​

Personal skills are great until the whole company needs the same standard. Admins can now promote a skill into an organization catalog:

  • Everyone in the org can discover and use it
  • The AI can apply catalog skills automatically when they help
  • While a skill is in the catalog, only admins can edit or delete it - changes to a shared skill apply to everyone immediately, so editing moves to the people accountable for that
  • Admins can disable a catalog skill org-wide without deleting it, or remove it from the catalog so it becomes personal again
  • Members who need a custom variant can fork the skill into their own library
  • Catalog skills tagged for agents can be linked to your agents too, and they stay in sync as admins update them

Admins also get an Organization skills page to see skills across user libraries, filter by where they are available (chat, agents, App Builder), and open an Analyze in chat review before promoting something sensitive.

Details for both members and admins are in the org skills catalog section of the Skills guide.

Code is now Workspace​

The agent tool formerly labeled Code is now Workspace, with a plainer description of what it is for (an info icon next to the name reminds you it was formerly called Code). New agents get Workspace enabled by default. If you link a skill that includes files, Workspace is the right companion so the AI can open those files instead of squeezing everything into the prompt.

If you build agents, the refreshed agent skills guide covers creating skills with file bundles, linking existing ones, and how they behave in conversations.

Improvements​

  • Chat feels steadier mid-run. The working indicator stays up through quiet stretches, ask-question flows mount more cleanly while arguments stream in, and interactive tool cards unlock when the run is waiting on you.
  • Web search cards read better in narrow panels (long queries no longer clip the header).
  • Shared chats: editors with collaborator access can upload attachments, not only the owner.
  • Skill picker and library polish across App Builder landing, agent skill views, and org discovery (file counts, clearer empty states, safer retries).

Bug fixes​

Reliability fixes across Skills (picker, catalog, permissions, file bundles), chat streaming and tool cards, Workspace / sandbox teardown, MCP tool ownership, auth invite and login edge cases, and billing balance reads. Together they should make Skills, Organization Units rollout, and everyday chat feel more predictable as each reaches your organization.

⌘J