/ok
Shorthand to confirm proposed changes in code mode.
According to the command reference, /ok is the short form of /code Ok, please go ahead and make those changes. โ any additional text you type is appended to this fixed sentence. According to the changelog, the command was introduced as a "shortcut for asking aider to go ahead with the proposed changes, with optional extra instructions".
The command fits the Ask/Code workflow described in the docs: you first discuss a change in a mode like /ask or /architect, and if the proposal works for you, a short /ok is enough instead of writing your own wording, to have Aider carry out the implementation in code mode โ comparable to the docs' note that even a simple "go ahead" in code mode triggers the implementation.
Without additional text, /ok sends exactly the fixed consent sentence; if you append your own text, according to the docs it is added to the sentence, not used in place of it.
โ WHEN TO USE IT?
Quickly approve a proposal from an Ask/Architect conversation
Type /ok instead of writing out the whole consent sentence yourself, after Aider has proposed a plan in Ask mode.
Combine consent with a short additional instruction
Type /ok but please don't change the tests โ according to the docs, the additional text is appended to the fixed consent sentence.
โ WHEN NOT TO?
You want to add fundamental change requests, not just give consent
/ok only appends your own text to a fixed consent sentence, it doesn't replace an independently formulated instruction.
Better: Use /code <your own, specific instruction>.
SOURCES
- Aider Docs โ In-chat Commands โ aider.chat
MORE COMMANDS ยท Aider