AgentKitten

Orbit selects a task from a dependency-ordered backlog, hands it to the configured agent adapter, runs tests, lint, and type checks against the result, and only advances the orbit when those gates pass. Every run writes four artifacts: structured agent output, rubric scoring, an accept-or-iterate recommendation, and a human-readable progress log. The workflow is agent-neutral — Claude, Codex, Cursor, or any adapter you wire up behind the same contract. Where it breaks: Orbit is intentionally minimal, so teams expecting a hosted dashboard, a GUI, or built-in multi-agent parallelism will find precious little of that. The harness is a loop, not a platform.