Updates and compatibility

What users should do

Before an announced update, save unsent drafts and download important results you need immediately. Follow any maintenance notice from your organization. After the update, refresh the application and check the affected task before submitting it again.

A disconnected browser does not prove that an agent or automated job stopped. Reopen its details and inspect the last confirmed action before repeating work.

What can differ

Available models, connector choices and controls depend on the installation, organization policy and plan. See feature availability. A provider can also change its model or authentication requirements independently of a CogLake update.

Existing account restrictions should not be worked around by granting broader roles. Use access troubleshooting when an expected option is missing.

Administrator preparation

Tell members about expected interruptions and coordinate any required source or identity-provider changes. Installation updates, infrastructure backups and technical rollback are handled by the responsible operator, not by following a procedure in this user handbook.

After an update, check a representative sign-in, permitted search, file preview and the workflows relevant to your organization.

Handbook coverage

This handbook was reviewed against the application on 4 October 2026. It includes chats and agents, automations, personal BYOK, memory, skills and plugins, source setup, account access and recovery. This date identifies the documentation review, not a promise that every feature is enabled on your installation.

Report a regression

Include the time, affected page, visible product version if available, browser/device, selected organization and exact message. For tasks, include the job reference and whether the action was confirmed. Do not send passwords, provider keys or decrypted backup content.