claw-code-parity README

The project's README from github.com/ultraworkers/claw-code-parity. As one markdown file: README.md.

Rewriting Project Claw Code

⭐ The fastest repo in history to surpass 50K stars, reaching the milestone in just 2 hours after publication ⭐

Star History Chart

Claw

Autonomously maintained by lobsters/claws — not by human hands

clawhip · oh-my-openagent · oh-my-claudecode · oh-my-codex · UltraWorkers Discord

[!IMPORTANT] The active Rust workspace now lives in rust/. Start with USAGE.md for build, auth, CLI, session, and parity-harness workflows, then use rust/README.md for crate-level details.

Want the bigger idea behind this repo? Read PHILOSOPHY.md and Sigrid Jin's public explanation: https://x.com/realsigridjin/status/2039472968624185713

Shout-out to the UltraWorkers ecosystem powering this repo: clawhip, oh-my-openagent, oh-my-claudecode, oh-my-codex, and the UltraWorkers Discord.

Backstory

This repo is maintained by lobsters/claws, not by a conventional human-only dev team.

The people behind the system are Bellman / Yeachan Heo and friends like Yeongyu, but the repo itself is being pushed forward by autonomous claw workflows: parallel coding sessions, event-driven orchestration, recovery loops, and machine-readable lane state.

In practice, that means this project is not just about coding agents — it is being actively built by them. Features, tests, telemetry, docs, and workflow hardening are landed through claw-driven loops using clawhip, oh-my-openagent, oh-my-claudecode, and oh-my-codex.

This repository exists to prove that an open coding harness can be built autonomously, in public, and at high velocity — with humans setting direction and claws doing the grinding.

See the public build story here:

https://x.com/realsigridjin/status/2039472968624185713

Tweet screenshot

Porting Status

The main source tree is now Python-first.

The current Python workspace is not yet a complete one-to-one replacement for the original system, but the primary implementation surface is now Python.

Why this rewrite exists

I originally studied the exposed codebase to understand its harness, tool wiring, and agent workflow. After spending more time with the legal and ethical questions—and after reading the essay linked below—I did not want the exposed snapshot itself to remain the main tracked source tree.

This repository now focuses on Python porting work instead.

Repository Layout

.
├── src/                                # Python porting workspace
│   ├── __init__.py
│   ├── commands.py
│   ├── main.py
│   ├── models.py
│   ├── port_manifest.py
│   ├── query_engine.py
│   ├── task.py
│   └── tools.py
├── tests/                              # Python verification
├── assets/omx/                         # OmX workflow screenshots
├── 2026-03-09-is-legal-the-same-as-legitimate-ai-reimplementation-and-the-erosion-of-copyleft.md
└── README.md

Python Workspace Overview

The new Python src/ tree currently provides:

Quickstart

Render the Python porting summary:

python3 -m src.main summary

Print the current Python workspace manifest:

python3 -m src.main manifest

List the current Python modules:

python3 -m src.main subsystems --limit 16

Run verification:

python3 -m unittest discover -s tests -v

Run the parity audit against the local ignored archive (when present):

python3 -m src.main parity-audit

Inspect mirrored command/tool inventories:

python3 -m src.main commands --limit 10
python3 -m src.main tools --limit 10

Current Parity Checkpoint

The port now mirrors the archived root-entry file surface, top-level subsystem names, and command/tool inventories much more closely than before. However, it is not yet a full runtime-equivalent replacement for the original TypeScript system; the Python tree still contains fewer executable runtime slices than the archived source.

Built with oh-my-codex

The restructuring and documentation work on this repository was AI-assisted and orchestrated with Yeachan Heo's oh-my-codex (OmX), layered on top of Codex.

OmX workflow screenshots

OmX workflow screenshot 1

Ralph/team orchestration view while the README and essay context were being reviewed in terminal panes.

OmX workflow screenshot 2

Split-pane review and verification flow during the final README wording pass.

Community

instructkr

Join the instructkr Discord — the best Korean language model community. Come chat about LLMs, harness engineering, agent workflows, and everything in between.

Discord

Star History

See the chart at the top of this README.

Ownership / Affiliation Disclaimer

claw-code-parity (ultraworkers/claw-code-parity)

Searching Database…

6.6K ·GitHub
Claw-code-parity
archived
What is this?A parity port of Project Claw Code — a rebuild of the Claude Code coding harness whose exposed snapshot the author chose not to track. The stated goal: prove an open coding harness can be built autonomously, in public, at high velocity.
So is this a coding agent I can actually use, or still a work-in-progress port?Right now it's a porting workspace, not a finished agent: the Python tree in src/ exposes a CLI (main.py) that renders porting manifests and summaries, while the active Rust workspace lives in rust/.
How do I get started with it?Start with USAGE.md in rust/ for build, auth, CLI, session and parity-harness workflows; rust/README.md covers the crates. On the Python side the quickstart renders the porting summary, manifest, module list and verification.
What do I need installed to run or hack on it?No requirements are spelled out. Since the repo mixes a Rust workspace (rust/, with its own Rust CI) and a Python porting tree (src/), you would need both toolchains to work across it.
Does the port actually behave like the original yet?Not yet: it mirrors the archived file surface, subsystem names and command/tool inventories, but is not runtime-equivalent — the Python tree has fewer executable runtime slices. The repo is also archived as temporary work while claw-code migrates.
Why not just use the exposed Claude Code source this came from?After weighing the legal and ethical questions (and reading an essay on the topic), the author did not want the exposed snapshot to remain the tracked source tree, so the repo pivoted to porting work instead.
Is this officially connected to Anthropic or Claude Code?No. The README states the repo does not claim ownership of the original Claude Code source material and is not affiliated with, endorsed by, or maintained by Anthropic.
If humans are not writing the code, who is?Autonomous claw workflows (lobsters/claws): parallel coding sessions, event-driven orchestration, recovery loops and machine-readable lane state. Humans like Bellman / Yeachan Heo set direction; restructuring and docs were orchestrated with oh-my-codex (OmX) on top of Codex.
The description says a Rust port, but the README says Python-first — which is it?Both exist: the README banner points to an active Rust workspace in rust/, while Porting Status says the main source tree is now Python-first in src/. The two surfaces coexist during the migration.
What are similar projects?munder-difflin, openrig, hive, deer-flow, ruflo, OpenTrade-Agent, fractal, agentbox
Which topics is it in?harness-engineering, harness, autonomous-agents, orchestration, multi-agent, developers, coding-agent, rust, codex, claude-code, automation, ai-agents
Creator
ultraworkers
Size
5.9 MB
Stars
6.6K
Updated
CommitApr 05
Age
6mo
Commits · 90 Days