Dashboard
The dashboard shows conversations, completed agent responses, active users and token usage, each with changes from the previous period. Switch the usage chart between responses and tokens, or view and copy its data as a table. Breakdowns by channel, agent and model show where usage comes from.
“Agent responses” replaces the previous message count, which included user messages. Date boundaries, failed responses and comparisons across daylight-saving changes are handled correctly.
Chat
New chats start with the greeting, agent description and input together in the center. During a conversation, the input moves to the bottom and becomes more compact in longer histories. A desktop timeline lets you preview and jump to individual turns.
- Concurrent conversations: Responses can run in several chats at once. Drafts, attachments and ongoing responses stay with their conversation; a background chat finishing does not change the current view.
- Prepare follow-ups: Queue more messages and attachments while a response is running. Remove queued messages, or pause and resume the queue. After failures, unsent follow-ups can be recovered as editable drafts. Queuing and recovery apply to the current session.
- Longer input: Messages support up to 65,536 characters. Large pasted texts become text-file attachments automatically; Ctrl/Cmd+Shift+V keeps them inline within the message limit.
- History and attachments: Open original files for every attachment type. Exports include the complete conversation; structured responses, attachments and tool details survive reloads and reconnects. Duplicate responses and incorrectly empty histories have been fixed.
Inbox
The conversation list shows agent avatars and names alongside chat titles. Label changes also appear in other open sessions, including removal of the last label. Large selections and reloaded histories are handled more reliably.
Agent settings
Profile, model, instructions and assignments are together on one page with expandable sections. Edit the name and model options there and save them together. Files and calendars appear according to the enabled tools.
Create new agents on a dedicated page. A confirmation helps protect unsaved input when leaving; agent switching and large selection lists respond faster.
Custom tools
Custom HTTP tools can map agent inputs into fixed JSON requests, including nested structures. Input types and defaults are preserved.
- Preview requests: Inspect the URL, headers and body using example arguments without contacting the external API. Credentials are masked.
- Send real tests: After explicit confirmation, send a request to the external API. This can create, change or delete data there. Previewing and testing do not save changes to the tool configuration.
- Inspect tool calls: Request information, status and error details are available on tool calls in chat and remain in the history. Repeated calls to the same tool are grouped compactly and can be expanded.
- Discover tools when needed: Enable on-demand discovery for each custom tool. The agent then receives its description and input schema when it discovers the tool. Existing tools remain directly available by default.
Other improvements
- Guided introduction: Short product tours explain the interface using isolated demo data. They leave real records untouched and return you to the previous view when finished.
- Files and calendars: Files already assigned to an agent are hidden in its file picker. Large file, calendar and group-member lists load completely. When some assignments fail, successful changes are preserved and errors are reported.
- WhatsApp: Newly connected numbers can be registered and verified more reliably. All website entries can be removed from a business profile. Templates support media headers, and the notice about Meta’s required payment method is clearer.
- Settings and privacy: Member, group and role pages reuse loaded data when switching between them. Download the data processing agreement as a PDF under Settings → Data and privacy.
- Loading and recovery: Previously loaded content remains visible where possible during temporary failures, with a notice and retry option. Sign-in and sign-up are simpler; new accounts wait for setup to finish. Navigation, permission updates and tenant switching are more reliable.
- Interface and languages: More compact headers and updated P-CATION colors make the interface more consistent. German, English, Italian and Polish translations have been completed.
Technical improvements and API notes
- Real-time updates and history: Typed tool results and structured responses are preserved in WebSocket updates. Deletion events also reach authorized owners of their own resources; recovery after connection loss has been improved.
- Chat streaming: Streams send blank NDJSON lines as heartbeats during longer pauses. Custom clients must skip these lines when parsing. Streaming and regular chat requests accept up to 65,536 characters.
- Whitelist events: Entries in
agent.whitelistare now a list of objects withid,match_typeandmatch_value, replacing the previous grouped-value structure. Custom event consumers need to be updated. - Custom tools: Defaults are validated against their declared input type when saving. The custom-tool HTTP client no longer stores or sends cookies. Error diagnostics retain useful status information with configured credentials masked.
- Models, access and operations: New agents default to
gpt-6-luna; existing model selections are preserved. Access checks for deactivated accounts and administrative impersonation have been tightened. Reused database connections reduce connection overhead; new readiness checks account for dependent services.