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
archived
这是什么?Project Claw Code 的对等移植项目——重建 Claude Code 编码工具框架,而作者选择不再跟踪其被泄露的快照。声明目标是:证明一个开放的编码工具框架能够以高速、公开、自主的方式构建出来。
那这个是一个我能真正用的编码智能体,还是一个还在移植中的半成品?目前它是一个移植工作区,还不是完成的智能体:src/ 下的 Python 目录提供了一个 CLI(main.py),用来渲染移植清单和摘要,而活跃的 Rust 工作区位于 rust/ 目录。
我该怎么上手?先看 rust/ 里的 USAGE.md,了解构建、认证、CLI、会话和 parity-harness 工作流程;rust/README.md 介绍了各个 crate。Python 这边的快速入门可以渲染移植摘要、清单、模块列表和验证结果。
要运行或者改这个项目,我需要装什么?没有明确列出任何依赖要求。由于这个仓库同时混合了 Rust 工作区(rust/,有自己的 Rust CI)和 Python 移植目录(src/),想全面动手的话两套工具链都需要。
这个移植版现在真的能表现得和原版一样吗?还不能:它复刻了存档的文件结构、子系统名称和命令/工具清单,但运行时行为并不等同——Python 目录里可执行的运行时部分更少。这个仓库还被归档为 claw-code 迁移期间的临时工作。
为什么不直接用它所基于的那份被泄露的 Claude Code 源码?作者权衡了法律和伦理问题(并读了一篇相关的文章)之后,不希望那份被泄露的快照继续作为被跟踪的源码树,于是仓库转向了移植工作。
这个项目和 Anthropic 或 Claude Code 有官方关系吗?没有。README 声明本仓库不主张对原始 Claude Code 源码材料的所有权,也与 Anthropic 无关联、未获其背书、也非其维护。
如果代码不是人写的,那是谁写的?自主的 claw 工作流(lobsters/claws):并行的编码会话、事件驱动的编排、恢复循环和机器可读的泳道状态。像 Bellman / Yeachan Heo 这样的人负责定方向;代码重构和文档则是在 Codex 之上用 oh-my-codex(OmX)编排完成的。
描述里说是 Rust 移植,但 README 又说以 Python 为主——到底是哪个?两者都存在:README 横幅指向 rust/ 里活跃的 Rust 工作区,而 Porting Status 说主源码树现在是以 Python 为主的 src/。在迁移期间这两部分并存。
Size
5.9 MB
Stars
6.6K
Updated
CommitApr 05
Age
6mo
Commits · 90 Days