Features
Scheduler & machine limits
One desk decides what may start, so agents wait for the machine instead of freezing it.
Every expensive thing Station starts (a Claude session, a build, a typecheck, a test run) asks the scheduler first. When CPU, memory or disk are above your limits, it waits its turn. Two rules are never broken: nothing is killed, and nothing waits forever.
- 3
- agents at once by default, up to 8
- 10 min
- longest any job waits before starting anyway, and saying so
- 0
- processes the scheduler has ever ended
85% · hard limit ▲
Three kinds of work, three counts
Claude sessions, heavy jobs (builds, installs, typechecks) and test runs are counted separately: three, one and one by default. A command you type yourself is counted but never held; Station’s own jobs queue behind you.
Limits you can read
Above the soft CPU limit (70%) a build waits while agents still start; above the hard limit (85%) no new Claude session starts either; above the freeze limit (95%) nothing starts. Memory (80%) and disk (90%) hold separately. Each limit is a slider in Settings → Agents → Machine limits.
Quiet mode
When you need the machine back (a call, a game, a render), quiet mode stops new automatic agents, defers typechecks, and drops Station’s running processes to below-normal priority with Windows’ efficiency mode. It ends nothing, and turning it off restores everything.
Two days, every feature, no card.