Feedback: Some Anna App Tools Show Installation Done but Still Appear as Not Installed in Agent Details

Developers
1

Background

While testing the flow for installing Anna App tools into an Anna Agent, I found that several apps show the same issue:

The installation flow shows that the tool installation is complete, with a Done status, but the corresponding tool still appears as Not Installed in the Agent Details page.

This makes it difficult for users to determine whether the tool was actually installed successfully, and it also affects subsequent usage and debugging of the app’s capabilities.

Core Issue

The main issue is: the installation status is inconsistent across different parts of the platform.

The behavior is:

  1. The user starts the tool installation flow.
  2. The installation process appears to complete successfully and shows Done.
  3. The user opens the Agent Details page.
  4. The corresponding tool still appears as Not Installed.

This inconsistency has several direct impacts:

  • Users cannot confirm whether the tool has actually been installed into the agent.
  • If the tool cannot be used, users cannot tell whether the installation failed or whether the displayed status is incorrect.
  • Developers cannot easily determine whether the problem comes from the tool configuration, the installation flow, or the status synchronization logic in Agent Details.

Key Affected Apps

Priority App Name Tool ID Observed Issue
:fire: Recall — Persistent Memory for Anna tool-perseus-mimir-memory-2gtynted The installation flow shows Done, but the tool still appears as Not Installed in Agent Details.
:fire: Meeting AI tool-prash-meeting-ai-anna-4jg6ku3k The tool uses npm-based distribution. After the download/installation flow completes, the tool still appears as Not Installed in Agent Details.
:fire: Manim Studio tool-manishpathania092-tool-dev-manim-studio-kea37juj The installation flow shows Done, but the tool still appears as Not Installed in Agent Details.
:fire: Mirror AI Multiple tools, listed below All 6 tools show as installed/completed in the installation flow, but all of them still appear as Not Installed in Agent Details.

Mirror AI tool IDs:

  • tool-parthbansal20-5851-decision-critic-b2r4yr54
  • tool-parthbansal20-5851-agent-supervisor-76y2kr8r
  • tool-parthbansal20-5851-learning-path-wyh42drj
  • tool-parthbansal20-5851-doc-brutalist-b4fkzsrj
  • tool-parthbansal20-5851-project-genesis-8rfxrwge
  • tool-parthbansal20-5851-prompt-analyzer-m9fex7sf

Other Observations

The following apps are not the main focus of this feedback, but I also observed some related issues during testing:

App Name Tool ID Notes
CommunityOps Agent tool-giansandoval-communityops-tool-ejh7utzy This tool may not have multi-platform distribution and may only provide a Windows build. I skipped the installation during testing.
Sanctum KeyPulse tool-learnerabhinavdwivedi-keypulse-tools-node-6z6kg573 The tool configuration file may have issues. I skipped the installation during testing.
World Director None This app appears to be frontend-only and may not have a tool that needs to be installed into the agent.

Expected Behavior

For the tool installation flow, the platform should keep the installation status consistent:

  1. If the installation flow shows Done, the corresponding tool should appear as installed in Agent Details.
  2. If the tool was not actually installed successfully, the installation flow should not show success and should provide a clear failure reason.
  3. If the installation succeeded but status synchronization failed, the platform should prompt the user to refresh or retry synchronization.
  4. For apps with multiple tools, the platform should show the installation result for each individual tool, instead of only showing an overall completion state.

Actual Behavior

Currently, multiple apps show the same behavior:

  • The installation flow shows completion.
  • The Agent Details page still shows the tool as Not Installed.

Mirror AI is especially useful as a reference case: all 6 of its tools show the same issue. This suggests the problem may not only be caused by individual tool configuration errors, but may also be related to installation status synchronization, installation result validation, or the display logic in Agent Details.

Suggested Investigation Areas

I suggest prioritizing the following areas:

  1. Whether the Agent Details installation status is correctly refreshed after a tool installation completes.
  2. Whether Done in the installation flow only means the package was downloaded, rather than fully registered as an installed tool.
  3. Whether npm-distributed tools have additional validation or registration steps that may fail after the download completes.
  4. Whether installation results for multi-tool apps are correctly written into the agent state.
  5. Whether the Not Installed status in Agent Details is based on the same source of truth as the installation flow.

Summary

The main issue in this feedback is: several Anna App tools show Done in the installation flow, but still appear as Not Installed in Agent Details.

It would be helpful for the platform to prioritize fixing this installation status inconsistency, or to provide a clear failure reason when installation does not actually complete. This would make it much easier for both users and developers to understand whether a tool was successfully installed and what action should be taken next.