NOTE: The default branch for this repository is 'dev', which should be considered a working beta. If you want to clone a more stable version, switch over to the 'master' branch.
Release Notes: https://docs.mycroft.ai/release-notes
Pair Mycroft Device: https://home.mycroft.ai
Mycroft Chat Network: https://mycroft.ai/to/chat
Looking to join in developing? Check out the Project Wiki for tasks you can tackle!
Ubuntu/Debian, Arch, or Fedora
Run the build host setup script for your OS (Ubuntu/Debian:
build_host_setup_fedora.sh). This script installs necessary packages. Please read it!
dev_setup.sh(Feel free to read it, as well).
Restart session (Rebooting, or logging out and back in might work).
The following packages are required for setting up the development environment and are installed by
Home Device and Account Manager
Mycroft AI, Inc. maintains a device and account management system known as Mycroft Home. Developers may sign up at: https://home.mycroft.ai
By default, Mycroft software is configured to use Home. Upon any request such as "Hey Mycroft, what is the weather?", you will be informed that your device needs to be paired. Mycroft will speak a 6-digit code, which is entered into the pairing page within the Mycroft Home site.
Once signed and paired, your unit will use Mycroft API keys for services such as STT (Speech-to-Text), weather, Wolfram-Alpha, and various other skills.
Pairing information generated by registering with Home is stored in:
~/.mycroft/identity/identity2.json <-- DO NOT SHARE THIS WITH OTHERS!
It is useful to know the location of this identity file when troubleshooting any device pairing issues.
Using Mycroft Without Home.
If you do not wish to use the Mycroft Home service, you may insert your own API keys into the configuration files listed below in configuration.
The place to insert the API key looks like the following:
api_key = ""
Put a relevant key inside the quotes and Mycroft Core should begin to use the key immediately.
API Key Services
These are the keys currently used in Mycroft Core:
Mycroft configuration consists of 4 possible locations:
- Mycroft Home (Remote)
When the configuration loader starts, it looks in these locations in this order, and loads ALL configurations. Keys that exist in multiple configuration files will be overridden by the last file to contain the value. This process results in a minimal amount being written for a specific device and user, without modifying default distribution files.
Running Mycroft Quick Start
To start essential tasks, run
./mycroft.sh start. This command will start the Mycroft service, skills, voice, and command line interface (cli) using
--quiet mode in a detached screen. Output of these screens will be written to their respective log files (e.g. ./log/mycroft-service.log).
Optionally, you may run
./mycroft.sh start -v which will start the Mycroft service, skills, and voice.
You may also run
./mycroft.sh start -c which will start the Mycroft service, skills and command line interface.
To stop Mycroft, run
./mycroft.sh stop. This command will terminate all detached screens.
To restart Mycroft, run
Quick Screen Tips
screen -listto see all running screens.
screen -r [screen-name](e.g.
screen -r mycroft-service) to reattach a screen.
To detach a running screen, press
Ctrl + a, Ctrl + d
See the screen man page for more details.
start.sh to run a large number of common tasks. This script uses a virtualenv created by
dev_setup.sh. The usage statement lists all run targets, but to run a Mycroft stack out of a git checkout, the following processes should be started:
Note: The above scripts are blocking, so each will need to be run in a separate terminal session.
Activate your virtualenv.
PYTHONPATH=. python client/speech/main.py# Main speech detection loop, which prints events to stdout and broadcasts them to the message bus.
PYTHONPATH=. python client/messagebus/service/main.py# Main message bus, implemented via web sockets.
PYTHONPATH=. python client/skills/main.py# Main skills executable, loads all skills under skills directory.
Note: The above scripts are blocking, so each will need to be run in a separate terminal session. Each terminal session will require that the virtualenv be activated. There are very few reasons to use this method.
FAQ / Common Errors
When running Mycroft, I get the error
mycroft.messagebus.client.ws - ERROR - Exception("Uncaught 'error' event.",)
This means that you are not running the
./start.sh service process. In order to fully run Mycroft, you must run
./start.sh voice, and
./start.sh cli all at the same time. This can be done using different terminal windows, or by using the included
./mycroft.sh start command, which runs all four process using