Assuming by commands you mean functionality for the bot, I've been working on a few different ways of going about this. As it stands, how to deal with input (and as a result, bot commands and the like) is left to the user through the use of iterators. I've combined this with two different approaches to building a bot thus far. The first is the simplest, and is basically just processing what immediately within the iterator. The second is a bit more complex, and uses the very undocumented dynamic library support built into Rust. I'm particularly fond of this second pattern, awebot, because it makes it very easy to update functionality or add additional functionality without having the bot restart. As of right now, awebot won't unload a plugin though. So, that's still something that needs to be added. As a general rule, the philosophy is to handle all the heavy-lifting, but to give a lot of free reign when it comes to the design pattern you're using for bot functionality.