Running unattended

A schedule or a watch runs with nobody at the keyboard, so nothing widens what it may do. A run works under the approval rules already in your profile, not under any file checked into the repo. Anything that would have asked you refuses instead: the run stops and the order waits on home, marked as needing you.

Try it in CodeAF

Trust is earned in a row

Every order on the /standing page shows how much rope it has. asks first means you never said what it may do on its own, so it can only tell you things. earning trust 3/5 means you gave it a licence in your own words, like the one above, and its last 3 runs came back clean. trusted alone means 5 clean runs in a row. One run that stops on a question sets the count back to 0. The count and the licence are labels, never permissions: what a run may do is still only your banked approvals, so keep anything you must review behind them.

Money, time and where the news goes

Everything standing shares one daily allowance, the same figure /budget sets, and the card says so: shares the day's $6.00 allowance. Each order also carries quiet backstops of $5 a run and 10 runs a day unless you named your own.

The first order you set up installs one small timer under your login, a systemd user timer on Linux or a launchd agent on macOS. Every 5 minutes it runs codeaf tick, which does what is due and exits, so orders fire with every window closed. /settings turns these background checks off. Nothing runs while the machine sleeps or you are logged out; on Linux the timer catches up once when the machine wakes. See Keeps working when you close it. The news lands in the conversation that asked, or in one while you were away note the next time you open that project. There is no email or phone push.

Things to build

• A morning inbox: a nightly routine whose report waits on home under since you left when you open CodeAF. Run a nightly test routine
• A weekend flake hunt: "Every 2 hours on Saturday, run go test -count=20 ./... and add any test that failed only sometimes to FLAKY.md", held to $5 a run and 10 runs a day.
• A cron job that cannot overspend: /budget 20, then call codeaf do from your scheduler: once today's spend reaches it, the job starts nothing and says why. Budgets
• A trust record per routine: write what a routine may do in its sentence, and /standing counts its clean runs, earning trust 3/5, so you can see which routines have run clean all week.

Go further