Harness — a personal agent platform
1. Thesis
FridaiOS — my day-to-day operating harness — is a personal agent platform with the same shape as an organisational agent deployment: one knowledge source of truth, skills as portable verbs, staged workflows with human gates, and observability and cost governance running underneath. I built it to run my own work, which means every piece of it has been exercised against real, messy tasks rather than a demo dataset.
2. Components
- A skills registry with a documented contract, so any skill can be composed into any workflow predictably
- A workflow dispatcher with explicit run-state semantics — ok / skipped / partial / failed / paused — rather than a binary success/fail
- A multi-provider model router with schema-validated retries, so a malformed response gets retried or escalated rather than silently breaking a downstream step
- An append-only token/cost ledger, so spend is auditable rather than estimated after the fact
- Retrieval with golden-case regression tests, so changes to the retrieval layer can't silently degrade answer quality
- Session harvesting from agent transcripts, turning working sessions back into durable knowledge
- A systemd file-watcher for event-driven runs, so workflows can trigger on filesystem events rather than only on manual invocation
3. Claude Code maturity
Claude Code has been my daily driver since early 2026. Between April and July 2026 I put ~430 commits across 9 self-directed repos through it — skills, hooks, and MCP-client orchestration running in production personal use, not a one-off proof of concept. The platform pages on this site (this one included) were themselves built through that harness.
4. Equivalence
A fair question is whether a skills-and-hooks harness built on Claude Code is doing fundamentally different work from a graph-based orchestration framework like LangGraph, or whether the two are equivalent architectures wearing different clothes. I've written up that comparison in detail: the LangGraph equivalence brief.
For the underlying engineering — the router, the workflow dispatcher — see the exhibits directly: