August 2026 Release
The August 2026 release introduces the Pulse app platform: integrations, the Meeting Agent, the Code Agent, skills, webhooks, and chat side panels are now delivered and governed as apps — one unit an organization can enable, roll out, or withhold in one place.
Developers maintaining custom applications should use the Developer Hub for API, SDK, package, and migration notes.
Highlights
- Apps are the new unit of capability in Pulse, with three states: enabled, available, disabled.
- Connect cards in chat — when the assistant first needs an account you have not connected (or one that expired), it asks with a card in the timeline; connecting resumes the paused work.
- Multiple accounts per provider, with a default account the assistant uses when you do not specify one.
- Organization app management — org-wide installs, required apps, audiences, and gradual rollouts.
- Manifest apps — org admins can author apps declaratively: HTTP tools, skills, webhooks, panels, and settings forms, validated and versioned at publish.
- REST token scopes — personal access tokens on
/rest/v1now carry explicit scopes; existing tokens keep working.
New in Pulse
The Apps world
Every catalog integration, plus the Meeting Agent and the Code Agent, now appears as a built-in app. Built-in apps arrive enabled automatically; enabled does not mean connected — Pulse asks for an account exactly when work first needs one. Built-in apps can be disabled by an admin but never uninstalled, and disabling never deletes data. Plan-gated apps (Meeting Agent on Enterprise, Code Agent on Pro and above) appear with a Requires plan notice on workspaces whose plan does not include them. See Apps.
Connect cards and account defaults
The assistant no longer fails quietly on a missing or expired connection: a Connect card appears in the timeline, deduplicated per app and reason, and completing the connection returns you to what you were doing. You can connect several accounts per provider and pick a default; if you never picked one, Pulse adopts the account it was already using as your sticky default, visible and changeable in your integration settings.
Chat side panels
The panels next to the timeline are now customizable — show, hide, reorder, reset. Apps can contribute panels of their own, and organizations can set a default arrangement for everyone or lock it.
For organization admins
- Organization apps — set each app's state, install org-wide, mark apps as required, and target audiences (everyone, or groups and users, evaluated live).
- Skill rollout through apps — distribute a skill by creating an app, adding the skill under it, and requiring the app for the right audience.
- App authoring — create a draft app, edit its manifest with server-side validation, publish immutable versions, and roll back. See Building apps.
- Per-user app settings — apps can define settings forms; secret values are stored encrypted and are write-only.
- Admin actions on apps are recorded in the audit log.
For developers
- Manifest reference — declarative tools with risk classes and response projection, skills, incoming/outgoing webhooks, chat panels, MCP servers, and settings forms, with strict validation, template namespaces, host allowlists, and egress guarding. See the manifest reference.
- Apps API — registry, publish/validate/rollback, installations, states, and user config over
/api/apps, with optimistic-concurrency (409 on conflict). See the apps API. - REST token scopes — eight coarse scopes on
/rest/v1; a missing scope returns 403 naming the scope. See scopes.
What to try
- Ask Pulse for work that touches a tool you have not connected — watch the Connect card appear, connect from it, and see the work resume.
- Connect a second account for a provider and set a default, then ask for work that uses it.
- As an admin, disable an app and confirm the assistant explains the capability is unavailable instead of failing.
- As an admin, create a small manifest app with one read tool, validate, publish, and call it from chat.
- Customize your chat panels, then (as an admin) set an organization default arrangement.
Action required
- Existing personal access tokens keep working unchanged. New tokens are minted with an explicit scope list — review the scopes your scripts actually need.
- Workspace admins should review their app states after the upgrade: catalog providers arrive enabled by default, and anything the workspace should not offer can be disabled in Organization apps.