Rewriting Project Claw Code
⭐ The fastest repo in history to surpass 50K stars, reaching the milestone in just 2 hours after publication ⭐
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.mdand 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
Porting Status
The main source tree is now Python-first.
src/contains the active Python porting workspacetests/verifies the current Python workspace- the exposed snapshot is no longer part of the tracked repository state
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:
port_manifest.py— summarizes the current Python workspace structuremodels.py— dataclasses for subsystems, modules, and backlog statecommands.py— Python-side command port metadatatools.py— Python-side tool port metadataquery_engine.py— renders a Python porting summary from the active workspacemain.py— a CLI entrypoint for manifest and summary output
Quickstart
Render the Python porting summary:
python3 -m src.main summaryPrint the current Python workspace manifest:
python3 -m src.main manifestList the current Python modules:
python3 -m src.main subsystems --limit 16Run verification:
python3 -m unittest discover -s tests -vRun the parity audit against the local ignored archive (when present):
python3 -m src.main parity-auditInspect mirrored command/tool inventories:
python3 -m src.main commands --limit 10
python3 -m src.main tools --limit 10Current 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.
$teammode: used for coordinated parallel review and architectural feedback$ralphmode: used for persistent execution, verification, and completion discipline- Codex-driven workflow: used to turn the main
src/tree into a Python-first porting workspace
OmX workflow screenshots
Ralph/team orchestration view while the README and essay context were being reviewed in terminal panes.
Split-pane review and verification flow during the final README wording pass.
Community
Join the instructkr Discord — the best Korean language model community. Come chat about LLMs, harness engineering, agent workflows, and everything in between.
Star History
See the chart at the top of this README.
Ownership / Affiliation Disclaimer
- This repository does not claim ownership of the original Claude Code source material.
- This repository is not affiliated with, endorsed by, or maintained by Anthropic.
