Skip to content

Let a machine stop itself

A machine nobody is using is a machine you are paying for. A machine with auto-stop on stops itself when it has been idle, so the meter stops too, and it warns you before it does.

Auto-stop ships off. Nothing starts stopping machines until somebody turns it on.

In Machinery, open Settings, then the Power section. Turn on the idle alarm and auto-stop.

A single machine departs from the account’s answer on its own Power tab.

Both switches must be on. The idle alarm is what notices a machine is quiet, and auto-stop is what stops it, so a machine with auto-stop on and the idle alarm off never stops itself.

A machine counts as idle when it stays under both of these, for a while:

  • a CPU percentage
  • a network rate

An open ssh session keeps it busy, and so does a terminal session, or Mecha while it works on a task. Every other kind of work counts as use only through the two ceilings, and both of them ship unset. Set them if your machines run builds, serve traffic, or run jobs with nobody attached:

Terminal window
deployport machinery account-settings set-power --idle-alarm-enabled true --auto-stop-enabled true --idle-alarm-cpu-max-percent 20 --idle-alarm-network-max-bytes-per-second 100000

Before it stops, the machine gets a warning. While the warning is showing, a developer can keep it running:

Open the machine and choose Keep running for…, then pick how long and choose Keep running. A longer request than the account allows is shortened to the cap, and the dialog says so. Choose Clear beside the suppression to give it back.

The longest suppression anyone may ask for is an account setting. It ships with no ceiling at all, which means nobody may keep a machine running past an idle stop until an operator sets one:

Terminal window
deployport machinery account-settings set-power --auto-stop-suppression-max 4h

A machine cannot raise that ceiling, because a ceiling a machine may raise is not a ceiling.

Terminal window
deployport machinery list

The AUTO-STOP column reads on, off, or waiting for the AI harness to finish a task while Mecha is working. The suppress command prints the time the machine runs until, so machine <machine-id> keeps running until <time>. is the confirmation.

They live under the power domain:

pathwhat it sets
power.idleAlarm.enabledwhether the machine works out that it is idle
power.idleAlarm.idleForSecondshow long it must be quiet before that counts
power.idleAlarm.cpuMaxPercentthe CPU ceiling for idle
power.idleAlarm.networkMaxBytesPerSecondthe network ceiling for idle
power.autoStop.enabledwhether an idle machine stops itself
power.autoStop.headsUpEnabledwhether a developer is warned before it stops
power.autoStop.headsUpSecondshow long the warning shows first
power.autoStop.suppressionMaxSecondsthe longest suppression a developer may ask for

Set what every machine inherits writes these for the account, and each machine’s own Power tab writes them for that machine.

A stopped machine keeps its disk, and connecting to it starts it again:

Terminal window
deployport machinery ssh <machine-id>

That is the whole point of the pairing: stopping costs nothing while it lasts, and reaching the machine again is one command.