Runtime Quickstart
Install the Oathe runtime, onboard your harnesses, and hand a task from Claude Code to Codex in five minutes.
The Oathe runtime keeps agent work durable, transferable, and verified. This guide takes you from install to your first cross-harness handoff.
Requirements
- Node ≥ 22
- A running Postgres
Install
npm install -g @oathe/oathe
cd your-project
oathe init # local substrate up (createdb + schema), installed harnesses onboarded
oathe claude # a normal interactive session — the board shows, nothing auto-resumes
Ctrl-C anytime. Open oathe codex in the same folder — same board, same claims, other harness. oathe uninstall removes exactly what init recorded.
The claim loop
You can let the harness drive through the oathe_* MCP tools, or make the loop explicit from the terminal:
oathe claim fix-login "users can sign in again"
oathe note fix-login "found the stale token check"
oathe done fix-login "guard rewritten, test added" src/auth.test.js
oathe verify fix-login # a NON-author engine judges it from recorded session traces
oathe ls # the board
Two rules carry most of the weight:
- Tasks outlive agent processes. Death of an executing agent just creates a new attempt.
- No agent grades its own homework. “Done” is a claim; verification by a non-author closes work.
Next
- How a handoff works
- How verification settles work
- The repo, roadmap, and honest status labels: github.com/oathe-ai/oathe