This is problematic upon first execution, if user hasn't yet created a .taskrc config file (or had it created by task), he may just conclude that vit just doesn't work and abandon altogether.

On startup, if no .taskrc file is available, task then generates one, upon user confirmation.
Would you like a sample /path/.taskrc created, so Taskwarrior can proceed? (yes/no)

Reproduce: execute TASKRC=/path/.dummytaskrc vit (you can also instead rename old .taskrc)
Vit probably expects a non-interactive/blocking reply.

A solution could be to give user control if rc file isn't found, and react accordingly when task returns (check existence of file/return code)
Alternatively, have vit create a dummy rc file itself (with or without confirmation), but it should been best left to task.