Changelog

[2026-07-08]

Permission Sets

Organizations can now control agent access with permission sets, with fine-grained, scope-based permissions.

What's new:

Permission sets — Create named sets that define, per action (view/edit/delete/publish/create), how far access reaches: all, project, team, own, or none at all.

Scoped enforcement — Access checks resolve against the assigned set's scope for each action.

Instant propagation — Updating a set's scopes re-syncs enforcement immediately for everyone assigned to it, with no per-user rewrite needed.

Safe rollout — Enforcement is gated behind a feature flag per organization, so existing orgs keep their current behavior until explicitly switched over.

Refer to this guide for details: Permission Sets for Agents

[2026-06-17]

Response API improvements

Deprecated created_by and caching_enabled from request body of "Stream Agent Response (SSE)" and "Generate Agent Response (Non-Streaming)" endpoints. The requesting user is now logged automatically based on the token whereas caching_enabled can be toggled using "Update an Agent" endpoint.

[2026-06-02]

Agent Status behavior

The status field on agents now follows a managed lifecycle tied to the publish workflow. Calling POST /api/v2/agents/{agent_id}/publish on a "Drafted" agent automatically promotes it to "Live", making it visible to other users. Once an agent reaches "Live" status, subsequent calls to PUT /api/v2/agents/{agent_id} attempting to revert it to "Drafted" will receive a 400 error.
Note: This behavior is applicable if staging-agent feature is available in your system.

[2026-04-22]

Staging & Publishing for Agents

Agents now support a staging environment that is completely separate from the published agent.

What's new:

Staging environment — All edits apply to Staging only. The published agent continues serving end-users unchanged until changes are explicitly published.

Change preview (diff) — Before publishing, a full diff of every change is available covering agent settings, instructions, knowledge sources, tools, and guardrails.

Publish — Promotes staging changes to Production instantly. Blocked if Staging is identical to Production to prevent no-op releases.

Publish history — Every publish is recorded with a timestamp, the publisher's identity, and a summary of what changed.

Rollback — Any previous publish can be restored back onto Staging, with a preview of the resulting changes before committing. Production is not affected until the rolled back state is published.

Refer to the guide for details: Staging & Publishing for Agents

[2025-10-15]

Deprecation Notice: Legacy Response & Indexing APIs

⚠️ The legacy Response and Indexing endpoints are scheduled for deprecation.
Please migrate to the respective Stable APIs before the sunset date.

Timeline:
Deprecation date: 15-Oct-2025
Sunset date (end of support): 14-Nov-2025

After the sunset date, the endpoints mentioned in below migration guides will no longer be available.

Refer to the migration guides for details:

Response API Migration Guide

Indexing API Migration Guide

[2026-07-08]#

Permission Sets#

[2026-06-17]#

Response API improvements#

[2026-06-02]#

Agent Status behavior#

[2026-04-22]#

Staging & Publishing for Agents#

[2025-10-15]#

Deprecation Notice: Legacy Response & Indexing APIs#