I am using MacroDroid (similar to Tasker) using the Termux:Tasker app to automate running Termux scripts and commands. My intent is to automate turning on the Ollama server by running the command "ollama serve &". This is accomplished using tudo so that commands can be run dynamically with MacroDroid/Tasker variables rather than being restricted to running a predefined script. The tudo wrapper and Termux:Tasker work fine otherwise in other situations and that is not the issue here. With a freshly booted phone or when Termux is not not running (i.e. no Termux persistent notification), If I run the "ollama serve &" command from Termux:Tasker, I get a successful stdout of the command like the server should be running. At this point there is no persistent notification from Termux indicating a running session, but remember I got a successful stdout. However, followup commands to communicate with the ollama server fail with an stdout of "Error: llama runner process has terminated: signal: broken pipe". When I go into Termux and run "ollama ps", I see a running process yet follow-up commands still fail until I "killall ollama" and retry directly from the start within Termux - this defeats the purpose of automating a command with Termux:Tasker. My opinion here is that it is neither a MacroDroid/Tasker, Termux:Tasker, nor Ollama issue. It seems to be an issue with Termux not properly starting a session. Are there any ways around this or perhaps this is a feature request? Thanks all!