Unable to overwrite updates / Task cannot be read—interrupted / bashoutput-ripgrep tool error / Conversation cannot continue / Unable to create automatically—manually add to history / External Chats not displaying properly

First of all, Alma is a great project. I’ve been using it for over a week now, and the user experience has been quite good. However, the latest few versions have contained several bugs that affect usability, and in my current environment, Alma is practically unusable:

1. Since the update to version 0.0.693, Alma cannot be installed via an overlay. Clicking "Retry" causes an endless loop as shown in Figure 1, while clicking "Cancel" results in the error shown in Figure 2. Even after disabling Alma’s auto-start, restarting the computer, and launching it as an administrator, the same error occurs. The only solution is to uninstall the current version and then install the downloaded package. Since you release updates frequently, having to uninstall the program every time is clearly quite cumbersome.

2. a) After successfully creating a task to run in the background, Alma cannot retrieve the task’s information or results; instead, it matches them to other currently running tasks.

b) There is an issue with task status synchronization. Taking the "Great Tit" task shown in the figure as an example, this was generated by the TG bot after I configured the grok-imagine-1.0 model in the settings. The image was also pushed to TG, but the task status continues to show as "In Progress."

c) Currently, users can only end a task by specifying the task ID in a conversation. Is it possible for users to manually interrupt tasks, view task execution output, or delete task records directly in Mission Control?

3. Errors frequently occur when invoking the bashoutput task, displaying “Tool 'BashOutput' failed: Background shell not found. Recent shells:”. Since Alma cannot retrieve bash information, it repeatedly attempts the operation. The persistent errors cause delays and prevent the task from progressing.

4. An error occurs when invoking the rg task: “Tool 'Grep' failed: rg:

.resources\app.asar.extracted\out\renderer\nul: function is incorrect. (os error 1) rg:Vresources\app.asar.extracted\out\renderer\assets\nul: function is incorrect. (os error 1)”, even though I have added the Windows installation path for ripgrep to the environment variables.

5. After some dialogue processing, no tool is selected, yet no output is generated. This persists whether I retry after an interruption, continue sending messages, or even switch models.

6. What are the conditions for automatic memory creation? Currently, no memory is being generated in the settings. Also, does manually adding memory require a specific model?When I manually add a memory using GPT-5.2 for testing, it displays “Failed to create memory: fetch failed.” Previous errors included “Failed to create memory: Embedding API error: 404 - {"error":{"message":"Not found","type":"invalid_request_error"}}” and“Failed to create memory: Embedding API error: 401 - {"error":"Unauthorized"}”

7. When toggling between Show and Hide External Chats, the chat only displays the first time. After that, when clicking Hide, the Telegram conversation briefly flashes and then disappears.

Here is a conversation snippet that covers both issues 2 and 4.

User (2026-03-17 10:14)

Currently, when running Alma, calling tools occasionally displays “Tool 'BashOutput' failed: Background shell not found. Recent shells:” and “Tool 'Grep' failed: ripgrep (rg) is not installed or not available in PATH.”I have already added E:\A_software\ripgrep to my system environment variables. Please check if these two issues still occur. If they do, please provide a solution—do not make any direct modifications yet; let me know the plan first.

Assistant (March 17, 2026, 10:14 AM)

<!-- mission:m-mmtzbat9 --> 📋 Mission Created — Investigate intermittent errors in Alma during runtime regarding the missing background shell in BashOutput and the Grep tool failing to find ripgrep, and provide a solution that does not involve direct modifications

• Reproduce and confirm the trigger conditions and occurrence frequency of the two types of errors (missing BashOutput background shell, Grep unable to find ripgrep)

• Verify whether the ripgrep path configuration in Windows environment variables is effective for the current runtime environment/process (including differences between new and old terminals/service processes)

• Identify the source and lifecycle of the shell relied upon by Alma/tool calls, and analyze why "Background shell not found" occurs

• Provide step-by-step solutions and verification steps for both types of issues (solutions first, then modifications) 📊 4 goals

Assistant (March 17, 2026, 10:14 AM)

Status

Task card created; the issue will be investigated via background execution. No changes to the environment for now.

Next Steps

Once the backend provides the trigger conditions and verification results, I will first provide you with a step-by-step solution and verification steps, and then we’ll determine if any changes are needed.

User (March 17, 2026, 10:30 AM)

Can the error still be reproduced? What is the solution you proposed?

User (March 17, 2026, 10:40 AM)

What about the results of the previous "m-mmtzbat9" task? Please summarize them.

Assistant (March 17, 2026, 10:41 AM)

Task Status (m-mmtzbat9)

I can't find any task records for m-mmtzbat9 on my end; I only see m-mmtzy6cb as currently active. This indicates that the previous task was not assigned to Mission Control (possibly due to an old thread or a failed creation).

Confirmed results

• ` rg --version ` outputs normally, indicating that ripgrep is available in the current process’s PATH.

Here is a comprehensive solution (no modifications required)

1) “Tool *Grep failed: rg not installed”

Possible cause: The Alma process is running in an “old environment” and hasn’t inherited the PATH you recently added.
Verification steps:

# Check using the process environment where Alma is running
where rg
rg --version

Solution (no changes required):

• Restart Alma first (to ensure the new PATH is loaded)

• If the error persists, run ` set PATH ` or ` setx PATH ` in the terminal before starting Alma

2) “Tool *BashOutput failed: Background shell not found”

Possible cause: The background shell has long since exited, but its output is still being fetched.
Verification steps:
Reproduction: Start a background Bash session, then wait a while before retrieving the output.

Solution (without modifications):

• When this error occurs, simply rerun the same command.

• If you need a long-running background task, avoid using short-lived shells; instead, run it in the foreground or use a long-running process

Next Steps

If you’d like me to continue reproducing and investigating the issue (especially the missing BashOutput), I can run another round of the “background shell + delayed output retrieval” test procedure.