Scope Flexibility for AI Loading States

The assistant.threads.setStatus API method now accepts either the assistant:write or chat:write scope. This change simplifies permissions management for developers building AI-powered Slack apps.

Benefits for Channel-Based Apps

This update is particularly valuable for channel-based applications that want to implement AI loading states. Previously, apps needed to request the assistant:write scope or use the AI assistant split view. Now they can leverage the more permissive chat:write scope already used for standard channel messaging.

Deprecation Timeline

Important: The assistant:write scope support is temporary. Slack will eventually deprecate assistant:write in favor of the chat:write scope exclusively. Developers should update their applications soon to use chat:write to avoid future compatibility issues.

Action Items

• Review your app's OAuth scopes and permission requests
• Migrate to chat:write if you're currently using assistant:write for status updates
• Test your implementation to ensure AI loading states continue to work as expected