CodeAFSchedules

Schedules

Say when, and the work happens then, every time.

Give your agents a calendar. Work happens at the time you named, not when you remember to ask.
  • every night at 2, run the suite and fix what broke
  • every Monday at 9, triage the new issues
  • remind me at 6 to check the release notes

A schedule is a standing order that wakes on your clock. Say the time the way you would to a person, such as "every Monday at 9" or "every 15 minutes", and the card reads it back in words: Mondays at 9am. Each run is real work: a brief carried out in the project by a worker of its own, with its own transcript and its own cost.

Try it in CodeAF

Where

In a conversation in your repo.

Type
Every night at 2am, run go test ./... here, fix the easy failures and write what you did to MORNING.md

Then press Enter.

You see

The card reads wants to set up a repeating check. Press 1, Set it up, with the time in words beside it, and the schedule stands.

Routines that earn their keep

A nightly sweep that runs the suite, files an issue per failing test, fixes the real bugs and has a morning report waiting. Its fixes land as uncommitted edits in the project folder, not on a branch, ready for you to look over. A Monday triage that drafts the list of new issues for your planning meeting. A cheap lint pass every 15 minutes: say "using openai/gpt-oss-120b" in the sentence and that routine runs on that model, whatever the rest of the project uses. 3 on the card runs it once now, before it repeats.

Reminders

Say when and press Enter, 1 sets it up, and the reminder arrives on the pass after that time. Keys: Remind me in 3 minutes to check the release notes.Enter1

A reminder is the smallest schedule: one moment, one line, then it retires. "Remind me in 3 minutes to check the release notes" gives the card wants to remind you, with 1 Remind me in 3 minutes and the clock time beside it, or 0 Don't remind me, and at that time the line Reminder: check the release notes. arrives in the conversation that asked.

When it runs

Everything standing is checked on one pass every 5 minutes, so a run can start up to 5 minutes after the time you named. The pass runs from any open window; with every window closed, a background timer keeps it going. See Keeps working when you close it. What a run finds waits in the conversation that asked, or on home under since you left.

Things to build

  • A nightly sweep: "Every night at 2am, run the suite five times, write an issue per failing test, fix the easy ones and write MORNING.md." Run a nightly test routine
  • A 15-minute vet on a cheap model: "Every 15 minutes, run go vet ./... here and fix what it reports, using openai/gpt-oss-120b": that routine runs on that model, about 8 cents a run in our test.
  • A Monday triage list: "Every Monday at 9, read the open issues in ISSUES.md and write TRIAGE.md ranked by how much they block." It is ready before planning.
  • A release-day reminder: "Remind me at 6 to check the release notes", and the line arrives in the chat that asked.

Go further

Run a nightly test routine: Every night the suite runs, failures become issues, easy bugs get fixed, and a report waits for you in the morning.

Coming soon: describe the org you want and CodeAF builds it: teams, managers, budgets, standing orders.