Skip to the guide text
godspeedmissioncontrol.com
Guide menu

The safeguards your assistant keeps

Five checks that keep your assistant from giving up early, handing you homework, posting in your name, missing a promise or cluttering your folder.

Applies to every installation

Last updated 13 November 2026

On this page
  1. It asks itself once whether it is really finished
  2. It never hands you a page with blanks to fill
  3. It drafts posts, but is stopped from posting in your name
  4. A promise on a clock is written down
  5. It is sent back when it adds something at the top of your folder
  6. Where the checks run
  7. Related

Your mission control comes with five checks that watch your assistant's work. They are small programs that run at the right moment, so they do not depend on the AI remembering a rule.

It asks itself once whether it is really finished

#

Your assistant may be about to end a turn with a message that gives up ("I can't do this") or hands the work back. The check then asks it once: show that the work is done or truly impossible, or carry on. A message that asks you before a step that cannot be undone always passes.

It never hands you a page with blanks to fill

#

Your assistant does not publish a page with an empty answer column, and does not end by sending you to a link to fill something in. A plain question you can answer by typing a reply is fine.

It drafts posts, but is stopped from posting in your name

#

Your assistant may draft posts, comments and replies. It cannot publish, schedule or queue one on a social platform in your name: you post, it prepares. The check refuses the posting tools and posting addresses of platforms it knows, such as LinkedIn, X, Facebook, Instagram, Reddit and TikTok. It also refuses a click on a button named Post, Publish, Share, Tweet or Schedule. Reading your history and statistics, cancelling a scheduled post and drafting stay allowed.

A promise on a clock is written down

#

When your assistant promises something on a clock ("I'll send you this every Sunday"), the promise becomes a file in the work/promises/ folder of your mission control. Setting up a routine writes its promise there too, when its schedule is one it can write down. Every morning each promise is checked, and a missed one is named at the top of your morning brief and of mc-due today until a later one is kept. If a turn ends with a recurring promise such as "every Sunday" and no file, the assistant is asked once to write it down.

It is sent back when it adds something at the top of your folder

#

A new file or folder at the top of your mission control sends your assistant back once, at the end of its turn. It is asked to move the thing into the folder where it belongs, remove it, or ask you. Anything that was already there, anything Git already tracks and anything you named in a message, such as "make a folder called garden", is never questioned. The check works in a mission control that is a Git folder with an AGENTS.md at its top.

Where the checks run

#

The checks run automatically when you use Godspeed through Claude Code or Codex (Use Godspeed in VS Code, Claude or Codex). Codex runs them only in a folder you have trusted: approve the folder's hooks with /hooks once.

Hermes, the program behind your Telegram chat, has no moment where a check can step in. It follows the same instructions, but these five checks do not watch it. The morning check of your promises covers every way of talking to Godspeed, and Godspeed separately checks every hour that your Telegram chat answers.

#

Something wrong or unclear? Tell us on GitHub.