Currently, navigating two or three levels deep into a submenu, only to realize you are in the wrong place, requires returning all the way to the three dots menu to start over. A small back button at each menu level would resolve this and meaningfully reduce friction for frequent users.

Given that the component already exists in Scenes v2, this feels like a natural carry-over rather than a net-new build. Small quality-of-life improvements like this compound over time and go a long way toward keeping the experience polished.

Thank you for considering it, and for everything you continue to put into Tasker.

However, when Tasker needs the user to select an image, the resulting file picker does not contain image sources in the Open from view. It's just a plain file picker.

As it is now, user must extract icons from packs and place the images in a folder so that the file picker can find them. It would save the user a lot of time if Tasker used the Open from menu variant that presents image sources. This would be particularly useful when using Tasker to create scenes and widgets.

Screenshots showing difference between the file pickers:

"normal" file picker

"image sources" file picker

A Google searched yielded this: Google Copy/Paste Menu

I would suspect that there might be a way for Tasker to predeclare some Task Caller spots that the user could configure in preferences, much like many of the other areas the app has enabled enhancements for (Tiles, Share, etc.).

Screenshots:

- Dialog reference of the menu I'm referring to

- The extended portion of the menu where apps Google Translate and CoPilot have added their own options.

The current Run Log is powerful but becomes hard to read with many automations running. Seeing only that specific task or profile's past runs would make debugging faster, clearer, and more approachable while keeping the global Run Log unchanged.

Tasker will by default include everything that is included in the project. Even those who doesn't belong to the project, which the user may not want to share to begin with. 

While I must acknowledge that including them may be very convenient to ensure the export works properly, it looks dubious to me that the user is not informed at all about this.

Furthermore the default behaviour is that we have to back out to export. Which is not the usual way to handle confirmation.

Thus Tasker should.

1. List everything profiles, tasks, scenes, (PTS) and their scoped variables in the share activity.
2. Make it very clear which items doesn't belong to the items that being shared. Especially those who is in different project.
   
   1. Show a toast that says. "Export contains another items from different project."
   2. Highlight those who belongs to another project or items that is directly tied the the shared item.
3. Improve the export flow.
   1. Replaces the cancel button with export button/ Create new button to confirm export.
   2. Ask user if they want to import or not when they back out of the share activity.

BIND_APPWIDGET
BIND_VOICE_INTERACTION
BIND_QUICK_SETTINGS_TILE
BIND_DEVICE_ADMIN
BIND_JOB_SERVICE
BIND_INPUT_METHOD
BIND_CONTROLS
BIND_SCREENING_SERVICE
BIND_INCALL_SERVICE
BIND_REMOTEVIEWS
Shizuku

I'm writing to report an issue with the "Notify Live Update" action on my Google Pixel 10 Pro. Currently, the notification content is not appearing on the lock screen or the always-on display.

I believe this is due to the "Show sensitive content on lock screen" setting being disabled.

Would it be possible to add a checkbox on the action that allows users to specify whether a particular notification's content should be treated as sensitive or not?

I have attached screenshots of my lock screen both with and without the sensitive content setting enabled for reference.

Having some kind of indication that there are variables Task/Profile/Project - Sometimes coming back to an old project you don't remember if you had your variables as a Task/Profile/Project.

So just like you have the "Show Linked Projects" action on each task, I would like a similar action that shows which other tasks are calling the selected task (i.e. tasks that call this task from the "Perform Task" action). 

You could call this "Show Linked Tasks". :)

I know this can be done from the search option by entering the name of the task, but this is cumbersome and shows a whole lot of other noise than I want to see.

Additionally, i suggest to put the values of variables under its names instead of right from it (on the "Vars" tab), because these can be long as well and it would be more easy to read if they take whole width of the screen.

I hope this can be implemented, i think, it will make the UI much more comfortable.

This would also be a great way to share complex tasks while providing an easy configuration method for non-advanced users.

1. Labeling an action.
2. Commenting projects, profiles, and tasks.
3. Explain projects, profiles, and tasks.

1. Google Cloud Payment rejected my debit card.
2. Open Router has very limited free tier.

Open AI accepted the same debit card rejected by Google and the free tier credit is also far more generous than Open Router. People can opt in to give away their data as well to upscale the daily limit.

This is just personal choice at this point but I like their dashboard and credits balance as well. I top up $5 into my balance and limit $1 for monthly usage. I never hit my limit, but just in case If I ever go wild.

I think it would be helpful to auto-hide a lot of those Actions (or even Action Groups, like `Zoom` or `Matter Home Automation`. 

How I envisage this working

When presented with the `Select Action Category` or `Select ____ Action` windows, long-clicking an option will give a small dialog asking if the user would like this Action/Category to be hidden by default. A visually distinct `Show All` button at the bottom of the list will, when clicked, reveal all the options that have been hidden. 

Why this would be helpful

Two immediate reasons - first, by auto-hiding a heap of the outdated or rarely-used Actions/Categories the initial learning curve could be lessened. I have a vague memory that there's a Simple Mode to Tasker which I think this is meaningfully distinct from this (can elaborate on why if that's a sticking point). 

The second big advantage is that it discourage usage of old Actions that receive less support, so might reduce bugfix requests/calls for help from users who are inadvertently trying to, say, get their location using `Get Location`, not `Get Location V2`. 

This also means Actions that have been supplemented by a feature in AutoTools could be filtered out, and AutoTools features that have been essentially ported into the main-app could also be filtered out. I do often find myself wondering whether AutoTools has the more recently-implemented version of a thing I'm trying to do, though maybe that's just me? 

Finally, as a bonus, combining it with this feature request could be an incredibly powerful move, allowing Tasker users much more flexibility.