Cross-agent asynchronous communication method and system based on versioned code repository

Abstract

The application discloses a kind of cross-agent asynchronous communication method and system based on versioned code repository.The method uses versioned code repository as the message communication bus between agents: the sender agent writes the message to be sent in the form of file in the agreed directory of shared repository, and completes message sending by executing version commit and remote push operation;The receiver agent synchronizes by pulling the version from the remote repository, automatically identifies the message sent to itself based on the file naming rules and reads and processes it.The application supports asynchronous, reliable and persistent message communication between AI agents under different technology stacks, different operating environments and different network conditions, with zero infrastructure dependency, natural offline buffering, concurrent safety, cross-platform compatibility and other significant advantages.

Description

Technical Field

[0001] This invention relates to the field of artificial intelligence technology, and in particular to a method and system for implementing asynchronous communication across intelligent agents based on versioned code repositories. This method is applicable to reliable, asynchronous, and persistent message interaction between AI intelligent agents with different technology stacks, different operating environments, and different network conditions. Background Technology

[0002] With the rapid development of artificial intelligence technology, multi-agent collaborative work has become an important direction for AI applications. In practical applications, AI agents often operate under different technology stacks, different operating environments, and different network conditions, requiring efficient and reliable message communication mechanisms between these agents.

[0003] In existing technologies, cross-agent communication mainly employs solutions such as message queue middleware, API callback mechanisms, shared databases, same-process dialogue frameworks, or centralized communication proxies. These solutions all suffer from varying degrees of dependence on external middleware, strong network coupling, insufficient offline capabilities, and limited cross-platform compatibility, failing to meet the cross-platform, cross-network, asynchronous, and reliable communication requirements of multiple AI agents. Therefore, a cross-platform asynchronous communication method is needed that does not rely on message middleware, API callbacks, or shared memory. Summary of the Invention

[0004] This invention aims to provide a cross-agent asynchronous communication method and system based on versioned code repositories, utilizing the core features of version control systems (file writing, version commit, branch merging, and remote synchronization) as a message communication mechanism between agents.

[0005] A cross-agent asynchronous communication method based on a versioned code repository includes the following steps: the sending agent writes communication messages as files to a pre-defined directory of a shared versioned code repository; the sending agent performs a version commit operation on the file and pushes the version changes to a remote repository; the receiving agent pulls the latest version changes from the remote repository; the receiving agent automatically filters messages targeting itself based on the naming rules of the message files; and the receiving agent reads and processes the contents of the message files.

[0006] Key innovations include: using versioned code repositories as message buses to completely replace traditional message middleware; a publish / subscribe routing strategy based on file naming rules; version control systems that natively support offline message buffering; a version control-based concurrency conflict self-healing mechanism; and the ability to communicate with any technology stack and runtime environment as long as a Git client is available.

[0007] Beneficial effects: zero infrastructure dependency, native support for asynchronous offline operation, global message auditing, concurrency security, cross-technology stack compatibility, low-cost unlimited scalability, and support for complex workflows.

Claims

1. A cross-agent asynchronous communication method based on versioned code repositories, characterized in that, Includes the following steps: The sending agent writes communication messages as files to a pre-defined directory of a shared versioned code repository; the sending agent performs a version commit operation on the file and pushes the version changes to the remote repository; the receiving agent pulls the latest version changes from the remote repository; the receiving agent automatically filters messages targeting itself based on the naming rules of the message files; the receiving agent reads and processes the contents of the message files.

2. The method according to claim 1, characterized in that, The naming convention for the message file is: FROM {Sender} Logo} {date} {Optional number or topic}.{File format}, where FROM As a fixed prefix, {sender identifier} is the unique identifier of the sender agent.

3. The method according to claim 1, characterized in that, The versioned code repository adopts any one of the Git protocol, Mercurial protocol or SVN protocol, and the remote repository is any one of Gitee, GitHub, GitLab or a self-built Git server.

4. The method according to claim 1, characterized in that, The sending agent and the receiving agent run in different technology stacks, different operating system environments, or different network environments, including any combination of Python, Java, JavaScript, or the Button AI Sandbox.

5. The method according to claim 1, characterized in that, When the receiving agent is offline, the messages sent by the sending agent are automatically stored in a remote repository; when the receiving agent returns to online and performs a version retrieval operation, all unread messages can be retrieved at once.

6. The method according to claim 1, characterized in that, When two or more agents simultaneously write files to a versioned code repository, there are zero conflicts if they write to different files, and conflicts are automatically handled by the file merging mechanism of the version control system if they write to the same file.

7. The method according to claim 1, characterized in that, Also includes: By utilizing the version history function of the version control system, a timeline of communication messages, sender identifier, message content summary, and version change record are automatically generated, forming a complete communication log audit chain.

8. A cross-agent asynchronous communication system based on a versioned code repository, characterized in that, include: The message sending module is used to generate message files and perform version commit and remote push operations; The message receiving module is used to pull version changes from a remote repository and filter and read message files; The routing parsing module is used to automatically determine the target agent of a message based on file naming rules; the shared versioned code repository module is used to store message files and their version history among all agents; and the conflict resolution module is used to handle file version merging and conflicts when multiple agents write concurrently.

9. The system according to claim 8, characterized in that, It also includes a message auditing module, which generates a timeline of communication records, participants, and content summaries based on the commit history of the version control system, supporting message backtracking and audit trails.