Oakridge
A workspace for agent-driven software development
Oakridge organizes software work into durable workflows, stages, artifacts, and review. Its operator workspace brings agent sessions and their outputs together so the human can inspect the work and decide what happens next.
Oakridge organizes agent-driven software development around explicit workflows and reviewable artifacts. Its operator workspace connects the active run, agent sessions, and outputs so the human can assess progress and direct the next stage.
Durable work, structured handoffs
Asynchronous software work needs more than an agent transcript. A human returning to a run needs to see the stage, the outputs it produced, and the decision needed to move forward. Oakridge makes workflow definitions, stages, artifact contracts, and review policy explicit so handoffs retain that context.
DBOS handles durable execution, recovery, fan-out/fan-in, and waits. Oakridge owns the domain workflow and operator projections. Runs organize stages; executor adapters connect stages to agent sessions; artifact contracts define the outputs to inspect; review policy controls the next transition.
The operator workspace
The operator PWA and current interactive Claude Code executor are provided through kbbl. The workspace brings sessions and run outputs together for review. Stage instances remain execution-agnostic, while adapters sit beneath the durable workflows. A headless integration is a future surface; the current source does not establish generic support for every executor.
What to inspect
Start with the repository layout and quick start, then examine the versioned workflow definitions and operator runbook for lifecycle, recovery, and review context.