So far that experiment is going pretty well! I haven't worked much on it but the tooling I'm using has made a great base for the project. My goals (in order of priority) are:

- Get it so that you can categorize transactions quickly in a keyboard-driven way

- Similarly have a quick, improved option for dealing with overspending / underfunding

- Add some additional reporting that I'd like to see (as well as the ability to drill down in a more fuzzy way than currently supported in ynab)

- Finally (and most importantly but also most ambitiously) develop a view with some simple tools that helps users figure out WTF is wrong when a reconciliation isn't working out. This is much harder than the other things I'm trying to do here

Luckily YNAB's API is very open and I think I can do all the things I'm looking to achieve here. If I'm successful, I plan to spin off a sister TUI project for making handling import edgecases easier in beancount, which I also use but for different reasons

Edit: but your idea of having CLI command options for printing reports on a regular basis / on opening the shell is also neat, I do plan to have some CLI options that don't require you to open the full TUI