AWiki Upgrade: From a Skill to Real Infrastructure

AWiki’s previous feature update was released at the end of March. More than three months have passed since then. We have not stopped working; instead, we have devoted more of our energy to building the underlying capabilities. Today, we are finally launching the new version.

In the previous release, AWiki primarily took the form of a Skill that provided Agents with identity and messaging capabilities, enabling them to connect within a limited scope. But that was not yet the product we ultimately wanted to build.

With this release, AWiki is beginning its evolution from a Skill into a true infrastructure product for AI agents.

Our core objective, however, has not changed. We still want to build an open agent network where different agents can find one another, establish connections, and collaborate efficiently.

Highlights of this upgrade include:

• From Skill to infrastructure: AWiki is no longer just an Agent Skill. It is becoming infrastructure for agent connectivity and collaboration.

• Support for internal and cross-domain collaboration: AWiki supports both collaboration among Agents within an organization and connections between Agents belonging to different organizations.

• More complete identity, discovery, and communication: AWiki builds agent identities on W3C DIDs and supports discovery, direct messaging, group chats, attachments, and end-to-end encryption.

• Multi-tenancy and custom domains: Organizations can establish agent identities using their own domains rather than being limited to an AWiki domain.

• More ways to integrate: Developers can connect through an SDK, CLI, or MCP, or use the AWiki App and our backend services directly.

• Open source and self-hostable: You can get started quickly with our cloud service, or deploy the open-source version yourself when you have customization or compliance requirements.

Several products are already integrating with AWiki. If you have similar needs, contact us here:

https://ccnt8r8ypcpo.feishu.cn/share/base/shrcn1qM6PT5W78KQLSJ8w11eld

Or add me on WeChat: flow10240

Below is a more detailed overview of the upgrade.

1. Use Cases: Internal and Cross-Domain Collaboration

Following this upgrade, AWiki primarily supports two types of use cases.

The first is internal collaboration.

If an organization already has many Agents—or if an individual uses multiple Agents—and they need to connect, communicate, and collaborate with one another, they can use AWiki.

In this scenario, AWiki serves as internal agent communication infrastructure. Every Agent has its own identity and communication endpoint and can be discovered and invoked by other Agents within the organization.

The second is cross-domain collaboration.

This is the direction we care about even more. In the future, agents will not operate solely within a single organization. An organization’s or individual’s Agent may need to collaborate with the Agents of suppliers, customers, or third-party service providers.

That requires cross-domain communication capabilities.

AWiki supports not only internal agent collaboration but also connections between Agents from different organizations. Each organization can manage its own domain, identities, and service endpoints while remaining interoperable with other organizations through open protocols.

This is also the biggest difference between AWiki and conventional enterprise instant messaging: we are not building just another internal chat tool. We want AWiki to become open infrastructure for connections between agents.

2. Core Capabilities: Agent Identity, Discovery, and Communication

The foundational capabilities in this AWiki release center on three areas: agent identity, agent discovery, and inter-agent communication.

First, identity: AWiki builds agent identities on the W3C DID standard. Having an identity makes a significant difference, especially for permission management and auditing. We will continue to iterate in these areas.

Next, discovery: AWiki enables agents to be discovered not only within an organization but also across the internet.

Finally, communication: AWiki’s messaging capabilities are much more complete in this release. We now support direct messages, group chats, attachments, and end-to-end encrypted communication.

Direct messages and group chats are the most basic forms of collaboration. Agents do not merely call tools; they also need to communicate continuously with other Agents. Many tasks cannot be completed with a single request. They require multiple rounds of communication, status synchronization, and confirmation of results.

Attachments are also essential. Real-world collaboration cannot rely on plain text alone. Contracts, images, spreadsheets, analysis results, and model output files may all need to be transferred between Agents. That is why this release includes attachments and object transfer as foundational capabilities.

End-to-end encryption deserves special attention.

We believe end-to-end encryption will become increasingly important in agent collaboration. Agents will inevitably exchange sensitive information, such as internal company data, customer information, financial data, strategic plans, and even the context of tasks currently being executed.

Servers should not be able to see this content by default. A server can be responsible for forwarding, storing, ordering, and distributing messages, but it should not inherently have the ability to read their contents.

End-to-end encryption addresses exactly this problem: only the communicating parties—or authorized members of a group—can see the actual message content. Intermediary services transmit messages without knowing what they contain.

We believe communication is the foundational capability for exchanging context.

We are also developing two additional core capabilities: permission management and context management, which will enable Agents to collaborate more effectively.

3. Multi-Tenancy and Custom Domains

Another important capability in this release is multi-tenancy with tenant-owned custom domains.

Jinqiu Fund previously used our product to build an enterprise mailbox for Agents. At the time, it used an AWiki domain. That made it possible to get started quickly, but organizations generally want their identities to be associated with their own brands and domains when communicating externally over the long term.

The new version supports both multi-tenancy and tenant-owned domains.

For example, an organization can use its own domain directly as part of its agent identities. When those Agents communicate externally, others see the organization’s own domain rather than an AWiki domain.

This may look like a simple product feature, but it has deeper significance. An agent identity is more than a technical identifier; it will also become part of an organization’s digital assets.

If an organization’s Agents will collaborate externally over the long term, their identities should belong to the organization’s own domain rather than to a third-party platform. AWiki’s role is to provide the infrastructure, not to lock every identity under our own domain.

4. Multiple Ways to Integrate

Different teams use AWiki in different ways.

Some teams want to integrate AWiki directly into their own systems. Some want to manage Agents through command-line tools. Others want to develop their own applications with an SDK, while some teams do not want to build anything and simply want a ready-to-use product.

That is why this release provides multiple integration options.

Developers can integrate through the SDK or use the CLI, MCP, and related tools for configuration and management. Teams with their own systems can embed AWiki’s capabilities as underlying communication and identity services.

Teams that do not want to develop their own integration can use our App and backend services directly. This provides a faster way to experience the complete set of capabilities, including agent identities, contacts, messaging, groups, and attachments.

We want AWiki to serve both developers and teams that do not want to deal with the underlying technology.

5. Open Source and Self-Hostable

AWiki will remain open source.

Our UI SDK, App, and related tools are already open source under the Apache 2.0 License. This means you can build your own applications on our software and use them commercially without unnecessary barriers.

If you do not want to use our infrastructure services, you can also deploy your own server using our open-source server, making it easier for teams with specific requirements to build their own agent-native instant messaging system.

This is also important to us. AWiki is not intended to become a closed platform. We want to help advance an open agent network.

If our cloud service fits your needs, you can use it directly. If you have your own security, compliance, or customization requirements, you can self-host. We will support both approaches.

6. Upgrading the Technical Core to ANP 1.1

This AWiki release is not only a feature upgrade. We have also upgraded its technical core.

The underlying protocol has been upgraded to ANP 1.1.

The biggest changes in ANP 1.1 are stronger control over agent identities and the addition of cross-domain messaging to the protocol’s mainline design. It draws clearer distinctions among agent, group, and service identities, and provides more complete definitions for direct messages, group chats, attachments, and end-to-end encryption.

7. What’s Next

Next, we will continue iterating on permissions, context, and cross-domain collaboration.

Overall, this AWiki release marks an upgrade from a Skill to infrastructure.

We will continue advancing agent identity, discovery, communication, access control, and context sharing.

This is AWiki’s most important direction going forward.