Openharness Daily: Three Catalogs and a Cleaner CLI
A four-PR stack landed today that splits sandbox tooling into three distinct catalogs — harness, runtime, and tool — while unifying the make and oh command paths behind one script, and a separate changelog fix closes a documentation loophole.
Duration: PT2M10S
Episode overview
This episode is a short developer briefing from Openharness Daily.
It explains recent repository work in plain language.
- Show: Openharness Daily
- Published: 2026-08-25T12:00:32Z
- Audio duration: PT2M10S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 25th, and today's story is one coordinated stack of work that reshapes how the sandbox CLI is organized.
Four pull requests — 821, 823, 824, and 825 — landed as an explicit stack, each reviewed in sequence and each touching the CLI's core file. The result is a clear three-way split in how sandbox tooling gets categorized. PR 821 introduced "oh harness install," letting developers add an agent CLI like OpenCode or Grok…
The capstone, PR 825, confirmed something worth remembering: the long-suspected redundancy between the make and oh command paths was surface-level, not structural. Every compose target — whether triggered by "make sandbox" or "oh sandbox" — runs the same underlying script. That PR consolidated the two entry points…
Separately, PR 822 tightened the changelog rule itself. The format was already supposed to be one line per entry, but "one line" was never quantified, so a nearly five-thousand-character paragraph technically qualified. That loophole is now closed with a quantified rule, since the changelog file is what the next…
What to remember: if you're adding a new harness, runtime, or tool going forward, expect three distinct code paths…
That's…
Nearby episodes from Openharness Daily
- Weekly Recap - Release Pipeline Overhaul
- The Release Pipeline Gets Rebuilt and Repaired
- Sandbox Substrate Spike Wraps Up
- Weekly Recap - Execution Architecture and Self-Healing Infrastructure
- Simplify, Then Verify
- The Firstmate Executor Lands, and the Harness Audits Itself
- Drawing the Boundaries
- Weekly Recap - Locking Down the Agent Sandbox