Right now wisteria's interface for composing messages within the TUI just allows you to type some text and send it. The cursor is locked to the end of the message that you're composing. If you need to add a word at the beginning, you have to erase everything after it and retype it. This is really because I built the editor on top of the existing TextArea widget, which doesn't allow getting the current cursor position from higher-level logic. If we knew where the cursor was in the editor code, we could implement this properly. I think the proper fix is to either modify the textarea widget to give us the access we need to its internal state, or to re-implement the editor without using views.TextArea as the basis.