codejunkie99

Autoharness — Development skill for Claude Code

Development community

macOS coding-agent control center: one objective, routed to direct execution, a bounded loop, a swarm, or a dynamic DAG.

How to install Autoharness

This entry records only its repository, not the path inside it, so there is no exact command to give. Open codejunkie99/autoharness and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Autoharness does

macOS coding-agent control center: one objective, routed to direct execution, a bounded loop, a swarm, or a dynamic DAG. Local only, no external writes.

Alternatives in Development

Gyoshu Auto — Start goal-based autonomous research with bounded execution 244 ★
Omk — Evidence-gated runner for Codex, Claude Code, OpenCode, and local coding agents 141 ★
Ccc Orchestration — Spawn, inject into, and ask questions of persistent sibling sessions via Claude Command Center (CCC) 130 ★

README

AutoHarness

[![platform](https://img.shields.io/badge/platform-macOS%2014%2B-000000?logo=apple&logoColor=white)](#requirements) [![rust](https://img.shields.io/badge/rust-1.97%2B%20·%20edition%202024-CE422B?logo=rust&logoColor=white)](#requirements) [![version](https://img.shields.io/badge/version-0.1.0-blue)](Cargo.toml) [![license](https://img.shields.io/badge/license-Apache--2.0-green)](LICENSE) [![tests](https://img.shields.io/badge/tests-606%20passing-brightgreen)](#test) [![network](https://img.shields.io/badge/external%20writes-none-informational)](SECURITY.md)

Badges are declared facts, not CI output. There is no hosted pipeline: the GPUI shell needs a Metal toolchain, so the gate in [CONTRIBUTING.md](CONTRIBUTING.md) runs locally and is what those numbers come from.

A macOS-only coding-agent control center. Accepts one objective through coordinator chat, routes it to direct execution, a bounded loop, a swarm, or a dynamic DAG, and orchestrates installed Codex or Claude CLI sessions — all local, no external writes. See `PLAN.md` for the full product plan, and [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for how the pieces fit.

**Status: all local V1 phases are complete in code.** Foundation, engine bridge, sandbox, durable queues, direct chat, router and loops, graphs and swarms, replayable review surfaces, memory/evolution, the true-black cockpit, and release hardening ship together. Release hardening covers data integrity, export, privacy purge, diagnostics, semantic keyboard/VoiceOver accessibility, native attention, universal packaging, and a fail-closed signed-update path. Production signing, notarization, and update-feed hosting still require the owner's external credentials. A raw interactive PTY is intentionally outside AutoHarness's structured-agent scope; captured ANSI check output and classified unified diffs are built in.