Skip to the guide text
godspeedmissioncontrol.com
Guide menu

Get help

Report a problem with the right log and no keys in it, share an idea, or ask a question.

Applies to every installation

Last updated 21 October 2026

On this page
  1. Where to go
  2. Report a problem
  3. Collect the log
  4. Take out what is private

Look for your message on Problems while installing, Problems after installing and Known issues first.

Where to go

#

Problems, ideas and questions each have one place. The places on GitHub need a free GitHub account.

  • A problem: fill in the bug form on GitHub, as Report a problem shows.
  • An idea: post it in Ideas on GitHub. People vote for an idea by clicking the arrow beside it, which shows what is wanted most. If yours is there already, vote for it instead.
  • A question: ask it in Q&A on GitHub, where the answer helps the next person too.
  • No GitHub account: write to support@ownward.studio. Our own Godspeed Mission Control posts it on GitHub for you, without your name or personal details.
  • A problem someone could misuse: write to support@ownward.studio and nowhere else. It is never posted on GitHub.

Report a problem

#
  1. Open the bug form on GitHub.
  2. Say how you installed (Windows, a Mac, Linux, the one-line server or a server without Docker), your system, such as Windows 11, and your release.
  3. Paste the exact message as text, what you did just before, and whether it happens again.
  4. Add the health line and the lines from the log, with private things taken out.

A newer release may already fix it: see what changed at the top of the README.

Collect the log

#

Copy the last 50 lines or so of the log that fits your problem.

  • Windows, while installing or updating: %LOCALAPPDATA%\Godspeed\setup-log.txt. Press Windows+R, paste the path and press Enter.

  • Windows, the running notebook: service-error.log in %LOCALAPPDATA%\Godspeed Mission Control State, or in %LOCALAPPDATA%\Godspeed Mission Control Full Alpha State if you installed before 2.0.0-beta.11. If Hermes would not install, hermes-install-error.log in the same folder.

  • Mac, while installing or updating: the last lines in the Terminal window.

  • Mac, the running notebook: ~/Library/Logs/Godspeed Mission Control/notebook.log. In Finder, press Shift+Cmd+G and paste the path.

  • Linux, or a server without Docker: run the line below, with --user after journalctl if it shows no entries. For a server's web address, use godspeed-https.service, or caddy.

    Terminal
    journalctl -u godspeed-integrated-notebook.service -n 50
  • The one-line server: log in as root and run these in /opt/godspeed-mission-control:

    Terminal
    tail -n 50 install.log
    Terminal
    docker compose logs --tail 50

Also copy the line your health address shows. It holds no keys.

Take out what is private

#

Everything on GitHub is public, including reports posted for you from an e-mail. Before you share a log or a screenshot, search it for key, token, password, secret and invite, and replace what follows with REMOVED.

Never share:

  • API keys, AI sign-in codes and your Telegram bot's key
  • your password, your recovery code, or a private link that contains /setup#invite=
  • the setup code: on the one-line server, the line GODSPEED_SETUP_CODE in /opt/godspeed-mission-control/.env
  • the keys under Connect other assistants in Settings

Never attach these files, which hold keys:

  • provider.json, and anything else in a .godspeed folder
  • auth.json and .env in the folder of Hermes, the program that runs your assistant
  • /opt/godspeed-mission-control/.env and ~/.godspeed/device.env
  • a backup

Also remove notes, names and e-mail addresses that a log line quotes.

Something wrong or unclear? Tell us on GitHub.