Skip to the guide text
godspeedmissioncontrol.com
Guide menu

Folders and files

What each folder and file in your mission control holds, and where the program keeps its own files on each installation.

Applies to every installation

Last updated 18 October 2026

On this page
  1. Files at the top
  2. Folders you write in
  3. Folders Godspeed keeps
  4. The program's own files
  5. On Windows
  6. On a Mac or Linux computer
  7. On the one-line server

Your mission control folder holds everything your assistant knows, as plain text files you can open in any text editor.

  • Windows: %USERPROFILE%\godspeed-v2, unless you chose another folder. The Start menu entry Open my mission control folder opens it.
  • Mac or Linux: ~/godspeed-v2.
  • One-line server: /opt/data/full-candidate/workspace, inside its container. Server commands shows how to look inside.

Your notebook shows the exact folders of your installation, including photos, files and backups, under Settings, About.

Names that start with a dot are hidden. On a Mac, press Cmd+Shift+. (full stop) in Finder to see them. On Linux, use ls -a.

Files at the top

#
  • AGENTS.md: your assistant's operating manual, with the list of your rules. It is rebuilt from rules/, so change rules as Change its rules shows, not here.
  • CLAUDE.md: one line, @AGENTS.md, so Claude Code reads the same manual.
  • README.md: notes about the folder.
  • NOTEBOOK.md: a note the notebook writes for itself. Leave it. A folder you share between computers through Git keeps the older name, FULL-ALPHA.md, for now.
  • procedures.md: everything that runs on its own, such as the routines.
  • decisions.md: one line per decision about your mission control, with the date and why. Lines are only added.
  • .mcp.json, .gitignore, .gitattributes and .claude/: settings for AI apps and for Git. On a computer the folder is a Git repository, and the installer saves everything in it once, as its first commit. .gitignore keeps .godspeed/, conflicts/ and assistant-state/history/ out of Git.

Folders you write in

#
  • profile/: who you are, your people, your projects and your voice.
  • rules/: one file per rule, with why you gave it. A new mission control has eight.
  • skills/: one folder per skill (also called recipe), each with a SKILL.md. A new mission control has 67.
  • assistant/: your extra instructions, in extra-instructions.md, once you write some.
  • inbox/: what is not settled yet, such as a question waiting for your answer.
  • dev/: your own coding projects. Their contents never sync.
  • secrets/expires.txt: when your keys run out, with names, dates and links only. Never put a key in it.

Folders Godspeed keeps

#

You can read all of these. Change them by asking your assistant or in the notebook.

  • notebook/: your notebook as readable pages, one Markdown file per note, person, fact or moment. You may edit a page's text here, but rename or move it in the notebook. Leave notebook/_system/ alone.
  • observations/: what your assistant worked out about you, one file per fact, indexed in MEMORY.md.
  • goals/: one card per goal, with each goal's nightly research in goals/research/.
  • work/: what your mission control is doing, from planned to checked.
  • forecasts/: what it expects to happen, with a date and a number.
  • ideas/: one file per idea for one of your goals.
  • due/: until 2.0.0-beta.12, things with a day attached, one file each. They are pages under notebook/Deadlines/ now. The old files are in archives/ (where your mission control folder is your own Git repository, they stay here beside one note).
  • world/: people, events and facts saved at a moment the notebook could not be reached.
  • prompts/: archive/ is your conversation archive; library/ holds prompts you keep.
  • coach/, routines/, assistant-state/: your talks and habits; the daily round's records and your journal; the assistant's own records. Each appears when first needed.
  • conflicts/: both versions of anything two machines changed at once, and the newer version of a skill you changed.
  • .godspeed/: this machine's own state: backups, the search index and a key saved in Settings. Do not edit it. Sync never copies it.

The program's own files

#

On Windows

#
  • %LOCALAPPDATA%\Godspeed Mission Control: the program.
  • %LOCALAPPDATA%\Godspeed Mission Control State: the notebook's own state.
    • installation.json: which folder and release this PC uses.
    • media\: your photos and files.
    • backups\: copies made before updates.
    • hermes-profile\: Hermes, the program that runs your assistant, with its sign-ins.
  • A Windows install made before 2.0.0-beta.11 keeps the older names of these two folders, Godspeed Mission Control Full Alpha and Godspeed Mission Control Full Alpha State, also after updating. Everything inside is the same.
  • %LOCALAPPDATA%\Godspeed\setup-log.txt: every setup run, the newest at the end.
  • %USERPROFILE%\.local\bin: the mc-* terminal commands.
  • %USERPROFILE%\.godspeed\device.env: this PC's own settings, such as which folder it uses.
  • Godspeed Mission Control among Windows' Startup apps: starts the notebook when you sign in, without opening your browser.

On a Mac or Linux computer

#
  • ~/godspeed-v2/.godspeed/integrated-runtime/: the notebook program, with versions/, version (the release that runs), backups/ (copies made before updates) and media/ (your photos and files).
  • ~/.hermes: Hermes and its sign-ins.
  • ~/.local/bin: the mc-* terminal commands and hermes.
  • ~/.godspeed/device.env: this computer's own settings.
  • On Linux, the service godspeed-integrated-notebook.service starts the notebook with the computer. On a server without Docker, godspeed-https.service or the server's own Caddy gives it its https:// address. An add-on that needs a web address of its own puts a file in /etc/caddy/godspeed-addons/.

On the one-line server

#
  • /opt/godspeed-mission-control/, readable only by root: compose.yaml (what runs), .env (your address and setup code) and install.log.
  • Three Docker volumes whose names start with godspeed-mission-control_: one holds your folder, media and the assistant's settings, two hold the certificate for your https:// address.

Something wrong or unclear? Tell us on GitHub.