Houston docs

Scheduled runs

Ask the agent for a recurring (or one-time) background run, such as "every morning at 9, run the tests and summarize failures", and it stores a schedule with schedule_run. At each occurrence, a fresh session starts with the stored prompt, under the approval policy of the chat that created it.

Schedule formats

All times are local.

  • every <N>m|h|d (minimum 5 minutes)
  • daily at HH:MM
  • weekdays at HH:MM
  • weekly on <day> at HH:MM
  • once at YYYY-MM-DD HH:MM

Managing schedules

  • list_scheduled_runs shows what's configured, with next and last fire times.
  • cancel_scheduled_run removes one.
  • Creating or cancelling a schedule asks for approval.

When they fire. Schedules survive restarts and fire while Houston (the desktop app or the terminal) is running. It's an in-app scheduler, not OS cron: an occurrence missed while Houston was closed fires once at the next launch.