Gopherbot logs in to your team chat like a normal user, and can respond to CLI-like commands for interacting with infrastructure. Since Gopherbot relies heavily on external shell utilities and scripting languages (python, ruby, bash) for adding functionality, it's strongest use case is kind of a "super CRON", running jobs on a schedule or on demand, and reporting any problems in your team chat. It can be used with strongly-encrypted secrets to run ansible playbooks or python/ruby/curl scripts interacting with remote APIs. Other use cases include manually triggering software deployments, or updating a status message on your company's website. If you have a collection of scripts for doing this kind of thing, and have ever wished you could trigger these scripts in your team chat, chances are good Gopherbot is the tool for you. You can find a lot more information in the introduction of the online manual. Gopherbot uses a model similar to Ansible, distributing a core robot with an array of built-in functionality. Individual robots are configured and stored in a git repository that is cloned during the robot bootstrap process; several example robot repositories are given below.