Standing orders
Some of what you say is for right now. Some of it is meant for always.
Say it once. It stays true after the conversation ends.
- security fixes always go to the strongest model
- every night, run the suite and fix what broke
- tell me when a file in docs/ changes
A standing order is the always-on layer of CodeAF: something you said once that keeps being true after the conversation ends, until you stop it. You say it in your own words, in any conversation, and CodeAF keeps it without being asked again. Your chats read your rules on every turn; a task gets only a rule's model choice.
Try it in CodeAF
- Where
In a conversation in your project.
- Type
/standing always write Go doc comments in full sentencesThen press Enter.
- You see
A card reads
wants to keep a rule. Press 1 and the rule stands for every conversation in that project.
One object, four ways to wake
There is no rules engine and no macro language. Rules, reminders, schedules and watches are one kind of thing that differ only in what wakes them. A rule never wakes: it rides into the work. A reminder wakes once, at a moment. A schedule wakes on a rhythm and runs a piece of work. A watch wakes when something changes, the output of a command or a file, or when the machine goes quiet.
CodeAF tells an order from an instruction with one question: can this be satisfied once and then forgotten? "Make sure this page has three sections" is finished when the page is. "Make sure the tests never break" can never be finished, so it stands.
Nothing stands until you say yes
Every order arrives as a card with your sentence, when it wakes and how far it reaches: this conversation, this project, or everywhere on the machine. 1 sets it up, 0 declines, o lets you say a different time or place, and a card nobody answers sets up nothing. If a sentence is taken as work to do now, send it again as /standing <words> and it can only be read as an order.
/standing opens one page with every order on the machine and what each last found. Press → on a row for p pause and s stop, or just say "stop the docs watch" in any chat.
Things to build
- A red-main pager: a watch on
go test ./...that fixes the code when a test fails and tells you in the chat in one line. Keep main green - A nightly sweep: every night the suite runs, each failing test becomes an issue file, easy bugs get fixed, and MORNING.md waits for you. Run a nightly test routine
- A docs change feed: "Whenever any file under docs/ changes, tell me which one and summarise the change in one line."
- A model policy: "Security fixes in this repo always run on openai/gpt-oss-120b": the chat hands those tasks to that model and the rest keep the usual crew. Rules
Go further
Keep main green: A watch runs the tests on a schedule, and when they go red, a worker fixes the code and tells you in one line.
Coming soon: describe the org you want and CodeAF builds it: teams, managers, budgets, standing orders.