This is perhaps a bit niche, but I’d love an easier way to set a particular tab configuration when navigating to a tiddler. I think it could be particularly useful when writing documentation/demos, as we currently see tab paths like this even in the official docs:
“You can use an $action-setfield widget to set the tab states to the appropriate values!”
Yes… but the <<tabs>> macro stores its state in a <<qualified>> system tiddler by default, so unless you’ve set a custom state parameter for each tabset you want to manipulate, you have to find the appropriate state tiddler before you can do anything with it — and there’s no human-discernible pattern to the titles. I end up using custom state tiddlers for most of the tabsets I build myself, but it’s not practical to change $:/core tabs this way.
“You could just link directly to the tiddler in question…”
Sometimes! The example above could indeed be simplified with a direct link to $:/core/ui/ControlPanel/Parsing. (Thank you, Link to Tabs! How I wish you were pre-installed on TW-com.)
But I use a lot of templates, and a lot of my tabs don’t correspond to any extant tiddler; they’re just a view template providing a particular view.
“If you weren’t overusing tabs so much, you wouldn’t have this problem…”
Possible — nay, likely. 
But I don’t intend to stop.
