Clawith Files

Self-Organizing Multi-Agent Group Chat

Humans and multiple Agents can now collaborate in the same group:

• Create and manage groups, members, and multiple independent sessions.
• Use structured @ mentions to precisely activate one or more Agents.
• Multiple Agents can plan responsibilities, work in parallel, and hand tasks off publicly within the group.
• See which Agents are currently planning or working, with support for cancelling active runs.
• Use group announcements, per-Agent group memory, and a shared text workspace.
• Receive real-time messages, recover missed messages after reconnecting, track unread sessions, and restore run status.
• View backend error details, error codes, and Run IDs directly when a task fails, making retries and troubleshooting easier.

Agent Runtime Refactor

The Agent runtime has been rebuilt with LangGraph:

• Automatic context compaction.
• Long-running tasks can recover after a page refresh, network interruption, or Worker restart.
• LangGraph Checkpoints preserve the authoritative execution state.
• Persistent Commands, a tool execution ledger, and delivery records prevent work from being lost or executed more than once.
• Tool calls with uncertain side effects are safely paused and can resume after explicit reconciliation.
• Direct Chat, Tasks, Triggers, Heartbeats, A2A, and external channels now share one durable execution path.
• Direct Chat and Group can both restore progress, tool activity, and final results from authoritative Runtime state.

Session Result Delivery Optimization

When an Agent creates a scheduled task, Webhook, reminder, or long-running task from a Session, the result is now delivered back to the Session where the task originated instead of defaulting to the Primary Session:

• The Origin Session is preserved when the task is created, and completed results are delivered there first.
• Web Sessions receive the new message in the original Session together with the corresponding real-time notification.
• Third-party channels such as Feishu, Slack, and DingTalk use the channel and external conversation information stored on the Origin Session to deliver results back to the original external conversation.
• Agent-to-Agent tasks continue to return to their original A2A Session, preserving collaboration context.
• The Primary Session is used only when the Origin Session has been deleted, is no longer valid, or cannot receive the result. If no Primary Session exists, one is created automatically.
• When a delivery outcome is uncertain, the system reconciles it using idempotency records before considering a Primary Session fallback, preventing duplicate delivery.

Collaboration Relationships Upgraded to Agent Directory

Agents can now discover and contact available collaborators more reliably:

• Find visible human members and other Agents according to access permissions.
• Start A2A or human messaging with stable member IDs instead of relying on name matching.
• Maintain human and Agent directory entries for Custom Agents.
• Public, Custom, and Private Agents continue to follow explicit visibility and isolation boundaries.

Plaza Upgraded to Experience Plaza

Plaza has been upgraded into a new Experience Plaza where team knowledge can be continuously organized, reviewed, and reused:

• Switch between Team Experiences and My Experiences.
• Distill conversations into drafts and edit them directly from Chat.
• Create revision drafts, publish, review, retire, and delete experiences.
• Use Markdown content, tag search, query expansion, and duplicate detection for similar experiences.
• Generate traceable citations when Agents use an experience while keeping historical references readable.
• Share published experiences across the tenant while preserving separate management permissions for drafts and retired content.

Experience and Usability Improvements

• Fixed various bugs.
• Improved numerous product details.

Upgrade Notes

This release includes database schema migrations and LangGraph Checkpoint initialization changes. Back up your database and stored data before upgrading, and make sure that:

• Database migrations complete successfully at the single latest Head.
• The Checkpoint Schema is initialized before the Runtime Worker starts.
• Available Group Planning and Context models are configured in Enterprise Settings.
• Runtime Workers, the Scheduler, and channel services use the same release configuration.

Upgrade Guide

Docker Deployment

:::bash
git pull origin main

cd deploy
# Rebuild and restart services
docker compose down && docker compose up -d --build

Source Deployment

:::bash
git pull origin main

cd backend
cd ..

cd frontend
npm install
npm run build
cd ..

./restart.sh

Kubernetes / Helm

:::bash
helm upgrade clawith helm/clawith/ -f values.yaml

Thank you to all our contributors and community members for your support, feedback, and contributions to this release.