Check that it is running
See in two minutes that your notebook runs, your AI answers and your routines do their work.
On this page
Open the health address
#The notebook is the web page where you talk to Godspeed. Its health address answers without a sign-in:
- On your own computer: http://127.0.0.1:47831/health
- On a server: your server's
https:/address followed by/ /health
A running notebook answers with a line that starts like this:
That is the version of Godspeed Mission Control you have, the same one Settings, About shows. Update Godspeed Mission Control shows how to tell whether a newer release is out. If the address does not load, see The notebook page does not open.
Send a test message
#- Open the notebook. The Godspeed card on the dashboard says Ready to chat.
- Click Chat with Godspeed and ask "What can you do for me?".
A real answer means your AI account works. On the one-line server, write to your Telegram bot too. If you get a message about your AI account instead, see Chat problems.
Look at your routines
#Routines are the jobs Godspeed does by itself at set times. Your first goal starts seven of them.
Open Settings. Under Your AI, it says "The routines reached it" with the time of its last check. If not, click Check now.
Scroll to Routines. The line at the top includes "Assistant: available."
Each routine has a row with its time and next run, such as "Runs every day at 05:30."

After its first run, the row says how it went, for example "Last ran today at 05:30, and it worked."
Each run with something to say leaves a note in Notes, in the folder From your routines. While Telegram is connected, on the one-line server, it comes to Telegram instead.
No rows, or a row that failed? See Routine problems.
See whether it runs on your installation
#Windows: the notebook starts each time you sign in to Windows.
Mac: the notebook starts each time you log in to your Mac. This shows a line with
"PID" =while it runs:launchctl list com.godspeedmissioncontrol.notebookLinux, or a server without Docker: this shows
active (running). If the installer could not usesudo, add--useraftersystemctl.systemctl status godspeed-integrated-notebook.serviceThe one-line server: log in as root and run this. A running server lists two services,
godspeedandhttps, each with the statusUp.cd /opt/godspeed-mission-control && docker compose ps
Get help shows where each installation keeps its logs.
Something wrong or unclear? Tell us on GitHub.