Weekly GitHub Report for Airi

Thank you for subscribing to our weekly newsletter! Each week, we deliver a comprehensive summary of your GitHub project's latest activity right to your inbox, including an overview of your project's issues, pull requests, contributors, and commit activity.

Table of Contents

• I. News
  • 1.1. Recent Version Releases
  • 1.2. Other Noteworthy Updates
• II. Issues
  • 2.1. Top 5 Active Issues
  • 2.2. Top 5 Stale Issues
  • 2.3. Open Issues
  • 2.4. Closed Issues
  • 2.5. Issue Discussion Insights

• III. Pull Requests
  • 3.1. Open Pull Requests
  • 3.2. Closed Pull Requests
  • 3.3. Pull Request Discussion Insights

• IV. Contributors
  • 4.1. Contributors

I. News

1.1 Recent Version Releases:

The current version of this repository is v0.8.0-alpha.6

1.2 Version Information:

Released on December 1, 2025, this version introduces significant enhancements including full beat-sync integration across multiple stages, Wayland support, a new Vite plugin for uploading large assets to S3-compatible storage, and improved UI features like chat history and devtools previews. Numerous bug fixes address issues in beat-sync event routing, macOS crash prevention, and UI responsiveness, reflecting a strong focus on stability and cross-platform compatibility.

II. Issues

2.1 Top 5 Active Issues:

We consider active issues to be issues that that have been commented on most frequently within the last week. Bot comments are omitted.

1. Use tRPC in server-runtime: This issue proposes using tRPC in the server runtime to enhance maintainability and robustness of the project. The suggestion aims to improve the software architecture by integrating a more streamlined communication method between client and server.

   • The comments question the necessity and technological advancement of using tRPC, suggesting that there are alternative ways to connect the client and that such an update may not be essential.
   • Number of comments this week: 1

2. 希望能将与airi的聊天记录保存在本地或者导出: This issue requests the addition of a feature to save or export chat records with the AI named Airi locally, aiming to facilitate chat backup or migration. The user highlights the need for a convenient way to preserve conversation history for future reference or transfer.

   • The comment suggests using the Model Control Protocol (MCP) as a potential method to save chat logs, explaining that some models have servers that automatically record interaction histories in local files, which include settings, documentation, and chat records formatted in a standardized way.
   • Number of comments this week: 1

Since there were fewer than 5 open issues, all of the open issues have been listed above.

2.2 Top 5 Stale Issues:

We consider stale issues to be issues that has had no activity within the last 30 days. The team should work together to get these issues resolved and closed as soon as possible.

1. airi Is Damaged and Can’t Be Opened. You Should Move It To The Trash: This issue reports that the application "airi" is damaged and cannot be opened on macOS 15.3.1 with an Apple M4 Max chip, prompting users to move it to the trash. A temporary workaround involving clearing extended attributes with the command xattr -c /Applications/airi.app is provided, and the reporter is willing to submit a pull request to fix the problem.
2. Provide reference for character card templates: This issue requests the provision of a character card template to serve as a reference for creating custom personalities or vtuber personas in Moeru-AI Airi, which currently supports character cards in .json format but lacks any official formatting guidelines. The absence of such a template in the devblog documentation or repository makes it difficult for developers to properly format and develop custom character cards.
3. feature request: Support for Pre-defined VTuber Studio Format Motions/Animations: This issue requests the implementation of support for importing and triggering pre-defined VTuber Studio format motions and animations to enhance the expressiveness and interactivity of AI-driven VTuber performances. It proposes parsing specific motion and expression JSON files, mapping Large Language Model outputs to these motions, and integrating with existing model metadata or alternatively using a simpler custom configuration to enable dynamic activation of rich, professional-style animations.
4. bug: does not hide main window when onboaring: This issue reports a bug where the main application window fails to hide during the onboarding process on a Windows 11 system. The reporter has provided system details and confirmed adherence to contribution guidelines, expressing willingness to submit a pull request to resolve the problem.
5. Crowdin integration: This issue is about integrating Crowdin, a localization platform, into the project to facilitate translation workflows, with the contributor offering assistance once the project lead authorizes the free open-source license. It also involves specific tasks such as skipping certain CI and review steps for Crowdin pull requests and considering the creation of a bot account to manage Crowdin PRs.

2.3 Open Issues

This section lists, groups, and then summarizes issues that were created within the last week in the repository.

Issues Opened This Week: 3

Summarized Issues:

• Feature Requests for Chat and Connectivity: This topic covers requests for new features including the ability to save or export chat records locally for backup or migration, as well as the reimplementation of the MCP connection feature after migrating to Electron. Both issues highlight the need for improved functionality to enhance user experience and system integration.
• [issues/782, issues/783]

• Alibaba Cloud STT Configuration and Testing Errors: This topic involves an error encountered during testing of Alibaba Cloud STT where configuration validation passes but the test fails due to a type mismatch error with FormData. The issue points to a discrepancy between successful configuration and runtime execution despite the service working correctly in the Alibaba Cloud console.
• [issues/785]

2.4 Closed Issues

This section lists, groups, and then summarizes issues that were closed within the last week in the repository. This section also links the associated pull requests if applicable.

Issues Closed This Week: 1

Summarized Issues:

• tauri-plugin-mcp server connection limitation: The tauri-plugin-mcp currently supports connection to only one server at a time, which restricts its usability for applications requiring multiple server connections. This limitation caused the maintainers to revert to using Electron and subsequently close the related issue.
• issues/196

2.5 Issue Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed issues that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed issues from the past week.

III. Pull Requests

3.1 Open Pull Requests

This section provides a summary of pull requests that were opened in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Opened This Week: 1

Key Open Pull Requests

1. feat(pinia-broadcast): use BroadcastChannel & SharedWorker for syncing states across windows & tabs: This pull request introduces the use of BroadcastChannel and SharedWorker to synchronize Pinia store states across multiple windows and tabs in the stage-tamagotchi multi-window architecture, addressing issues with state syncing and simultaneous TTS audio playback by implementing a communication channel that ensures only one instance handles message dispatching.

• URL: pull/780

• Merged: No

• Associated Commits: ed3d0, d6b6d, 08d43, 0c9a5, 8608d, 5102e, 6e41f, a45ff, 5055b, efeeb, b4585

3.2 Closed Pull Requests

This section provides a summary of pull requests that were closed in the repository over the past week. The top three pull requests with the highest number of commits are highlighted as 'key' pull requests. Other pull requests are grouped based on similar characteristics for easier analysis. Up to 25 pull requests are displayed in this section, while any remaining pull requests beyond this limit are omitted for brevity.

Pull Requests Closed This Week: 3

Key Closed Pull Requests

1. feat(nix/stage-tamagotchi): update to electron rewrite: This pull request updates the nix package for the stage-tamagotchi project to incorporate an Electron rewrite, addressing the issue where the app previously only displayed a transparent window with error messages and was in a non-functional state.

• URL: pull/646

• Merged: Yes

• Associated Commits: f6e59, 61e5d, 05625, ac26e, 17dda

2. fix(stage-tamagotchi,stage-shared): split eventa and beat-sync business into two entries: This pull request fixes the stage-tamagotchi and stage-shared components by splitting the eventa and beat-sync business logic into two separate entries to improve code organization and clarity.

• URL: pull/779

• Merged: Yes

• Associated Commits: 5dfb4, 02bde

3. refactor(ui): move Button component to @proj-airi/ui: This pull request refactors the codebase by moving the Button component into the @proj-airi/ui package to improve modularity and organization within the UI layer.

• URL: pull/781

• Merged: Yes

• Associated Commits: 7e21e, 88404

3.3 Pull Request Discussion Insights

This section will analyze the tone and sentiment of discussions within this project's open and closed pull requests that occurred within the past week. It aims to identify potentially heated exchanges and to maintain a constructive project environment.

Based on our analysis, there are no instances of toxic discussions in the project's open or closed pull requests from the past week.

IV. Contributors

4.1 Contributors

Active Contributors:

We consider an active contributor in this project to be any contributor who has made at least 1 commit, opened at least 1 issue, created at least 1 pull request, or made more than 2 comments in the last month.

If there are more than 10 active contributors, the list is truncated to the top 10 based on contribution metrics for better clarity.