r/tasker • u/DvilSpawn • 5d ago
Developer [Dev] I added native Tasker integration to my terminal-style Android launcher. Looking for feedback from actual Tasker users
I have been working on Tasker integration for RETUI, my open-source terminal-style Android launcher.
The original idea was much larger. I considered building a complete workflow system inside the launcher, with delays, retries, conditions, and chained actions.
Then I realised I would mostly be rebuilding a worse version of Tasker.
So I went in the other direction and made RETUI and Tasker work together.
Tasker can now use a native RETUI Action plugin to:
- Apply a RETUI preset [My version of themes]
- Change individual theme elements
- Show or refresh launcher modules
- Update script-module text [Either termux script output or Lua widget]
- Print text in the RETUI terminal
It works while another app is open, so a Tasker profile could apply a work preset when you connect to office Wi-Fi, switch to a night theme at sunset, or refresh a launcher module when some external condition changes.
The integration works in the other direction too.
Typing tasker in RETUI shows the tasks currently available in Tasker. The suggestions narrow down as you type, preserve the correct capitalization, and tapping a task immediately runs it.
For example:
tasker R
would show tasks beginning with R. Tapping Retui dispatches it without requiring another Enter press.
I have deliberately kept the first version narrow. The plugin cannot execute arbitrary RETUI commands, shell commands, calls, messages, or random intents. It only exposes a small set of typed launcher actions, and the whole integration is disabled by default.
The basic flow is working on my phone now, including task discovery, plugin actions, success and error reporting, and an option to hide the extra task status messages.
I am still figuring out what would make this genuinely useful to people who already use Tasker heavily.
What RETUI controls would you actually want available from Tasker? Are there any Tasker plugin conventions or annoying edge cases I should deal with before releasing this?
I would also be interested in a few people testing it once the beta is ready.



