oah helps you build an AI development workflow that fits you and keeps changing as AI improves. It is a working reference and a guide you can adapt.
A useful result needs more than generated code: the scope must be clear, the changes checked, and decisions kept for the next session. oah connects those steps so one request can carry through the work with a record of what happened.
002 / Why it keeps changing
Older rules and skills can hold a newer model back or make its results worse. Defaults should be easy to understand and change; a rule that gets in your way is a design problem to fix.
Keep the parts that help, remove what no longer helps, and revise the workflow as your tools improve. You can start with the full setup or take only the impact map, wiki, leases, evidence gates or review loop that your project needs.
003 / Why Claude builds and Codex reviews
This split comes from the author's own experience, not a measured comparison: Claude fills in details a beginner might miss in a first version; Codex checks and corrects within a fixed scope.
The current commands run Claude Code and Codex CLI. The ideas can also be adapted to another tool or harness, with one AI or several. Give each stage to the AI that suits your work.
004 / From one request to a checked change
Describe the result you want in plain language. The AI records the goal and scope, checks what the change touches, reserves its paths and chooses the tools for the task. Claude builds; Codex reviews, corrects and reviews again.
Gates record the checks and their results. The project wiki keeps the decisions and reasons beside the code. In v0.3.0, optional TypeSafe Jev can judge difficulty for model selection; rules remain the fallback when it is unavailable or uncertain.
005 / The decisions stay with you
You ask, answer when the AI needs a decision, and confirm before the change lands. If the same problem repeats or the work reaches a design choice, the loop stops to ask you.
Ask “Is the review done?” or “Did all the gates pass?” and inspect the evidence. The final confirmation belongs to you; writing code, checking it and approving its landing are separate steps.
006 / Free, open source, yours to adapt
oah is free, open-source software under the MIT license. Read the source, change it and bring the useful pieces into your own workflow. Your AI services and any optional services use their own accounts and billing.
The current v0.3.0 release supports macOS and native Windows, and expects familiarity with git and pull requests. Install it, run oah init in your project, then try the small hello-oah example. The installation and documentation sections explain each step.
oah init creates docs/wiki/, an Obsidian-compatible folder where your AI keeps the task history, decisions and reasons beside the code. oah wiki maintain writes each task's log entry and index line, oah finish checks that it ran, and the next session has a record to read instead of asking you to explain everything again.
When you need it
A new AI session starts with no memory of why things were done, so you explain the same decisions again and the reasons behind older changes get lost.
How it works
oah init creates docs/wiki/ with index.md (catalog by category), log.md (newest first), log_archive_NN.md files and note and decision templates.
oah wiki maintain --task T writes the task's log entry and index line before the final commit, the gates and the review, and again after corrections. Running it twice adds nothing twice.
oah finish only checks that it ran, and refuses with OAH_WIKI_MAINTENANCE_MISSING when it did not.
Above 512,000 bytes, the oldest whole entries move to the next log_archive_NN.md; each move is journalled.
oah wiki lint and oah wiki hygiene report broken links, unindexed notes, missing sources and other real problems.
Example
The folder `oah init` creates (from Concepts).
docs/wiki/
index.md catalog by category
log.md newest first, below <!-- OAH:LOG_INSERT_BELOW -->
log_archive_NN.md older whole entries, moved by rollover, never edited
templates/ note and decision templates
Requirements
Created by oah init; nothing else to install.
graphify is optional (oah graph).
Limits and recovery
Lint and hygiene list candidates only: no wiki command deletes or moves a note on its own.
If a file changes during a log rollover, wiki commands stop with OAH_WIKI_RECOVERY_PENDING until you run oah wiki recover.
Nothing rebuilds the graphify graph automatically.
--allow-missing-wiki-maintenance skips the finish check and is recorded.