That's interesting. If I could suggest one feature, maybe a time of day span window when the task can fire? Like, be able to set it to only fire on idle if between 2 AM and 4 AM type of thing?
I think this application is best kept as-is, in order not to frustrate myself or others.
IdleStart is very simply designed. It doesn't store any settings to the registry or to any type of config file. Everything is passed as a command line parameter. This way, one single copy of IdleStart can be used simultaneously for multiple applications with different parameters for each one.
If I save the times to run to the registry or a config file, it would either lose the ability for multiple instances to run with different configurations, or become a complicated mess requiring me to code the whole thing over from scratch and plan it much differently.
And I think adding more command line parameters might make it more confusing for users to use, with more potential for it not to do what they expected, no matter how good my instructions are.