Understand. Plan. Execute. Validate.
Every run moves through the same four stages — nothing skipped, nothing hidden.
This is the loop behind every Ottili Coder run, from a one-line fix to a multi-file feature.
Understand the repository
Ottili Coder reads the structure, stack, and conventions already in your codebase before touching anything.
Build an execution plan
It breaks the goal into ordered tasks and flags risks before writing a single line.
Edit and run
Files get edited, commands get run, and each step builds on the last.
Validate and repair
Tests and checks run automatically. Failures become the next task, not the final answer.
It does not stop at the patch.
Long jobs need more than one model response. Ottili Coder checkpoints its own progress with Cairn, resumes interrupted work, and keeps validation inside the loop.
- Checkpoint saved
Cairn records the goal, the plan, and what's already done after every meaningful step.
- Session interrupted
A dropped connection or a closed terminal doesn't erase the run.
- Resumed from checkpoint
Ottili Coder picks the job back up from the last known-good state, not from zero.
- Validation loop continues
Checks keep running until the result actually holds up.
Try it on your own repository.
The fastest way to understand the loop is to give it a real task.
Install Ottili Coder