I did tell you to try "command history" on the same line I told you about events.tail(). You can pass a string argument to events.tail() to filter it (which works even better in the beta/next version). I'm considering modifying the events.tail() behavior to filter / differentiate human-triggered events vs machine triggered events, which should clean up the default output a bit. One of the things I'm strongly considering for the next release is a "subtitle" feature that's enabled by default to tell you what is recognized.

The wiki is something I currently try to introduce folks to later in the process, because it's unofficial and historically has had assumptions, inaccuracies, or very outdated information that caused me additional stress/support load. I know the community has been working on improving that.

Bluetooth mics are almost universally worse than cheap wired mics, due to bandwidth/power/compression constraints. If you make a file user/settings.talon containing "settings(): speech.record_all = 1", Talon will record successful utterances to recordings/ adjacent to user/, and you can compare what the mic sounds like to Talon. It's also very likely the mic works better with Conformer.

The alphabet is pretty easy to change. Check out the top of keys.py. There are some words that aren't really the engine's fault when it comes to accent, and some pairs like air/near are more of a configuration issue if your accent doesn't differentiate them.

I'm hoping to release v0.2 with Conformer sometime around July 1