Skip to the guide text
godspeedmissioncontrol.com
Guide menu

Problems after installing

What to do when the chat, the notebook, your routines, Telegram or your server sign-in stop working.

Applies to every installation

Last updated 27 October 2026

On this page
  1. Chat
  2. "The connected AI account needs sign-in."
  3. "The connected AI account reached a usage limit."
  4. "The AI request failed."
  5. "Godspeed could not load its AI program (Hermes) on this computer"
  6. "The AI request exceeded the model context limit."
  7. "Model provider failed with HTTP"
  8. The notebook
  9. The notebook page does not open
  10. Search misses notes you know exist
  11. Routines
  12. The seven routines do not appear after your first goal
  13. Routines did not run
  14. A routine row says it failed
  15. Telegram
  16. Telegram stays silent
  17. "Telegram no longer accepts the key of @yourbot"
  18. A voice note gets only text back
  19. Signing in to a server
  20. You forgot your password
  21. "This setup link has expired or was already used."
  22. "Your account is already set up. Sign in instead."
  23. Sync
  24. Sync stays at pending after many notes vanished
  25. "Conflicts waiting for review"

Find your message or symptom below. If yours is not here, Get help says what to collect and where to report it.

Chat

#

"The connected AI account needs sign-in."

#

The key or sign-in that connects your AI account no longer works, for example because the key was deleted or the plan ended.

  1. Check the account on your AI company's website.
  2. Connect it again:
    • On your own computer or a server without Docker: as First setup shows. That is Settings, Your AI with your ChatGPT plan or an API key, the Hermes app on Windows, or hermes model on a Mac or Linux. Your chat and your routines both use it.
    • On the one-line server: in your notebook, Settings, Your AI, choose ChatGPT (sign in with your ChatGPT plan) to sign your plan in again, or connect a key. Or send /model to your bot and switch to another AI you set up.

"The connected AI account reached a usage limit."

#

Your AI company stopped answering for now. Wait until your plan's limit resets, or add credit with that company. A backup AI keeps the work going meanwhile.

"The AI request failed."

#

Your AI did not answer, for a reason the notebook could not name. The details stay on your own machine, and nobody is sent them.

  1. If you have not connected an AI yet, do it as First setup shows.
  2. Try again in a moment.
  3. On your own computer, connect again and choose the next model in the list. Not every ChatGPT plan can use every model.
  4. If it keeps failing, collect the logs as Get help shows.

"Godspeed could not load its AI program (Hermes) on this computer"

#

Hermes, the program that runs your assistant, did not start for an add-on, or for Check now when you have a backup AI. No AI was asked, so your AI account and its limits are not the cause. When a part Hermes needs is missing, the message names it, for example "the Python module ruamel is missing".

On a Mac or Linux computer, or a server without Docker:

  1. Open a terminal as the account that installed Godspeed.
  2. Type hermes and press Enter. When Hermes cannot start, it prints why.
  3. If a chat opens instead, type /quit and press Enter.
  4. Report it as Get help shows, with the message and what hermes printed.

On Windows or a server installed with the one-line command, report it as Get help shows, with the message.

Once Hermes starts again, Godspeed finds it by itself the next time it asks.

"The AI request exceeded the model context limit."

#

You asked about more text than your AI model can read at once. Ask about fewer notes, or a shorter text.

"Model provider failed with HTTP"

#

The AI you connected under Settings, Your AI refused a request, such as the form's own test. The number says why:

  • 401: the key was not accepted. Copy it again from your AI company and paste it whole.
  • 404: the address or the Model is unknown. Check both in your AI company's documentation.
  • 429: your account is out of credit or reached a limit.
  • 502, 503 or 504: the AI company's service had a passing fault. Godspeed already tried twice more before it said so; try again in a few minutes, or pick another model.

The notebook

#

The notebook page does not open

#

The notebook is not running.

On Windows

  1. Choose Open my notebook in the Start menu. If the notebook is not running, this starts it and then opens it in your browser. Right after the computer starts, this can take a few minutes.

  2. If it still does not open, restart the computer.

  3. Choose Open my notebook again.

  4. If that does not help either, press the Windows key, type PowerShell and press Enter.

  5. Paste this line and press Enter:

    PowerShell
    powershell -NoProfile -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\Godspeed Mission Control\start-notebook.ps1"

    If you installed before 2.0.0-beta.11, your folder is still called Godspeed Mission Control Full Alpha, also after updating. Use that name in the line.

  6. The notebook opens in your browser. The window may show a line that starts with {"wired":true, which is normal.

If it says "The notebook did not start.", see that entry. If it says a file cannot be found, run GodspeedSetup.exe again.

On a Mac

Log out of your Mac and log in again, or restart it: the notebook starts by itself. To start it again without logging out, run this in Terminal:

Terminal
launchctl kickstart -k gui/$(id -u)/com.godspeedmissioncontrol.notebook

If it says "Could not find service", run the installer again. If it stops again, Get help shows its log.

On Linux or a server without Docker

Terminal
sudo systemctl restart godspeed-integrated-notebook.service

If you installed without sudo, run systemctl --user restart godspeed-integrated-notebook.service instead. If it stops again, Get help shows its log.

On the one-line server

Log in as root and run this:

Terminal
cd /opt/godspeed-mission-control && docker compose up -d

If the page still does not open, docker compose logs --tail 50 in the same folder shows why.

Search misses notes you know exist

#

Open Settings, scroll to Recovery and click Rebuild search.

Routines

#

Routines are the jobs Godspeed does by itself at set times. Your first goal starts seven of them, listed in Settings under Routines.

The seven routines do not appear after your first goal

#
  • You installed before 17 October 2026. Update to the newest release. On a mission control set up from 8 October on, Godspeed then adds the seven by itself, on the machine that runs your routines.
  • On a Mac or Linux computer, you used Hermes before Godspeed. Routines you made in Hermes earlier keep the seven away, so Godspeed never mixes its routines with yours. Each machine decides this once, at your first goal.

To keep this from happening on a new installation, list your own Hermes routines before your first goal, and remove the ones you no longer need:

Terminal
hermes cron list --all
Terminal
hermes cron remove <job id>

Without the seven you can still ask for the same work in the chat, for example "research my goal run 10 km now" or "decide today". Coaching talks and the evening habit check need the seven and do not run without them.

Routines did not run

#
  1. Check that you have a goal: the Goals page in the sidebar.
  2. Under Routines, look for a row that says "Paused. Nothing runs until you resume it." Click Resume.
  3. On your own computer, routines run only while the computer is on and the notebook runs. Run due routines runs everything that is due now.
  4. With more than one machine, only one runs the routines. Settings, Sync and schedule ownership says which.

A routine row says it failed

#

The row says "and it failed" with the reason, or "it could not start". Open Settings, Your AI and click Check now: it asks your AI the way a routine does. If the routines cannot reach it, connect it again as First setup shows.

Telegram

#

Telegram is only on the one-line server.

Telegram stays silent

#
  1. In the notebook, open Settings and find Telegram. When it works, it says "Telegram is connected."
  2. If it says setup is running in your chat, answer your bot's questions there first.
  3. Write from the Telegram account that pressed Start in your bot. The bot answers only its owner.
  4. Routine results reach Telegram while it is connected, unless Settings, Routine delivery says Keep results here. A routine with nothing to say sends nothing.
  5. A routine row that says "It worked, but its message could not be sent." means Telegram did not take the message. Check steps 1 to 3.
  6. If the bot answers nothing at all, check that the server runs, as Check that it is running shows.

"Telegram no longer accepts the key of @yourbot"

#

Telegram stopped accepting the key your server has for your bot.

  1. In Telegram, open BotFather, send /token and choose your bot.
  2. Copy the key it shows.
  3. Paste it into Your bot's key under Settings, Telegram, and click Check and connect.

A voice note gets only text back

#
  1. Send /voice status in the chat.
  2. If it answers "Voice mode: Off (text only)", send /voice on.

With your own voice from ElevenLabs, also:

  1. Open Settings, Voice replies. It names the last problem with the voice, for example used-up ElevenLabs credits or a key ElevenLabs refused.
  2. Fix that problem in your ElevenLabs account, for example by buying credits or making a new key.
  3. If you made a new key, paste it into ElevenLabs key.
  4. If it says ElevenLabs does not know the voice, paste the voice's ID from its page at ElevenLabs into Voice ID.
  5. Click Make a sample and save again.
  6. Press play on the player that appears. When you hear the sample, the voice works.

The text always arrives meanwhile. More on Talk to it with voice notes.

Signing in to a server

#

You forgot your password

#
  1. On the sign-in page, click Forgot your username or password?.

  2. On Recover your account, enter the recovery code you saved when you made your account.

  3. Choose a new username and password.

  4. Save the new recovery code you get. The old one stops working.

There is no reset by e-mail, and without the recovery code there is no way back in from the browser. Your notes on the server are not affected. Ask for help as Get help shows.

#

The private link that makes your account works once, within 24 hours.

  • If you already made your account with it, sign in instead.
  • Otherwise run the install command again on the server. It keeps everything on the server and prints a new link.

"Your account is already set up. Sign in instead."

#

Sign in with the username and password you chose. If you did not make the account, someone else opened your private link first. Reinstall the server from scratch and keep the new link to yourself.

Sync

#

Sync keeps your notes the same on several machines through a private GitHub repository, set up under Settings, Sync and schedule ownership.

Sync stays at pending after many notes vanished

#

When one machine removes more than 25 records of one kind at once, and more than a fifth of them, sync stops that removal. Settings then shows only "Sync: pending".

  • On the machine where they vanished: if it was a mistake, put the files back from the Recycle Bin or the Trash. To remove notes, delete them inside the notebook, and sync passes that on.
  • On a machine where the removal arrives: it waits under Review conflicting edits. Keep the records, or accept the removal.

"Conflicts waiting for review"

#

Two machines changed the same thing, or an update met a built-in skill you had edited. Under Review conflicting edits in Settings, choose which version to keep.

Something wrong or unclear? Tell us on GitHub.