A chat bot in Go, now with 100% less CoffeeScript!
"Good morning, Dr. Chandra. This is HAL. I'm ready for my first lesson."
Hal is Go all the way down, and uses standard packages wherever possible. It's a bit rough around the edges right now. For an idea of how you can use it, look at a simple example, or a more complex example. API Documentation is available here.
Hal doesn't have any command line options, instead opting to use environment variables exclusively.
PORT=9000 # The port on which the HTTP server will listen.
# Default: 9000
HAL_NAME=hal # The name to which Hal will respond.
# Default: hal
HAL_ADAPTER=shell # The adapter name.
# Default: shell
# Options: shell, slack
HAL_LOG_LEVEL=info # The level of logging desired.
# Default: info
# Options: info, debug, warn, error, critical
By default, Hal uses Slack's hubot integration. Currently Hal will listen in on all public channels. In the future, you'll be able to specify channels by either a whitelist or blacklist. Private groups require the IRC gateway to work around a current limitation of the Slack API. See Using IRC. The IRC gateway is author's prefered method as your bot will automatically join all channels and groups it belongs to, and removing Hal from a room is as simple as a /kick hal
command. Some advanced features like
Start by adding the Hubot integration for your team (if you haven't done so). Then, set the following environment variables when starting up your bot:
HAL_ADAPTER=slack # The adapter
HAL_SLACK_TOKEN=blah # Your integration token
# Default: none
HAL_SLACK_TEAM=acmeinc # Your Slack subdomain (<team>.slack.com)
# Default: none
HAL_SLACK_BOTNAME=HAL # The username Hal will send replies as
# Default: HAL_NAME
HAL_SLACK_ICON_EMOJI=":poop:" # The emoji shortcut used as the response icon
# Default: none
HAL_SLACK_CHANNELS="" # not yet implemented
HAL_SLACK_CHANNELMODE="" # not yet implemented
HAL_SLACK_LINK_NAMES="" # not yet implemented
The default integration only works with public chats. If you want hal to listen in on private chats, you must utilize the IRC gateway. You'll need a real user for hal, so be mindful of the username you choose for it and make sure you configure your bot to use that name so it can login to the IRC gateway. When enabled, hal will only use the IRC gateway to listen for messages. Hal can be configured to either respond using the API or the IRC gateway.
- Enable the IRC gateway in the admin settings interface
- Choose "Enable IRC gateway (SSL only)". You don't want your private messages sent unencrypted.
- Register a new user
- Sign in as this new user
- Capture your new IRC credentials
- Set the following environment variables
HAL_SLACK_IRC_ENABLED # Enable the Slack IRC listener
# Default: 0
# Options: 0, 1 ; 0 is disabled, 1 is enabled
HAL_SLACK_IRC_PASSWORD # The IRC gateway password
# Default: none (required)
HAL_SLACK_RESPONSE_METHOD # The method by which hal will respond to a message.
# The irc option requires that the IRC gateway be configured
# Default: http
# Options: http, irc
For more information, please see the following link:
Hal requires a user account to integrate with Hipchat. Be sure to one before configuring the adapter.
HAL_HIPCHAT_JID # Hipchat JID
# Default: none (required)
HAL_HIPCHAT_PASSWORD # Hipchat password
# Default: none (required)
HAL_HIPCHAT_ROOMS # A comma-separated list of rooms to join
# Default: none (optional)
Set the following environment variables when starting up your bot:
HAL_ADAPTER=irc # The adapter
# Default: shell
HAL_IRC_USER=blah # IRC username
# Default: none (required)
HAL_IRC_PASSWORD=sekret # IRC password if required
# Default: none (optional)
HAL_IRC_NICK=hal # IRC nick
# Default: HAL_IRC_USER (optional)
HAL_IRC_SERVER=irc.freenode.net # IRC server
# Default: none (required)
HAL_IRC_PORT=6667 # IRC server port
# Default: 6667
HAL_IRC_CHANNELS="#foo,#bar" # Comma-separate list of channels to join after connecting
# Default: none (required)
HAL_IRC_USE_TLS=false # Use an encrypted connection
Hal comes with a default shell adapter, useful for testing your response handlers locally. It has no special configuration variables.
Please use the issue tracker for development progress tracking, feature requests, or bug reports. Thank you! ❤️